test-data

Along with the four-part key, the XML Batch file format uses additional attributes. The table on this page provides the definitions for the additional attributes as well as examples of their use.

This page describes the data that is returned from validation events that can occur when processing using the Browser Post API.

North Developer provides various resources to assist with developing payment integrations, including the EPX Data Dictionary. Use the tiles below to browse some of the most commonly used chapters of the Data Dictionary.

This page describes the fields that can be used in a transaction request to the EPX Hosted Pay Page or Browser Post API.

Get test payment values that can be used in North's UAP/Test environment to simulate various accounts using credit card, credit card track data, and ACH information.

This page outlines the request fields specific to MasterCard Money Transfer SMS Funding and Payment transactions.

The EPX Four-Part Key consists of four attributes: CUST_NBR, MERCH_NBR, DBA_NBR, and TERMINAL_NBR. The values for these fields are required to process transactions with the EPX platform in both test and production environments. Definitions for these attributes, as well as examples of how they are used shown below.

North Developer provides various resources to assist with developing payment integrations. These include testing resources such as test credit card data and codes that trigger transactions responses that are returned in the production environment.

This page describes the option for the EPX processor to calculate fees on the back end and apply them to the total amount of the sale or authorization request.

This page describes the fields that can be used in a transaction request to the EPX payment gateway.

When processing transactions, credit card networks return various codes in response to transaction requests. North provides those codes to assist with payment software development for credit card and PIN debit transactions.

This page describes the fields that are returned in the response from EPX after running a transaction.

This page describes the fields that can be included in Verified by Visa (VbV) or Mastercard SecureCode transaction requests for an additional layer of payment security.

This page outlines the request fields specific to Visa Debt Repayment transactions.

This section outlines the request and response fields specific to VMT transactions, Account Funding Transaction (AFT), Watch List Screening (WLS), and Original Credit Transaction (OCT).

When testing payment integrations, the transaction amount value can be used to trigger various credit card response values that may be encountered when processing in the production environment. North Developer provides these values for use in the UAP/Test environment.