Transaction amount in US dollars. Amount may include any fees and taxes at are part of the transaction total but does not include the surcharge. Amount is after any discounts, coupons, or rebates have been applied.
The authorization code returned from the Merchant’s credit card processing capture process. The AuthCode is an optional field.
This is opaque data that is available for further data analytics and is also used during A/B Test-Implementation phases.
The ISO Numerical Country Code. See https://en.wikipedia.org/wiki/ISO_3166-1. This is an optional field and will default to 840/US.
The first 6 digits of credit card number. InterPayments never handles more than 8 digits and therefore is not in conflict with PCI requirements or guidelines.
The MID or Name value of the processor to use for calculating Transaction Fees. This field is optional when the Merchant has only one configured processor. In that case the single, configured processor is used. If multiple processors are configured then the processor field becomes a required field.
InterPayments calculated fee for making a credit card transaction (sent in response from API).
A Merchant orderId or unique identifier in the Merchant scope referencing the Order or Shopping Cart. This field is optional. If the mTxId is not known until the “sale” sequence, it may be passed at that time. If a mTxId is supplied during the transaction fee operation then the mTxId may be used to identify the transaction during the sale operation.
Zip code or the ISO State Code. See https://en.wikipedia.org/wiki/ISO_3166-2:US. There are cases when the region is optional.
A unique transaction identifier in the InterPayments system which refers to the persistence state of the Transaction Fee calculation.