Parameters in Responses/Callbacks
You can enable additional parameters in the synchronous server responses and webhooks you receive.
You can enable the below in the synchronous responses and in the notifications to your notification URL as well. Please find below a list of the extra parameters you could include.
General parameters
| Parameter | Value |
|---|---|
| bin | BIN value |
| bin_country | Bin Country |
| payment_method | Payment method which is used in the transaction |
|
|
| card_type | You can enable 1 of the below 2 options for card_type
|
| currency | Currency e.g.: EUR |
| amount | Amount value |
| expiry_year | Expiry year other card. e.g. expiry_year=2029 |
| expiry_month | Expiry month of the card. e.g. expiry_month=07 |
| cardholder | Cardholder bank name |
3DS parameters
| Parameter | Value |
|---|---|
| 3dstatus | Status of 3DS. e.g. Verified/Attempted/Non3d/Incomplete/Not verified |
| 3dauthentication_status | We sent "Y" for success, "N" for failed, "A" for attempted, "R" for Rejected from bank and "U" not authenticated due to unknown reason |
| 3dauthentication_flow | The flow of the 3DS: e.g. frictionless_flow/challenge_flow |
| 3dProtocolVersion | Protocol version. e.g.: 2.2.0 |
| 3dtransactionStatusReasonMessage | A message only when 3DS is failed |
| 3dtransactionStatusReason | An error code only when 3DS is failed |
| 3dcardholderInformation | Additional information to Cardholder about the rejection |
| eci | (Electronic Commerce Indicator) is a value that shows whether and how a card transaction was authenticated with 3D Secure e.g.: 05, 06, 07 |
MPI parameters
| Parameter | Value |
|---|---|
| mpi_avv | (Authentication Verification Value): A cryptographic string generated by the card issuer after a 3D Secure authentication. It acts as a digital signature proving the cardholder was authenticated. The merchant passes this value in the final authorization request to secure the fraud liability shift. |
| mpi_ds_transaction_id | (Directory Server Transaction ID): A universally unique identifier (UUID) assigned by the card network's at the start of the 3DS process. It acts as the primary tracking number that links the merchant's authentication request, the issuer's response, and the final payment authorization together across the entire payment ecosystem. |
Initial Scheme Transaction ID
The Initial Scheme Transaction ID refers to the unique network identifiers generated by card schemes (such as Visa and Mastercard) during the first, authenticated transaction of a Credential on File (CoF) transaction. When a customer initially saves their card, the network returns these specific parameters (e.g., Visa's Transaction Identifier or Mastercard's Trace ID).
| Parameter | Value |
|---|---|
| banknet_date | Mastercard Settlement date |
| banknet_ref_number | Mastercard Financial Product Code and Banknet Reference |
| visa_transaction_id | Visa Transaction Identifier |
Scheme Transaction Identifier
| Parameter | Value |
|---|---|
| transaction_identifier | Transaction Identifier for Visa/Mastercard/AMEX. A Transaction Identifier is a unique reference value generated by a payment network (scheme) to track and trace a specific transaction throughout its lifecycle, as well as to link economically related transactions. Please see examples below:
|
Response example with enabled parameters
currency=EUR&transaction_identifier=MpEYnPP6SRqTFk-tjiPQYV&card_type=Mastercard&banknet_date=0817&banknet_ref_number=MAD8DHJIV&3dstatus=VERIFIED&3dauthentication_status=Y&&cardholder=Payabl+Test&
type=capture&amount=0.02&expiry_year=2029&bin_country=CYP&expiry_month=07&payment_method=1&
transactionid=299223801&bin=535456&orderid=Payabl-Test&first_time_customer=0×timestamp=1738224826&errorcode=0&
ccn_four=2917&errormessage=&3dProtocolVersion=2.2.0&3dauthentication_flow=frictionless_flow&eci=05&security=6ec4f44449d1dc0fa67e9016e85c474c93dcc8645428d226596d5a35270cba54Please contact your Client Relations Manager or our Technical support team to enable any of the above.
Updated 12 days ago
Did this page help you?