Supplementary Data
Direct API allows you to pass additional data in transactions. The data may include industry data relating to airline, healthcare, or data related to the transaction (internet, order, or even custom data). The supplementary data you pass for a transaction is stored on the ANZ eGate payment gateway against that transaction.
Contact your payment service provider to check if providing such data is supported for your acquirer. The transaction operations that support the data, and the mandatory data fields required to process the transaction depend on your acquirer.
Please use the navigation menu for details on individual use cases for supplementary data.
Supplementary Data Type | Description |
---|---|
Account Funding Transactions | Transactions that involve debiting money from one account to credit another account are referred to as Account Funding Transactions (AFT) in your payment service provider parlance. |
Acquirer Custom Data | Acquirer custom data includes any additional information requested by the acquirer, which cannot be passed using other available data fields. |
Airline Data | Airline data includes details about, for example, flights, booking reference, itinerary, passenger details, and ticket details. |
Cruise Data | Cruise data includes information about the cruise and passengers on the cruise. It can also include data relating to services provided by other industries, such as airline or car hire, if they have been purchased as part of a cruise package. |
Customer Internet Data | Customer Internet data includes information about the source of the eCommerce transaction. For example, payer's email, IP address, or hostname. |
Debt Repayment Data | Debt repayments are transactions that are used to pay off debt. |
Healthcare Data | Healthcare data includes item details for healthcare purchases such as approved vision, dental, prescription, or other (clinic-related purchases). |
High-Risk Securities and Cryptocurrency Indicator Data | High-risk securities indicator only applies to merchants with Merchant Category Code (MCC) 6211 (Securities—Brokers/Dealers) processing Mastercard or Maestro card transactions. |
Level 2 and 3 Data | A credit card transaction can be submitted with three levels of transaction data: Level 1, Level 2, and Level 3. Each level is defined by the amount of information provided to process the transaction. |
Merchant Custom Data | Merchants can include custom transaction data for reporting and analysis that cannot be passed using other available data fields. Custom data fields are returned in the response. |
Order and Line Item Data | Order and line item data includes information about the order and the line items that are contained in the order. |
Risk Custom Data | Risk custom data includes any additional information requested by third-party risk assessment providers which cannot be passed using other available data fields. |
Statement Descriptor Data | Statement descriptor data, also known as dynamic descriptor data, includes contact information that you provide for printing on the account statements of a payer. |