These fields are required for Merchant Initiated (3RI) transactions when a cardholder is not present.
Field Name | Description | Condition | Field Definition |
|---|---|---|---|
ThreeRIIndicator | Indicates the type of 3RI request. Possible Values: 01 - Recurring transaction 02 - Installment transaction 03 - Add card 04 - Maintain card 05 - Account verification 06 - Split/delayed shipment 07 - Top-up 08 - Mail Order 09 - Telephone Order 10 - Trustlist status check 11 - Other payment NOTE: EMV® 3-D Secure version 2.1.0 supports values 01-05. Version 2.2.0 supports values 01-11. | Required for Merchant Initiated transactions. | N(2) |
Amount | Unformatted total transaction amount without any decimalization. Example: $100.00 = 10000, $123.67 = 12367, $.99 = 99 NOTE: Supports 3RI Device Channel in version 2.2.0 | Required for 02-NPA if 3DS Requestor AuthenticationIndicator = 02 or 03. | N(48) |
CurrencyCode | 3 digit numeric ISO 4217 currency code for the sale amount. NOTE: Supports 3RI Device Channel in version 2.2.0 | Required for 02-NPA if 3DS Requestor AuthenticationIndicator = 02 or 03. | N(3) |
PurchaseDate | Date of original purchase. Format: YYYYMMDDHHMMSS NOTE: If not passed, Cardinal will use current date. Required for recurring transactions. NOTE: Supports 3RI Device Channel in version 2.2.0 | Required for Recurring and Installment transactions. | AN(14) |
Installment | Indicates the maximum number of authorizations for installment payments. An integer value greater than 1 indicating the maximum number of permitted authorizations for installment payments. Example values accepted:
NOTE: Supports 3RI Device Channel in version 2.2.0 | Required for Recurring and Installment transactions. | N(3) |
RecurringEnd | The date after which no further recurring authorizations should be performed. Format: YYYYMMDD NOTE: Supports 3RI Device Channel in version 2.2.0 | Required for Recurring and Installment transactions. | N(8) |
RecurringFrequency | Integer value indicating the minimum number of days between recurring authorizations. A frequency of monthly is indicated by the value 28. Multiple of 28 days will be used to indicate months. Example: 6 months = 168 Example values accepted (31 days):
NOTE: Supports 3RI Device Channel in version 2.2.0 | Required for Recurring and Installment transactions. | N(4) |
ProductCode | Merchant product code. Possible Values: PHY - Goods/Service Purchase CHA - Check Acceptance ACF - Account Funding QCT - Quasi-Cash Transaction PAL - Prepaid Activation and Load NOTE: Supports 3RI Device Channel in version 2.2.0 | Required for Brazil. | AN(3) |
DeviceChannel | Determines the channel that the transaction came through. Possible Values:
| Required for Merchant Initiated transactions. | AN(10) |
MessageCategory | Identifies the message category for Payment or Non-Payment transaction. Set to NPA or Merchant Profile configured. Possible Values: 01 - PA 02 - NPA NOTE: EMV® 3-D Secure version 2.1.0 supports values 02. Version 2.2.0 supports values 01 and 02. This value can be set in the API on each transaction or within the client's Merchant Id. | Required for Merchant Initiated transactions. | N(2) |
AlternatePriorAuthenticationData | This field carry data that the ACS can use to verify the authentication process. DS Transaction ID of the Initial or first recurring payment transaction must be passed on the field. | Required by Mastercard for 3RI transactions | AN(2048) |
AlternatePriorAuthenticationDate | Date and time in UTC of the prior cardholder authentication. Format YYYYMMDDHHMM | Required by Mastercard for 3RI transactions | N(12) |
AlternatePriorAuthenticationRef | This data element contains a ACS Transaction ID for a prior authenticated transaction For example, the first recurring transaction that was authenticated with the cardholder | Required by Mastercard for 3RI transactions | AN(36) |