All transactions in the platform are executed asynchronously, that is, once you request a new Transaction it is registered as
pending and sent to the execution pipeline. Whenever the transaction state changes a new Postback is sent and the
transaction.status field gets updated.
You may check the
state.additionalData field from the last
transaction.states entry to get specific details about the transaction failure.
All cards transactions are internationally standardized using ISO 8583. Whenever a Card transaction is processed, a Result Code is emitted both on the POS machine and the Web Gateways. This code is used to identify possible scenarios where the physical or virtual cards may not be working.
VISA Response Codes
|03||Establishment not registered|
|07||Special Condition ( cancelled / stolen card)|
|10||Invalid unblock code|
|12||Transaction no permitted to this establishment|
|31||Establishment not in environment|
|41||Reverse Validity Date / Embedded data differ from the registration|
|54||Card out-of-date (invalid)|
|55||Invalid or unregistered password|
|56||Card does not exist|
|57||Transaction cancelled (or already cancelled)|
|59||Account has pending debits (cardholder)|
|62||Invalid session key|
|65||Overlimit permitted quantity exceeeded|
|84||Invalid dealer / merchant|
|85||Query not authorized|
|94||Transaction already registered|
|99||Original transaction not found / Parameter error|
Attempts of card transactions may get flagged as a suspicious activity or attempted fraud. In this case, you may get errors other than the 55 even with the correct PIN Code. Contact the consumer to ensure that the card has not been stolen and open a ticket with the Help Desk.
For more information, refer to the official Visa Request and Response Codes developer guidelines.
Updated 2 months ago