Response Details

Upon completion, the transaction details will be sent back to the defined URL as hidden fields:

Field Name	Description	Value
`approval_code`	Approval code for the transaction. The first character of this parameter is the most helpful indicator for verification of the transaction result.	`Y` indicates that the transaction has been successful, `N` indicates that the transaction has not been successful, `?` indicates that the transaction has been successfully initialized, but a final result is not yet available since the transaction is now in a waiting status. The transaction status will be updated at a later stage.
`oid`	Order ID, if not defined in the request, the Gateway generates it automatically	e.g. C-2101f68a-45e9-4f3c-a6da-1337d5574717
`refnumber`	Reference number	-
`status`	Transaction status	`APPROVED`, `DECLINED` (by authorisation endpoint or due to fraud prevention settings),`FAILED` (wrong transaction message content/parameters, etc.) or `WAITING` (asynchronous Alternative Payment Methods)
`txndate_processed`	Time of transaction processing	-
`ipgTransactionId`	Transaction identifier assigned by the Gateway, e.g. to be used for a Void	-
`tdate`	Identification for the specific transaction	-
`fail_reason`	Reason the transaction failed	-
`response_hash`	Hash-Value to protect the communication (see a note here)	-
`processor_response_code`	The response code provided by the backend system.	Note that response codes can be different depending on the used payment type and backend system. While for credit card payments, the response code `00` is the most common response for an approval, the backend for giropay transactions for example returns the response code `4000` for succesful transactions.
`fail_rc`	Internal processing code for failed transactions	-
`terminal_id`	Terminal ID used for transaction processing	-
`ccbin`	6 digit identifier of the card issuing bank	-
`cccountry`	3 letter alphanumeric ISO code of the cardholder’s country	e.g. `USA`, `DEU`, `ITA`, etc. Filled with `N/A` if the cardholder’s country cannot be determined or the payment type is not credit card
`ccbrand`	Brand of the credit or debit card	`MASTERCARD`, `VISA`, `AMEX`, `DINERSCLUB`, `JCB`, `CUP`, `CABAL`, `MAESTRO`, `RUPAY`, `BCMC`, `SOROCRED`. Filled with `N/A` for any payment method which is not a credit card or debit card.

For 3-D Secure transactions only:

Return code indicates the classification of the transaction:

Field Name	Description
`response_code_3dsecure`	1 – Successful authentication (VISA ECI 05, MasterCard ECI 02) 2 – Successful authentication without AVV (VISA ECI 05, MasterCard ECI 02) 3 – Authentication failed / incorrect password / authentication rejected by DS or ACS (authorization transaction declined by the Gateway) 4 – Authentication attempt (VISA ECI 06, MasterCard ECI 01) 5 – Unable to authenticate / DS not responding (VISA ECI 07) - relevant for 3DS 1.0 6 – Unable to authenticate / ACS or DS not responding (VISA ECI 07) 7 – Cardholder not enrolled for 3-D Secure (VISA ECI 07) - relevant for 3DS 1.0 only 8 – Invalid 3-D Secure values received

Field Name

Description

response_code_3dsecure

1 – Successful authentication (VISA ECI 05, MasterCard ECI 02)
2 – Successful authentication without AVV (VISA ECI 05, MasterCard ECI 02)
3 – Authentication failed / incorrect password / authentication rejected by DS or ACS (authorization transaction declined by the Gateway)
4 – Authentication attempt (VISA ECI 06, MasterCard ECI 01)
5 – Unable to authenticate / DS not responding (VISA ECI 07) - relevant for 3DS 1.0
6 – Unable to authenticate / ACS or DS not responding (VISA ECI 07)
7 – Cardholder not enrolled for 3-D Secure (VISA ECI 07) - relevant for 3DS 1.0 only
8 – Invalid 3-D Secure values received

Credential-on-file transactions only:

Field Name	Description
`schemeTransactionId`	Returned in the response by a scheme for stored credentials transactions to be used in subsequent transaction requests as a reference

For Currency Conversion transactions only:

Field Name	Description
`dcc_foreign_amount`	Converted amount in cardholder home currency. Decimal number with dot (.) as a decimal separator
`dcc_foreign_currency`	ISO numeric code of the cardholder home currency. This transaction is performed in this currency.
`dcc_margin_rate_percentage`	Percent of margin applied to the original amount. Decimal number with dot (.) as a decimal separator.
`dcc_rate_source`	Name of the exchange rate source (e.g. Reuters Wholesale Inter Bank)
`dcc_rate`	Exchange rate. Decimal number with dot (.) as a decimal separator.
`dcc_rate_source_timestamp`	Exchange rate origin time. Integer - Unix timestamp (seconds since 1.1.1970)
`dcc_accepted`	Indicates if the card holder has accepted the conversion offer (response value ‘true’) or declined the offer (response value ‘false’).

For iDEAL transactions only:

Field Name	Description
`accountOwnerName`	Name of the owner of the bank account that has been used for the iDEAL transaction
`iban`	IBAN of the bank account that has been used for the iDEAL transaction
`bic`	BIC of the bank account that has been used for the iDEAL transaction

For SEPA Direct Debit as part of the Local Payments offering:

Field Name	Description
`mandateReference`	Mandate reference as returned for the first direct debit transaction
`mandateDate`	Date of the initial direct debit transaction as returned for the first transaction

Validity & Errors

Additionally when using your own error page for negative validity checks (full_bypass=true):

Field Name	Description
`fail_reason_details`	Comma separated list of missing or invalid variables. Note that ‘fail_reason_details’ will not be supported in case of payplus and fullpay mode.
`invalid_cardholder_data`	true – if validation of card holder data was negative. false – if validation of card holder data was positive but transaction has been declined due to other reasons.