Transactions

Hi there! Welcome to Dex, Forte's latest and greatest payments application. With Dex, you can view, create, and manage all your transaction data—including customers, payment methods, addresses, and schedules—in one convenient place. You can also view and maintain your merchant account, keep track of your funding entries, resolve disputed transactions, and generate API credentials to connect Dex with your third-party applications.

Create a Credit Card Transaction

Merchants can perform four different types of credit card transactions from the Transactions Datagrid. Additionally, merchants can choose to save the customer data from a transaction or perform a one-off transaction without saving customer data. NOTE: To create a new credit card transaction from a previously processed transaction using the same values (i.e., customer and payment method), access the original transaction and click Action > Add Transaction.

To add a new credit card transaction, complete the following steps:

Click Transactions in the Dex Navigation menu. The Transactions Datagrid displays.
Click the Add Transaction button in the upper right corner. The Add Transaction modal displays.
Ensure Dex selected the correct location. If your merchant account is set up with more than one location, the Location field displays as a dropdown menu of all the merchant's available locations.
Click the dropdown in the Action field to select the type of transaction to perform.NOTE: Refund/Disbursement transactions require the Create Credit role. The following options are currently supported:
- Debit/Sale
- Refund/Disbursement
- Authorize
- External Authorization
Enter the subtotal amount in the Subtotal field. This field is required.
Calculate the tax amount and enter it into the Tax field. This field is optional.
If you are a service-fee merchant or a merchant subscribed to the VISA Tax Program, a pre-populated Service Fee field displays beneath the Tax field. The Service Fee field only displays service fee merchants.
As you enter values into the Subtotal, Tax, and, if applicable, Service Fee fields, Dex automatically updates the Total amount that displays in the lower-left corner of the modal.
If you'd like to include additional order information for this transaction, fields are available in the Order Info section. Click the View all order fields to display all order information fields available for the transaction. NOTE: The configuration in the Location Transaction settings determines what fields are visible and if they are optional or required.
If you'd like to include the Customer information, Phone and Email fields are available in the Customer Info section. NOTE: Depending on the Location Transaction Settings, these fields may or may not be required.
If you would like to create a customer record from this transaction, click the Add new option and complete the following fields that display:

Field	Description
First Name	The customer's first name. NOTE: A customer must have, at a minimum, values for the First Name and Last Name fields or a value for the Company Name field.
Last Name	The customer's last name. NOTE: A customer must have, at a minimum, values for the First Name and Last Name fields or a value for the Company Name field.
Company	The name of the customer's company. NOTE: A customer must have, at a minimum, values for the First Name and Last Name fields or a value for the Company Name field.
Email	The customer's email address. This field is optional.
Phone	The customer's phone number. This field is optional.
Address Line 1	The first line of the customer's billing address. This field is required.
Address Line 2	If needed, the second line of the customer's billing address. This field is optional.
City	The city of the customer's billing address. This field is required.
State	The state of the customer's billing address. This field is required.
Postal	The zip or postal code of the customer's billing address. This field is required.
Country	The country of the customer's billing address.

12. Ensure the Credit/Debit Card box is selected and then capture the credit card data by either:

Clicking the Insert or Swipe options and then dipping or swiping the card in your eDynamo device (requires the Magtek MTSCRA service). If the dip or swipe attempt(s) fail or errors out, Dex will prompt you to manually enter the card data.
Manually enter the card data by completing the following required fields:

Field	Description
Card Holder Name	The first and last name of the cardholder. Both names are required.
Card Number	The full PAN or account number listed on the card. As you type the card into the Card Number field, Dex automatically detects and displays the card type. Supported card types include the following: • Visa • Mastercard • American Express • Discover • Diners Card • JCB
Expiration	The expiration date of the card in MM/YYYY format. This value must be a future date.
CVV	The CVV/CVV2 number listed on the card. This field is optional.
Postal	The zip code or postal number associated with the customer's billing address. This field is optional.
Auth Code	The authorization code provided by the issuer for a transaction. This field only displays for External Authorization Credit Card transactions and is required.
Procurement Card	Select this box if the credit card is a procurement card. When selected, the Account Code/PIN field displays. Enter the account code associated with the procurement card in this field. The Account Code/PIN field is required for procurement cards.

13. After completing the required fields, click the Add Transaction button. If the transaction is approved, an “Approved” message displays. From the message you can print the transaction receipt by clicking the Print Receipt button, which will display a browser Print Tab where you can configure your printer settings and print a copy of the EMV-compliant transaction receipt. NOTE: If you opt not to print the receipt at the time of submission, you can print a copy at a later time from the Transaction’s Details Screen.

Creating an eCheck Transaction

Merchants can perform six different echeck transaction from the Transactions Datagrid. Additionally, with the exception of Bank Account Owner Verification transactions, merchants can choose to save the customer data from a transaction or perform a one-off transaction without saving customer data. NOTE: To create a new echeck transaction from a previously processed transaction using the same values (i.e., customer and payment method), access the original transaction and click Action > Add Transaction.

To add a new echeck transaction, complete the following steps:

Click Transactions in the Dex Navigation menu. The Transactions Datagrid displays.
Click the Add Transaction button in the upper right corner. The Add Transaction modal displays.
Ensure Dex selected the correct location. If your merchant account is set up with more than one location, the Location field displays as a dropdown menu of all the merchant's available locations.
Click the eCheck option at the end of the Add transaction popup. NOTE: This applies only to merchants that have both Card Services and eCheck Services enabled.
Click the dropdown in the Transaction Action field to select the type of transaction to perform. NOTE: Refund/Disbursement transactions require the Create Credit role. The following options are currently supported:
- Debit/Sale
- Refund/Disbursement
- Authorize
- Force
- Verify
- Bank Account Owner Verification (go to step 14 for instructions on creating a Bank Account Owner Verification transaction)
If you'd like to include an Order Number and/or Reference ID for this transaction, click the More Options dropdown. The Order Number and Reference ID fields display.
Enter the subtotal amount in the Subtotal field. This field is required. NOTE: For Verify transactions, this field must be any value greater than $0.00.
Calculate the tax amount and enter it into the Tax field. This field is optional.
If you are a service-fee merchant or a merchant subscribed to the VISA Tax Program, a pre-populated Service Fee field displays beneath the Tax field. The Service Fee field only displays service fee merchants. NOTE: Dex does not charge service fees for verify-only transactions.
As you enter values into the Subtotal, Tax, and, if applicable, Service Fee fields, Dex automatically updates the Total amount that displays in the lower-left corner of the modal.
If you'd like to include additional order information for this transaction, fields are available in the Order Info section. Click the View all order fields to display all order information fields available for the transaction. NOTE: The configuration in the Location Transaction settings determines what fields are visible and if they are optional or required.
If you'd like to include the Customer information, Phone and Email fields are available in the Customer Info section. NOTE: Depending on the Location Transaction Settings, these fields may or may not be required.
If you would like to create a customer record from this transaction, click the Add new option in the Customer Info section and complete the following fields that display:

Field	Description
First Name	The customer's first name. NOTE: A customer must have, at a minimum, values for the First Name and Last Name fields or a value for the Company Name field.
Last Name	The customer's last name. NOTE: A customer must have, at a minimum, values for the First Name and Last Name fields or a value for the Company Name field.
Company	The name of the customer's company. NOTE: A customer must have, at a minimum, values for the First Name and Last Name fields or a value for the Company Name field.
Email	The customer's email address. This field is optional.
Phone	The customer's phone number. This field is optional.
Address Line 1	The first line of the customer's billing address. This field is required.
Address Line 2	If needed, the second line of the customer's billing address. This field is optional.
City	The city of the customer's billing address. This field is required.
State	The state of the customer's billing address. This field is required.
Postal	The zip or postal code of the customer's billing address. This field is required.
Country	The country of the customer's billing address.

14. Complete the following required for Payment Method fields:

Field	Description
Account Holder Name	The first and last name of the account holder. Both names are required.
Account Type	Use the dropdown to select whether this account is a Checking or Savings account.
Routing Number	The TRN or routing number of the bank. This value is typically the first number listed at the bottom of the check. This field is required.
Account Number	The customer's account number. This value is typically the second number listed at the bottom of the check. The value listed in this field must match the confirmation value in the Confirm Account Number field. Both the Account Number and the Confirm Account Number fields are required.
Entry Class Code	The entry class code for the transaction. Dex defaults this field to WEB, but you can use the dropdown to select the other available values: • ARC • CCD • CIE • CTX • POP • POS • PPD • RCK • TEL • BOC NOTE: The SEC code selected must be a code that you've used for transactions in the previous year; otherwise, the transaction may be declined for security and compliance purposes. To use a new SEC code for a transaction, contact Forte Customer Support at 1-866-290-5400, Option 1.
Check Number	The check number of the check. This field is optional.

15. If you would like to create a customer record from this transaction, click the Save Customer checkbox and complete the following fields that display:

Field	Description
First Name	The customer's first name. NOTE: A customer must have, at a minimum, values for the First Name and Last Name fields or a value for the Company Name field.
Last Name	The customer's last name. NOTE: A customer must have, at a minimum, values for the First Name and Last Name fields or a value for the Company Name field.
Company	The name of the customer's company. NOTE: A customer must have, at a minimum, values for the First Name and Last Name fields or a value for the Company Name field.
Email	The customer's email address. This field is optional.
Phone	The customer's phone number. This field is optional.
Address Line 1	The first line of the customer's billing address. This field is required.
Address Line 2	If needed, the second line of the customer's billing address. This field is optional.
City	The city of the customer's billing address. This field is required.
State	The state of the customer's billing address. This field is required.
Postal	The zip or postal code of the customer's billing address. This field is required.
Country	The country of the customer's billing address.

16. After completing the required fields, click the Add Transaction button. If the transaction is approved, an "Approved" message displays. From the message you can copy the transaction ID to search for it in the dex transaction datagrid or print the transaction standard or detailed receipt clicking the Print Receipt button, which will display a browser Print Tab where you can configure your printer settings and print a copy of the transaction receipt. NOTE: If you opt not to print the receipt at the time of submission, you can print a copy at a later time from the Transaction's Details Screen.

Creating a Bank Account Owner Verification Transaction

Merchants that have Bank Account Owner Verification – Authenticate enabled can create a bank account owner verification transaction. If this service is not enabled for the merchant than the action will not be visible in the drop-down list.

To add a new Bank Account Owner Verification transaction, complete the following steps:

17. Click Transactions in the Dex Navigation menu. The Transactions Datagrid displays.

18. Click the Add Transaction button in the upper right corner. The Add Transaction modal displays.

19. Ensure Dex selected the correct location. If your merchant account is set up with more than one location, the Location field displays as a dropdown menu of all the merchant’s available locations.

20. Click the eCheck option at the end of the Add transaction popup.

21. Click the dropdown in the Transaction Action field and select Bank Account Owner Verification

22. Complete the following required fields:

Field	Description
First Name	First Name of the Bank Account Owner
Last name	Last Name of the Bank Account Owner
Business name	Registered Business Name of the Bank Account
Routing and Transit Number	The TRN or routing number of the bank. This value is typically the first number listed at the bottom of the check.
Bank Account Number	The bank account number to be verified. This value is typically the second number listed at the bottom of the check.
Bank Account Type (optional)	Checking Account or Savings Account

Note: First Name and Last Name or Business Name is required. First Name, Last Name and Business Name can be entered.

23. After completing the required fields, click Verify Account Owner button. The verification check will return a result of Match, Conditional Match, No Match or No Into.

Search for a Transaction

The Transactions Datagrid enables merchant users with appropriate permissions to view the transactions of an Organization's child Locations. By default, Dex displays the newest transactions by received date and time first, but you can choose to sort the results from Oldest to Newest or Newest to Oldest or can filter the displayed results by Received Date, Locations, Status, Method, Action, Amount,Order ID, Response, and/or the Last 4 digits of an account number. You can customize the number of items that display using the display dropdown in the bottom left corner.

To access the Transactions Datagrid, click Transactions in the Dex main menu. The most recent transactions display first.

To view a specific transaction without having to filter through a long list, enter one of the following values in the search bar on the Transaction Datagrid:

Billing Company Name
Billing First Name
Billing Last Name
Transaction Trace Number
Location
Customer ID

Dex auto-populates the list of results, which you can further refine by using the search filters described below.

The following table provides a brief description of what each column displays on the Transactions Datagrid:

Column	Description
Received	The date and time when Forte received the transaction (e.g., March 31, 2018 04:23 PM). This timestamp data displays for the timezone of the merchant location that processed the transaction. If the location has not designated a timezone, Dex defaults to Pacific Standard Time (PST).
Status	The status of the transaction. The following values are supported: • In Progress - The transaction was received and is awaiting origination (echecks) or settlement (credit cards). If authorized, this field also displays the Status, Response, Return, and/or Settlement Code that returned with the response. • Completed - The transaction was funded to or from the merchant's bank account. • Failed - The transaction was declined, rejected, voided, or failed verification for reasons detailed in the Status, Response, Return, and/or Settlement Code that returned with the response.
Customer	The Company Name or First and Last Name of the customer associated with this transaction. If applicable, this field also includes the merchant-specified Consumer ID.
Order Info	If supplied, the merchant-defined Order Number and Reference ID included with the transaction. These parameters can include anything from invoice IDs, ticket numbers, or P.O. Box numbers.
Amount/Action	Displays the transaction amount and type of transaction. Dex supports the following transaction types: • Debit/Sale • Auth • Refund/Credit • Force/External Auth • Verify • Balance Inquiry NOTE: The Auth action also displays either a D or C to indicate if the transaction was a Debit or Credit.
Method	The payment method used plus the last four digits of the credit card or bank account number. The following values are supported: • eCheck • American Express • Discover • MasterCard • Visa
Authorization Info	Displays the authorization result and the transaction source. If the transaction was approved, this column displays the Authorization Number and the Approval Code. If the transaction was declined, an "Auth Decline" message displays. If the authorization is still in progress, the column remains blank.
Location	The name and ID of the merchant location that processed the transaction.

If you would like to view more data related to your transactions, you can expand the Transactions Datagrid by clicking and selecting the additional columns of data to display. The following table provides a brief description of these additional data columns:

Column	Description
Bank Account Status Verification	Displays the P-codes associated with a Validate Plus transaction. The following options display: P15 - High Risk P20 - Negative Reports P21 - No Negative Reports P23 - Invalid Account/ABA Number P40 - No Negative Info P41 - Negative Info P50 - No Info P70 - Validated P71 - Low Risk Approval P73 - Medium Risk Approval P80 - Vendor Busy P90 - Preauth Vendor Unavailable P91 - Preauth Vendor Error P92 - Preauth Server Unavailable
Bank Account Owner Verification	Displays the P-codes associated with an Authenticate transaction. The following options display: P10 - No Match P50 - No Info P60 - Match P75 - Conditional Match P90 - Preauth Vendor Unavailable P91 - Preauth Vendor Error P93 - Error P94 - Invalid Routing Number P94 - Invalid Account Number P95 - Bad Account
Principal	The authorized amount of a transaction, which includes taxes (if applicable) but not service fees.
Service Fee	The service/convenience fee for the transaction. Service fees are either a percentage of the principal or a set amount.

Filtering the Transaction Display List

Apply the following general filters to customize the displayed transaction list:

Filter	Description
Received	The Received Date of the transaction. Use the date picker in both the Start Date and End Date fields to customize the date range of your listed transactions or manually enter the desired dates in MM/DD/YYYY format in the provided data fields. 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: • Since Yesterday • Last 7 days (the previous six days plus today) • Last 30 days • Last 60 days • Last 90 days • Last 180 days • This week (starting from Sunday to Saturday) • This month • Custom 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 transactions.
Location	Wording for Merchant Guide: Search the name or ID of the merchant location that processed the transaction. • At the Merchant level the location filter will display the first 10 Locations in a dropdown list for the user to select. If there are more than 10 locations under the Merchant Organization, users can search for additional locations using the search function in the location filter modal. • To limit performance issues, no locations will be displayed in the Location filter at the Enterprise level. The search bar within the filter can be used to search for specific locations to select.
Amount	The amount of the transaction. Enter only the number(s) and/or decimal point. Do not enter currency symbols. The maximum allowable amount is $100,000.
Status	The status of the transaction. The following values are supported: In Progress • Authorized • Ready • Settling • Review • Conditional Match Successful • Complete • Settled • Funded Match Unsuccessful • Declined • Failed • Rejected • Voided • Unfunded • No Match No Info
Last 4	The last four digits of the credit card or echeck account number.
Account Number	The full credit card PAN or bank account number associated with the payment method.
Order ID	The unique, merchant-defined identification number associated with this transaction.

If you would like to refine the results of a transaction list further, you can use more specific filter parameters located under the More Filters dropdown field. The following filters are available.

Filter	Desciption
Authorization Number	The numeric authorization number generated for the transaction (e.g., 244234).
Action	The type of transaction. The following values are supported: • All • Debit/Sale • Auth • Refund/Credit • Force/External Auth • Verify • Balance Inquiry
Methods	The payment method used for the transaction. The following values are supported: • Echeck • American Express • Discover • MasterCard • Visa • Diners • JCB
Order ID	The unique, merchant-defined identification number associated with this transaction.
Source	The terminal hardware, software, or integration method used to connect to Forte. Enter a source in the free-text search field and click Update. Supported search values include the following: • RESTAPI • FCO (Forte Checkout) • Scheduled • CONSOLE (Dex) • VX520 • FORTECO • SPLITTRANS • N/A
Response	The transaction response. Users can filter transactions results by the following supported response values: • All • Approved • Declined
Bank Account Status Verification	Displays the P-codes associated with a Validate Plus transaction. The following options display: • P15 - High Risk • P20 - Negative Reports • P21 - No Negative Reports • P23 - Invalid Account/ABA Number • P40 - No Negative Info • P41 - Negative Info • P50 - No Info • P70 - Validated • P71 - Low Risk Approval • P73 - Medium Risk Approval • P80 - Vendor Busy • P90 - Preauth Vendor Unavailable • P91 - Preauth Vendor Error • P92 - Preauth Server Unavailable
Bank Account Owner Verification	Displays the P-codes associated with an Authenticate transaction. The following options display: • P10 - No Match • P50 - No Info • P60 - Match • P75 - Conditional Match • P90 - Preauth Vendor Unavailable • P91 - Preauth Vendor Error • P93 - Error • P94 - Invalid Routing Number • P94 - Invalid Account Number • P95 - Bad Account
Wallets	The wallet type used for the transaction. Users can filter transactions by the following wallet types: • Apple Pay • Google Pay

Dex has a 2048 character limit for filters applied. If the filters applied to the data grid exceed the 2048 character limit, dex will display a warning message to inform the user to reduce the number of filters and try the search again.

Viewing Transaction Details

The Transaction's Detail Screen enables merchant users with appropriate permissions to view the details of a particular transaction. A Transaction's Detail Screen displays Payment Information, Authorization and Settlement Data, the Receiver's Effective Date, Dispute Status, Transaction History, and a detailed Receipt from the transaction.

To view the details of a transaction, complete the following steps:

Access the Transactions Datagrid by clicking Transactions on the Dex main menu.
Search for the desired transaction by First Name, Last Name, Company Name, Transaction ID, or Location ID, or use the applicable filters to narrow down the displayed search results.
After locating the desired transaction, click the row on which it is listed. That Transaction's Details Screen displays.

NOTE: Transactions with a status of Voided, Declined, Authorized, Rejected, Review, or Unfundedwill not display settlement information for both credit card and ACH transactions.

For more details on what the Transaction's Detail Screen displays, select whether it's a Credit Card or eCheck transaction.

Credit Card Transactions

The following table displays Payment, Receiver, Dispute, Authorization, Settlement, History, and Receipt data that could display with a credit card transactions.

Card/Tab	Field	Description
Payment Information	Status	The current status of the transaction. Supported options include the following: • In-Progress - The transaction is in the process of settling. • Authorized - The customer's payment was authorized. To complete the sale, the item must be captured from the Transaction's Details page. • Declined - The transaction was declined for reasons detailed in the Response Code and Response Description fields. • Failed - The transaction failed for reasons detailed in the Response Code and Response Description fields. • Ready - The transaction was received and is awaiting settlement. • Review - Transaction was unable to be settled due to a merchant configuration issue. Contact Customer Service to resolve the issue. • Settled - The credit card item has been funded to the merchant's bank account. • Voided - The transaction was voided and the item will not be settled.
	Action	The action the transaction performs. Supported options include the following: • Debit/Sale • Refund/Credit • Auth • Force/External Auth • Balance Inquiry
	Authorization Amount	The total authorization amount to be debited/credited plus the currency. This amount can include the Subtotal, Tax, and Service Fee amounts.
	Customer/Company Name	The first and last name of the customer or the company name associated with the customer.
	Wallet type	The wallet type used for this transaction. This parameter displays the logo of the following supported alternative methods of payment: • Apple Pay • Google Pay
	Method	The card brand used for this transaction. This parameter displays the logo of the following supported card brands: • American Express • Discover • MasterCard • Visa • Diners • JCB
	Last 4 Account Number	The last four digits of the customer's credit card PAN .
	Card Holder Name	The First and Last Name or Company Name of the cardholder.
	Card Number	The semi-redacted credit card PAN.
	Customer ID	The merchant-defined identification number associated with the customer.
	Expires On	The month and year when the credit card expires in mm/yyyy format.
	Card Category	Uses the card BIN number to determine the category or amount of credit this issuer has provided for this card (e.g., Business Platinum). Following are the supported values for this field: • N/A • AARP • AIRMILES PREMIER • ATM ONLY • ATM ONLY - CASHLINE CARD • ATM CARD • BLACK • BLUE • BLUE AIRMILES CASH BACK CARD • BLUE & REVOLVING • BLUE CASH • BLUE FOR BUSINESS • BMI PLUS • BONUS • BUSINESS • BUSINESS CARD • BUSINESS ELITE • BUSINESS PLATINUM • CASH REBATE • CENTURION • CENTURION SERVICIO • CHARGE CARD • CHECK CARD • CLASSIC • CONSUMER CARD • CONSUMER PREMIUM CARD • CORP.GOLD D & RANGES • CORP. GOLD S & RANGES • CORP.GREEN D & RANGES • CORP.GREEN S & RANGES • CORP. PURCHASING CARD • CORPO.CO.S & RANGES • CORPORATE • CORPORATE CARD • CORPORATE FLEET CARD • CORPORATE GOLD • CORPORATE GOLD Y PLATINUM • CORPORATE GREEN • CORPORATE GREEN EBTA • CORPORATE PURCHASE • CORPORATE PURCHASING • CORPORATE T • CORPORATE T&E • CORPORATE REVOLVING • CREDIT • DEBIT • DELTA • DIREKT • DORADA • ELECTRIC ORANGE • ELECTRON • ELECTRONIC • EXECUTIVE BUSINESS • GIFT • GLOBAL PAYMENT • GM CARD • GOLD • GOLD & PLATINUM • GOLD BUSINESS • GOLD CASH BACK CARD • GOLD GRCC YBLUE • GOLD/PLATINUM • GOLD/PREM • GOLD PREMIUM • GOVERNMENT • COMMERCIAL CARD • GREEN • GSA CARD • HSA NON-SUBSTANTIATED • ICARD • IKEA CARD • INFINITE • LOWES CARD • MASTERMONEY • NEW WORLD • OPTIMA • OTHER • OUROCARD • PAYMENT CARD • PAYPASS • PAYPASS CARD • PEONY • PEONY MONEY LINK • PEONY QUASI-CREDIT • CARD • PLATINUM • PLUS • PREMIUM • PREMIUM PLUS • PREMIER • PREPAID • PREPAID – BUSINESS • PREPAID CASH • PREPAID - CLASSIC • PREPAID - CORPORATE T&E • PREPAID - ELECTRON • PREPAID - PLATINUM • PREPAID - PRIVATE LABEL • PREPAID TRAVEL MONEY • PRIVATE • PRIVATE LABEL • PROPRIETARY • PROPRIETARY ATM • PURCHASING • QUANTUM • REBATE • REVOLVING • SALUTE • SBS GOLD Y BLUE • SEARS • SIGNATURE • SIGNATURE BUSINESS • SMALL BUSINESS • SMALL BUSINESS SBS GREEN • SMALL CORPORATE • SMALL CORPORATE CARD • STANDARD • STANDARD UNEMBOSSED • TJ PERSONAL • TRAVEL MONEY • V PAY • VIRGIN ATLANTIC • VIRTUAL • VISA CASH • VISA COMMERCE • WORLD • WORLD CARD • WORLD DEBIT EMBOSSED • WORLD ELITE • WORLD FOR BUSINESS
	Issuer	The name, country, phone number, and website of the bank or issuer of the credit card.
	Location	The name and ID of the merchant's location.
Receiver Effective		The date when the transaction received an authorization response.
Dispute Status		If applicable, the current status of any dispute the customer made against the transaction. Clicking this card takes you to the Dispute's Detail Screen.
Details - Authorization	Status	The status of the transaction's authorization. Supported values include the following: • Authorized - The customer's payment was authorized. To complete the sale, the item must be captured from the Transaction's Details page. • Declined - The transaction was declined for reasons detailed in the Response Code and Response Description fields. • Ready - The transaction was received and is awaiting settlement. • Review - Transaction was unable to be settled due to a merchant configuration issue. Contact Customer Service to resolve the issue. • Settled - The credit card item has been funded to the merchant's bank account. • Voided - The transaction was voided and the item will not be originated or settled. • Unfunded - For debit transactions, funds have been removed from the merchant's bank account because of sale transaction returns or dispute losses. For credit transactions, funds have added to the merchant's bank account because of refund dispute losses and refund transaction returns.
	Transaction ID	A 36-character code that uniquely identifies the transaction.
	Authorization Number	The numeric authorization code generated for the transaction (e.g., 244234).
	AVS Result	The result of the Address Verification Service check. The following values are supported: • Match: Street Address and 9-digit Zip Code both match • Match: Street Address and 5-digit Zip Code both match Partial Match: Street Address matches, but both 5-digit and 9-digit Zip Code do not match • Partial Match: Street Address does not match, but 9-digit Zip Code matches • Partial Match: Street Address does not match, but 5-digit Zip Code matches • No Match: Street Address, 5-digit Zip Code, and 9-digit Zip Code all do not match • System Unavailable: Address information unavailable. Forte returns this response if the Street Address is a non-US address, if the AVS service is unavailable, or if the AVS service for a particular US bank is not properly functioning. • System Unavailable: Forte will retry the AVS check because the issuer's system is unavailable or the request times out. • Invalid: AVS data is invalid • Not Supported: The US issuing bank does not support AVS checks.
	CVV Result	The result of the Card Verification Value check. The following values are supported: • Match • No Match • Error (Unrecognized or • Unknown Response) • Invalid or Null • Not Processed • Service Not Supported • Issuer Unable to Process • No Response
	Swipe Data	A field indicating whether or not this transaction has associated magstripe data (track one or two).
	Card Input Method	Indicates whether the cardholder data was: • Keyed • Swiped • EMV NOTE: A value for this field only displays for credit card transactions.
	Recurring Indicator	A field indicating if this transaction is part of a schedule of recurring transactions.
	Procurement Card	A field indicating whether or not a procurement card was used for this transaction.
	Source	The terminal hardware, software, or integration method used to connect to Forte (e.g., Direct Socket, VX520, etc).
	IP Address	The IP Address from where the merchant/partner submitted the transaction.
	Entered By	The name or API key of the user that created this transaction.
Details - Settlement	Status	Indicates whether the transaction resulted in a Deposit or a Withdrawal.
	Amount	The total amount the transaction was settled for.
	Response Code	This field displays the response and settlement codes for rejected transactions. Click here to view the supported Transaction Return • Codes:Insufficient Fund - R01 - The balance is not sufficient to cover the value of the transaction. • Account Closed - R02 - A previously open account has been closed. • No Account - R03 - The account is closed or doesn't match the name submitted. • Invalid Account Number - R04 - The account number structure is invalid. • Pre-Note Not Recieved - R05 - Pre-notification was not received. • Returned per ODFI - R06 - ODFI has requested RDFI to return this item. • Authorization Revoked - R07 - Account holder has revoked the company's authorization. • Payment Stopped - R08 - Account holder has stopped payment on this single transaction. • Uncollected Funds - R09 - Balance is sufficient, but can't be released until uncollected items are collected. • No Authorization - R10 - Account holder advises that the transaction is not authorized. • Check Safekeeping Return - R11 - Return of a check safekeeping entry return. • Branch Sold - R12 - The account is at a branch that was sold to another financial institution. • RDFI Not Qualified - R13 - RDFI not qualified to participate. • Deceased - R14 - The account holder is deceased. • Beneficiary Deceased - R15 - The beneficiary entitled to benefits is deceased. • Account Frozen - R16 - Funds are unavailable due to action by RDFI or other legal action. • Non-Transaction Account - R20 - Policies/regulations restrict activity to this account. • Payment Refused - R23 - The account holder refuses the transaction because the amount is inaccurate for another legal reason. • Duplicate Entry - R24 - The transaction appears to be a duplicate item. • Mandatory Error - R26 - The transaction is missing data from a mandatory field. • Invalid TRN - R28 - The Transit Routing Number is invalid. • Corporate Not Authorized - R29 - The corporate receiver has notified RDFI that the Corp entry is not authorized. • ODFI Permits Late Return - R31 - RDFI rejected an entry that the ODFI had accepted (applies to CCD and CTX only) • Invalid Company ID - R50 - The OwnerCompany ID field is not valid. Invalid Transaction Date - R56 - The date specified is invalid. • Stale Date - R57 - The transaction is too old for processing. • Over Limit - R95 - This transaction is over your authorized limit. • Account On Hold - R96 - The company account is on hold. • RDFI Does Not Participate - R97 - RDFI does not allow this type of transaction. • Invalid Password - R98 - The password supplied was invalid. • Declined Unpaid Item - R99 - This account or ID has been declined due to unpaid items.
History		Provides a dated and timestamped summary of all the events that have occurred with this transaction.
Receipt		Provides a detailed view of this transaction's receipt, including Line Items, XDATA 1-9, and other user-defined fields (e.g. Data Label 1-4 fields in Secure Web Pay).

ECheck Transactions

The following table displays Payment, Receiver, Authorization, Settlement, History, and Receipt data that could display with echeck or Validate/Validate+ transactions.

Card/Tab	Field	Description
Payment Information	Status	The current status of the transaction. Supported options include the following: • In-Progress - The transaction is in the process of settling. • Authorized - The customer's payment was authorized. To complete the sale, the item must be captured from the Transaction's Details page. • Complete - An echeck verification was performed via Validate or Validate+ and the results were positive (POS) or unknown (UNK). • Declined - The transaction was declined for reasons detailed in the Response Code and Response Description parameters. • Failed - An echeck verification was performed via Validate or Validate+ and the results were negative (NEG) or the transaction failed for reasons detailed in the Response Code and Response Description parameters. • Funded - An echeck item was funded to or from the merchant's bank account. • Ready - The transaction was received and is awaiting settlement. • Rejected - An echeck item was rejected or returned by the customer's financial institution. The merchant will not be funded fort he item. • Review - Transaction was unable to be settled due to a merchant configuration issue. Contact Customer Service to resolve the issue. • Settling - The echeck item has been originated and Forte is awaiting the settlement results. • Unfunded - A previously funded echeck item has been returned and funding was reversed. • Voided - The transaction was voided and the item will not be originated. • Unfunded - For debit transactions, funds have been removed from the merchant's bank account because of sale transaction returns or dispute losses. For credit transactions, funds have added to the merchant's bank account because of refund dispute losses and refund transaction returns.
	Action	The action the transaction performs. Supported options include the following: • Debit/Sale • Refund/Credit • Auth • Force • Verify
	Authorization Amount	The total authorization amount to be debited/credited. This amount can include the Subtotal, Tax, and Service Fee amounts.
	Customer/Company Name	The First and Last Name of the customer or the Company Name associated with the customer.
	Method	The payment method associated with the transaction. For echeck transactions, this field will always display the Dex eCheck logo.
	Last 4 Account Number	The last four digits of the customer's bank account number.
	Card Holder Name	The First and Last Name or Company Name of the cardholder.
	Routing Number	The semi-redacted routing number of the customer's bank.
	Issuer	The name of the customer's bank.
	Phone	The phone number of the customer's bank.
	Account Type	The type of bank account the customer is using for this transaction. Supported options include Checking or Savings.
	Location	The name and ID of the merchant's location.
Receiver Effective		The date when the transaction received an authorization response.
Details - Authorization	Status	The status of the transaction's authorization. Supported values include the following: • Authorized - The customer's payment was authorized. To complete the sale, the item must be captured from the Transaction's Details page. • Complete - eCheck verification was performed and the results were positive (POS) or unknown (UNK). • Declined - The transaction was declined for reasons detailed in the Response Code and Response Description parameters. • Failed - An echeck verification was performed via Validate/Validate+ and the results were negative (NEG) or the transaction failed for reasons detailed in the Response Code and Response Description. • Funded - The echeck item was funded to or from the merchant's bank account. • Ready - The transaction was received and is awaiting settlement. • Review - Transaction was unable to be settled due to a merchant configuration issue. Contact Customer Service to resolve the issue. • Settle - The echeck item has been funded to the merchant's bank account. • Unfunded - A previously funded echeck item has been returned and funding was reversed. Voided - The transaction was voided and the item will not be originated or settled.
	Transaction ID	A 36-character code that uniquely identifies the transaction.
	Response Code	The 3-digit response code returned with the transaction. For a list of transaction response codes, see Transaction Codes in Forte's Developer Documentation.
	Description	A text description of the authorization (e.g., approved, declined, etc.)
	Approval Code	The numeric authorization code generated for the transaction (e.g., 244234).
	Entry Class Code	The SEC code associated with the transaction. The following values are supported: • ARC • CCD • CIE • CTX • POP • POS • PPD • RCK • TEL • WEB For descriptions of these codes, see Using ACH and SEC Return Codes topic on Forte's Developer Documentation site.
	Source	The terminal hardware, software, or integration method used to connect to Forte (e.g., Direct Socket, VX520, etc).
	IP Address	The IP Address from where the merchant/partner submitted the transaction.
	Entered By	The name or API key of the user that created this transaction.
	Recurring Indicator	A boolean field indicating if this transaction is part of a schedule of recurring transactions.
	Verify Result	The 3-character code and description of a Validate/Validate+ result. NOTE: This field only displays for Verify Only transactions. Supported options include the following: • NEG:P15:HIGH RISK • NEG:P41:NEGATIVE INFO • UNK:P50:NO INFO • POS:P70:VALIDATED • POS:P71:LOW RISK APPROVAL • POS:P73:MEDIUM RISK APPROVAL • UNK:P80:PREAUTH • VENDOR BUSY • UNK:P90:PREAUTH • VENDOR UNAVAIL • UNK:P91:PREAUTH VENDOR ERROR • UNK:P92:PREAUTH SERVER UNAVAIL
History		Provides a dated and timestamped summary of all the events that have occurred with this transaction.
Receipt		Provides a detailed view of this transaction's receipt, including Line Items, XDATA 1-9, and other user-defined fields (e.g. Data Label 1-4 in Secure Web Pay).

Bank Account Owner Verification Transactions

The following table displays information that could display with Bank Account Owner Verification transactions.

Card/Tab	Field	Description
Verification Information	First Name	First Name of the Bank Account Owner
	Last name	Last Name of the Bank Account Owner
	Business name	Registered Business Name of the Bank Account Routing and Transit Number The TRN or routing number of the bank. This value is typically the first number listed at the bottom of the check.
	Issuer	The name of the customer’s bank
	Phone	The phone number of the customer’s bank.
	Account Type	The type of bank account the customer is using for this transaction. Supported options include Business Checking or Business Savings.
	Location	The name and ID of the merchant’s location.
Bank Account Owner Verification – Authenticate	Status	The status of the transaction’s authorization and the supported values include are as follows: Match No Match Conditional Match No Info
Bank Account Owner Verification – Authenticate	Transaction ID	A 36-character code that uniquely identifies the transaction
Response Details	An overall result code and description of the individual components provided from the request	A05 Overall Match A05 First and Last Name Match A05 Business Match A06 Partial Match N01 No Info U80 No Match U82 Preauth Error U84 Auth Timeout U85 Auth Error
	Authorization Number	N/A
	Source	The terminal hardware, software, or integration method used to connect to Forte (e.g., Direct Socket, VX520, etc.).
	Entered By	The name or API key of the user that created this transaction.
Verify Advice	Response Type	The result of the response type check, the following results are supported: O Overall Match M First and Last Name Match B Business Name Match N No Match P Partial Match U No Info
Verify Advice	Verify Advice	The result of the verify advice check. The following values are supported: 300 Valid but drawn on a contributor 301 Valid participant but not a an AOA contributor/ABA masked 302 Valid participant but not an AOA data unavailable 304 No name field populated 396 AOA matching is not available because account is in one of the following categories; closed, non-DDA or no known information 900 No account owner response requested or provided 901 No account owner response requested or provided
Pre Auth Result & Description	The following value in these fields provide the postential result and current state of the account ownership match provided by the verifying agent are as follows:
	POS	P60: Match
	CON	P75: Conditional Match
	NEG	P10: No Match
	UNK	P50: No Info P90: Preauth Vendor Unavailable P91: Preauth Vendor Error
	ERROR	P93: Error P94: Invalid Routing Number P95: Bad Account
Bank Account Owner Verification Details	The status displayed under the fields listed below will display with the transaction’s authorization. Supported values will include Match, No Match, Conditional Match and/or No Info
	First Name & Status	First Name of the Bank Account Owner
	Last Name & Status	Last Name of the Bank Account Owner
	Business Name & Status	Registered Business Name of the Bank Account

Create a Transaction from a Previous Transaction

The Add Transaction action gives you the ability to quickly create a new transaction using the same Location, Customer, and Payment Method settings as the previously processed transaction. This action is only available for previously created Debit/Sale, Credit/Refund, Auth Only credit card transactions and Debit/Sale, Credit/Refund, Auth Only, and Force echeck transactions. NOTE: This option is not available for transactions where the payment method (i.e., credit card) has expired. To create a transaction from a previous transaction, complete the following steps:

Search for the desired transaction by First Name, Last Name, Company Name, Trace Number, or Location ID, or use the applicable filters to narrow down the displayed search results.
Perform the Add Transaction action using one of two methods:
- From the Transactions Datagrid, click > Add Transaction.
- Access the Transaction's Details Screen and click Actions > Add Transaction.
The Add Transaction modal displays with the Location, Customer, and Payment Method data displayed. Select the type of transaction using the dropdown menu in the Action field. Supported values include the following:
- Debit/Sale
- Refund/Disbursement
- Authorize
- Force (eCheck only)
- External Authorization (Credit Card only)
- Verify (eCheck only)
If you'd like to include an Order Number and/or Reference ID for this transaction, click the More Options dropdown. The Order Number and Reference ID fields display.
Enter the subtotal amount in the Subtotal field. This field is required. NOTE: For Verify transactions, this field must be any value greater than $0.00.
Calculate the tax amount and enter it into the Tax field. This field is optional.
If you are a service-fee merchant or a merchant subscribed to the VISA Tax Program, a pre-populated Service Fee field displays beneath the Tax field. The Service Fee field only displays for service fee merchants. NOTE: Dex does not charge service fees for verify-only transactions.
As you enter values into the Subtotal, Tax, and, if applicable, Service Fee fields, Dex automatically updates the Total amount that displays in the lower-left corner of the modal.
Complete the remaining transaction fields:
1. For echeck transactions, use the dropdown menu in the Entry Class Code field to select the correct SEC code. Supported values include the following:
  - ARC
  - CCD
  - PPD
  - WEB
  If desired, enter the check number in the Check Number field.
2. For credit card transaction, enter the card's verification value in the CVV field (if required) and, if desired, the customer's billing ZIP or postal code in the Postal Code field.
After completing the required fields, click the Add Transaction button. Dex displays a modal indicating the transaction's status and, if applicable, a printable receipt. Click Done to return to the Transaction's Details Screen.

Capture Transactions

Captures enable merchants to collect the funds of a previously authorized transaction. The capture amount can be equal to the authorization amount of the transaction. A capture must be performed within the authorization/pre-authorization period (i.e., when the status of the transaction is In-Progress) for credit card and echeck transactions.

To capture a transaction, complete the following steps:

Search for the desired transaction by First Name, Last Name, Company Name, Trace Number, or Location ID or use the filters to narrow down the list of results.
Perform the capture action using one of two methods:
1. From the Transactions Summary Datagrid, click > Capture.
2. Access the Transaction's Details Screen and click Actions > Capture.
A Capture Transaction Message displays. Click the Capture button on the message to confirm the action. Dex returns you to the previous screen and changes the status of the transaction to In-Progress.

Printing a Transaction Receipt or Invoice

If you need to print a receipt or invoice for a transaction after submitting it, complete the following steps:

Access the Transactions Datagrid by clicking Transactions on the Dex main menu.
Search for the desired transaction by First Name, Last Name, Company Name, Trace Number, or Location ID or use the filters to narrow down the list of results.
Click the row on which the desired transaction displays. The Transaction's Details Screen displays.
Click the Receipt tab.
Click the Print Receipt dropdown button and select either Standard Receipt (available for credit and debit card transactions only) or Detailed Receipt. A browser window opens displaying the receipt or invoice.
Configure where and how you want to print the receipt and click Print on the browser window.

You can print a detailed receipt from the Transactions Datagrid for the following:

Debit/Sale
Auth
Refund/Credit
Force/External Auth

To print a detailed receipt for one of these transactions, click the ellipsis at the right of the Transactions Datagrid and click Print Detailed Receipt.

Reverse Transactions

A Reverse takes the original charge from a billing account and retracts it (e.g., reversed sales will have a disbursement or credit performed). Reverses are performed on transactions that are too late to void because the transaction has already been sent for settlement. In Dex, merchant users with the proper permissions can only reverse transaction amounts that are less than or equal to the original transaction amount. The following table displays what types of transactions you can reverse.

Method	Action	Status
Credit Card	Sale, Authorize, and Credit	Settled
Echeck	Sale, Authorize, Credit, and Force	Funded

To reverse a transaction, complete the following steps:

Search for the desired transaction by First Name, Last Name, Company Name, Trace Number, or Location ID or use the filters to narrow down the list of results.
Perform the reverse action using one of two methods:
1. From the Transactions Summary Datagrid, click > Reverse.
2. Access the Transaction's Details Screen and click Actions > Reverse.
A Reverse Transaction Confirmation Message displays. Click the Agree button.
Enter the amount you want to reverse. This amount must be less than or equal to the original transaction amount and cannot be a negative number.
Click the Reverse button on the Reverse Transaction Confirmation Message to confirm the action. Dex returns you to the previous screen and creates a new In-Progress transaction.

Resubmit Transactions

A Resubmit gives merchants the ability to create a new transaction using the original parameters of a transaction. Merchants can only resubmit Debit/Sale, Credit/Refund, and Auth Only credit card transactions in the Settled status or Debit/Sale, Credit/Refund, Auth Only, and Force echeck transactions in the Funded or Rejected/Unfunded statuses. Transactions created using an alternative method of payment (Apple Pay) are not enabled to resubmit.

To resubmit a transaction, complete the following steps:

Search for the desired transaction by First Name, Last Name, Company Name, Trace Number, or Location ID or use the filters to narrow down the list of results.
Perform the reverse action using one of two methods:
1. From the Transactions Summary Datagrid, click > Resubmit.
2. Access the Transaction's Details Screen and click Actions > Resubmit.
A Resubmit Confirmation Message displays. Click the Resubmit button on the Resubmit Message to confirm the action. Dex returns you to the previous screen and changes the status of the transaction to Ready.

Void Transactions

A Void is used to stop a transaction from originating (echecks) or going to settlement (credit cards) and for canceling holds on transactions that were previously authorized. You can only void a transaction once. The following table displays what types of transactions you can void.

Method	Action	Status
Credit Card	Sale, Authorize, Credit, and Pre-Auth	Ready, Authorized, and Review
Echeck	Sale, Authorize, Credit, and Force	Ready, Authorized, Review

Voiding Individual Transactions

To void an individual transaction, complete the following steps:

Search for the desired transaction by First Name, Last Name, Company Name, Trace Number, or Location ID or use the filters to narrow down the list of results.
Perform the void action by one of two methods:
1. From the Transactions Summary Datagrid, click > Void.
2. Access the Transaction's Details Screen and click Actions > Void.
A Void Confirmation Message displays. Click the Void button on the message to confirm the action. Dex returns you to the previous screen and changes the status of the transaction to Failed.

Voiding Transactions in Bulk

To perform a bulk void of transactions, complete the following steps:

Access and filter the Transactions Datagrid using the Status = Ready filter field. If necessary, use the other filters to further narrow down the list of results.
Click the checkboxes that display next to every transactions you want to void. You can also click the Select All button that displays next to the datagrid column headings. NOTE: Up to 100 transactions can be voided at a time. After clicking the eligible transactions, an activated Void button displays in the top-left corner of the datagrid.
Click the Void button. A Void Confirmation Message displays.
Click the Void button on the Void Confirmation Message. Dex displays a success message indicating how many of the transactions were successfully voided.
Click the Okay button to return to the Transactions Datagrid. The newly voided transactions display as Failed.

Integrations

Peripherals

Merchant.docs

Partner.docs

Merchant.docs

Merchant.docs

Partner.docs

First Time Users

Quick Start

Transactional

Customer data

Tutorials

Response Code

Code samples

Third Party Modules

Plugins & More

Drivers

Additional Support

Getting Started

Merchant.docs

Transactions

Create a Credit Card Transaction

Creating an eCheck Transaction

Search for a Transaction

Filtering the Transaction Display List

Viewing Transaction Details

Credit Card Transactions

ECheck Transactions

Bank Account Owner Verification Transactions

Create a Transaction from a Previous Transaction

Capture Transactions

Printing a Transaction Receipt or Invoice

Reverse Transactions

Resubmit Transactions

Void Transactions

Voiding Individual Transactions

Voiding Transactions in Bulk

On this page

Your benefits:

What happens next?

Get Connected to our Team

Simplifying IT for a complex world.

Platform partnerships

Services

Business Challenges

Digital Transformation

Security

Automation

Gaining Efficiency

Industry Focus

Simplifying IT
for a complex world.