Maintenance Work Notice!
We will carry out maintenance work on this documentation on Tuesday, 15.06.2021 between 3 pm and 4 pm CEST. Thank you for your understanding.
Paygate response codes are 8 digits and are constructed accordering to the syntax described below.
Format: N8, (
206 3DS credit card adapater for authorization protocol GICC
0203 Card brand does not support 3DS
Operation completed succesfully.
Operation failed and data that were processed might be lost.
Continue / Transient
Operation is not completed. Final status will be transferred asynchrounous.
EMV 3DS Info
Intermediate states in the EMV 3DS sequence
The category code is a 3 digit value designating the payment adapater or payment protocol. For 3DS 2.0 those category codes will be in the range of 100 to 299 depending on the card connector.
|2||Message received invalid|
|2||Message version number not supported|
|2||Sent messages limit exceeded. Only used for PReq|
|Required element missing|
|Critical message extension not recognized|
|Format on one or more elements is invalid according to the specs|
|Duplicate data element|
|Transaction id is not recognized|
|Data decryption failure|
|Access denied, invalid endpoint|
|ISO code is not valid|
|Transaction data is not valid|
|Merchant category code is not valid for payment system|
|Serial number is not valid|
|Transaction timed out|
|Transient system failure|
|Permanent system failure|
|System connection failure|
|UnionPay specific error code. Present when Data fields relevance check failed (ECI value and AV appearance are inconsistent with transaction status).|
|UnionPay specific error code. Present when duplicated transaction ID (Transaction ID should be unique for each AReq request).|
|3DS 2.0 is not supported by this card. The merchant has to follow the fallbacl process.|
|Invalid parameter BROWSERINFO|
|Invalid parameter BILLINGADDRESS|
|3DS 2.0 versioning successful|
|Authentication response --> challenge mandated|