MerchantID

Message version.

Values accepted:

• 2.0

Notes:

• Fixed length of 12 characters (only characters (A..Z, a..z) and digits (0..9) are allowed, no special characters like whitespace, underscore...)
• If the number of characters entered is lower than 12, BNP will complete, starting from the left side, with "0" (Example : 000018279568)

Card scheme specific transaction ID required for subsequent credential-on-file payments, delayed authorizations and resubmssions.

Mandatory: CredentialOnFile – initial false – unschedule MIT / recurring

Resubmission

A merchant performs a re-submission in cases where it requested an authorization, but received a decline due to insufficient funds; however, the goods or services were already delivered to the cardholder.

Merchants in such scenarios can resubmit the request to recover outstanding debt from cardholders.

Reauthorization

A merchant initiates a re-authorization when the completion or fulfillment of the original order or service extends beyond the authorization validity limit set by Visa.

There are two common re-authorization scenarios:

• Split or delayed shipments at eCommerce retailers. A split shipment occurs when not all the goods ordered are available for shipment at the time of purchase. If the fulfillment of the goods takes place after the authorization

validity limit set by Visa, eCommerce merchants perform a separate authorization to ensure that consumer funds are available.

• Extended stay hotels, car rentals, and cruise lines. A re-authorization is used for stays, voyages, and/or rentals that extend beyond the authorization validity period set by Visa.

DelayedCharges

NoShow

Indicates the type of channel interface being used to initiate the transaction.

Values accepted:

• Browser

• App

• 3RI

If not present the value Browser is implied.

ans..256

Indicator to request an account verification (aka zero value authorization). If an account verification is requested the submitted amount will be optional and ignored for the actual payment transaction (e.g. authorization).

Values accepted:

• Yes

threeDSPolicy

JSON

O

Object specifying authentication policies and excemption handling strategies

threeDSData

JSON

C

Object detailing authentication data in case authentication was performed through a third party or by the merchant

priorAuthenticationInfo

JSON

O

Prior Transaction Authentication Information contains optional information about a 3-D Secure cardholder authentication that occurred prior to the current transaction

browserInfo

JSON

M

Accurate browser information are needed to deliver an optimized user experience. Required for 3-D Secure 2.0 transactions.

accountInfo

JSON

O

The account information contains optional information about the customer account with the merchant. Optional for 3-D Secure 2.0 transactions.

billToCustomer

JSON

C

The customer that is getting billed for the goods and / or services. Required unless market or regional mandate restricts sending this information.

shipToCustomer

JSON

C

The customer that the goods and / or services are sent to. Required (if available and different from billToCustomer) unless market or regional mandate restricts sending this information.

billingAddress

JSON

C

Billing address. Required for 3-D Secure 2.0 (if available) unless market or regional mandate restricts sending this information.

shippingAddress

JSON

C

Shipping address. If different from billingAddress, required for 3-D Secure 2.0 (if available) unless market or regional mandate restricts sending this information.

credentialOnFile

JSON

C

Object specifying type and series of transactions using payment account credentials (e.g. account number or payment token) that is stored by a merchant to process future purchases for a customer. Required if applicable.

merchantRiskIndicator

JSON

O

The Merchant Risk Indicator contains optional information about the specific purchase by the customer

URLNotify

an..256

M

The merchant URL that receive asynchrounous reqeusts during the authentication process

MAC

• HMAC Authentication (Request)
• HMAC Authentication (Notify)

MID

Status

a..20

M

Status of the transaction.

Values accepted:

• AUTHENTICATION_REQUEST

• PENDING

• FAILED

RefNr

an12

M

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional settlement file we cannot add the additional payment data.

Notes:

• Fixed length of 12 characters (only characters (A..Z, a..z) and digits (0..9) are allowed, no special characters like whitespace, underscore...)
• For AMEX : RefNr is mandatory
• If the number of characters entered is lower than 12, BNP will complete, starting from the left side, with "0" (Example : 000018279568)

versioningData

JSON

M

The Card Range Data data element contains information that indicates the most recent EMV 3-D Secure version supported by the ACS that hosts that card range. It also may optionally contain the ACS URL for the 3-D Secure Method if supported by the ACS and the DS Start and End Protocol Versions which support the card range.

threeDSLegacy

JSON

M

Object containing the data elements required to construct the Payer Authentication request in case of a fallback to 3-D Secure 1.0.

schemeReferenceID

ans..64

C

Card scheme specific transaction ID required for subsequent credential-on-file payments, delayed authorizations and resubmssions.

card

JSON

M

Card data

ipInfo

JSON

O

Object containing IP information

threeDSData

JSON

M

Authentication data

resultsResponse

JSON

C

In case the authentication process included a cardholder challenge additional information about the challenge result will be provided.