Searching for an Application
The Merchant Application Datagrid enables you to quickly and efficiently search for merchant applications and/or filter the resulting datagrid to find precisely the application on which you want to work or view. The default datagrid displays nine commonly used data columns to identify an application, but can be expanded to include more data columns that display the results of automated checks, the decisioning method, and bank information.
The Merchant Application Datagrid
To access the Merchant Application Datagrid, log in at the corporate level (Forte Payments - 10000) and click Merchant Application > Applications. The following table describes what each data column displays in the default (i.e., unexpanded) datagrid:
| Column | Description |
|---|---|
| Application ID | The ID number automatically assigned to the application when the merchant submits it. The that displays next to the Application ID indicates unassigned applications. Currently, Dex automatically assigns merchant applications after submission; manual assignment occurs in Web Tools. |
| DBA Name | The "Doing Business As" name of the business. |
| Status |
The status of the application. Supported values include the following:
|
| Received | The date and time when Forte received the merchant application. |
| Services |
The Forte service or combination of services for which the merchant applied. Supported values include the following:
|
| Assigned To | The name of the Forte employee auto assigned to the application. |
| Last Updated | The date and time when the application was last updated. |
| Portfolio ID | The name and Portfolio ID of the partner that submitted the application. |
| Sales Rep | The name or ID number of the Forte or partner sales representative who originally sent the application to the merchant. |
Click the
button to select and display additional columns on the Merchant Applications Datagrid. The following table describes what each of these additional data columns display:
| Column | Description |
|---|---|
| Select All | Click this option to add all the fields listed in this table to the Merchant Application Datagrid. |
| Tax ID | The Tax Identification Number associated with the business or owner of the business. This number could be the primary owner's Social Security Number (SSN) or Individual Taxpayer Identification Number (ITIN) or the Employer Identification Number (EIN) associated with the merchant's business. |
| Last 4 SSN | The last four digits of the primary owner's Social Security Number. |
| Bank Name | The merchant's bank name, routing number, and last four digits of the account number. |
| Fee ID | The identification number of the rate plan associated with this merchant application. |
| Source |
Indicates what the merchant used to submit the application. Supported options include the following:
|
| Credit Check |
The result of the credit check performed on the merchant's primary owner. Supported options include the following:
|
| Consumer Checks |
The result of the various, automated authentication and verification checks performed by LexisNexis's Fraudpoint solution using the merchant's submitted ownership data ((P) for the Primary Owner, (2) for the Secondary Owner, (3) for the Tertiary Owner, and (4) for the Quaternary Owner). These checks include CIDV scores, red flag reports, and OFAC verifications. Supported options for these fields include the following:
|
|
Business Check |
The result of the automated verification check performed by LexisNexis's Fraud Defender using the merchant's submitted data. These checks include BIDV scores and red flag reports. Supported options for this field include the following:
|
| Risk Check |
The result of the automated verification check performed on the merchant's submitted business type, business category, and Merchant Category Code (MCC). Supported options for this field include the following:
|
| Phone Check |
The result of the automated verification check performed by Twilio on the merchant's phone number. Phone numbers associated with VoIP or prepaid/burner phone automatically puts an application in review. Supported options for this field include the following:
|
| Bank Check |
The result of the automated Account Owner Authentication (AOA) check performed by Early Warning. Supported options for this field include the following:
|
| Criminal Check |
The result of the automated criminal background check performed by LexisNexis. After obtaining the merchant's Criminal Report, Forte performs validations on it to ensure the merchant has not been arrested or convicted of a specific list of charges involving fraud and financial crimes. Supported options for this field include the following:
|
| Internal Check |
The result of the automated check Forte conducts on every merchant application to ensure the submitted data falls within our acceptable internal thresholds for that Merchant Category Code, such as maximum and annual sale and payable amounts, ownership types, and High-Risk Partner associations. Supported options for this field include the following:
|
| Tin Match |
The result of the automated check conducted by the TINCheck web service which verifies that the merchant's Tax Identification Number (TIN) matches the TIN associated with the legal name of the business.
|
| Decision Method | Indicates whether the application was Auto decisioned or put through a Manual review by Credit and Risk. |
Finding an Application
You can search for a specific application by entering the Application ID or DBA Name in the Search field of the Merchant Application Datagrid. If you're unsure what the Application ID or DBA Name are for the application, you can filter the datagrid using the following filters:
| Filter | Description |
|---|---|
| Received Date |
The date when Forte received the application. Use the date picker in both the Start Date and End Date fields to customize the date range of your listed applications. If a date range is not provided, the End Date defaults to today's date and the Start Date defaults to yesterday. You can also choose one of the following pre-set dates/date ranges:
This field saves the last date filter option so that you don't have to put the same option in every time you search for applications. |
| Status |
The status of the application. Supported filter values include the following:
|
| Portfolio Name | Enter the name of the partner that submitted the application. |
| Sales Rep | Enter the name of the sales representative associated with the application |
| Fee ID | Enter the identification number of the Rate Plan associated with the application. |
If you would like to refine the results of the Merchant Application Datagrid further, you can use more specific filter parameters located under the More Filters field. The following filters are available.
| Filter | Description |
|---|---|
| Assigned To | Enter the name of the Forte user assigned to this application. |
| Last 4 of SSN | Enter the last four digits of the primary owner's Social Security Number. |
| Portfolio ID | Enter the Portfolio ID of the organization that submitted the application. |
| Services |
Use the dropdown to select the Forte service or combination or services for which the merchant applied. Supported options include the following:
|
| Source | Use the dropdown to select how the merchant submitted his/her application. Supported options include the following:
|
| Tax ID | Enter the primary owner's Social Security Number (SSN) or Individual Taxpayer Identification Number (ITIN) or the Employer Identification Number (EIN) associated with the merchant's business. |
| Verification Checks |
Use the dropdown to select the verification checks and specified result associated with the merchant's application. The checks that can be used to filter the datagrid include the following:
Within each Verification Check filter field you select, use the dropdown menu to filter the datagrid by result. The Verification Check filter fields support the following result values:
|
that displays next to the Application ID indicates unassigned applications. Currently, Dex automatically assigns merchant applications after submission; manual assignment occurs in Web Tools.