Customer onboarding
Onboarding overview
Card management
Tokenization and digital wallet
Sensitive card information
3DS - authentication of online payments
Strong customer authentication (SCA)
Spend control
Address verification service
Click to Pay
Communication
Customer communication strategy
Resources
Trust center
Response codes
After the authorisation processing is concluded, Mynt generates a response that directs the merchant on how to proceed with the transaction. If validations are successful and the authorisation is approved, the purchase can be finalised. If the authorisation is declined, the merchant needs to discontinue the purchase or ask for an alternative payment method.
Response codes & description
| Response Code | Description | Use Case | User Friendly Message |
|---|---|---|---|
| 0 | Approved/ Successfully completed | Approved response code. The transaction is successfully approved for the requested amount. | N/A |
| 1 | Refer to Card Issuer | Decline response code. Outdated code that can be used by issuer if they wish the merchant to reach out to the issuer for further verification, however this service is by default no longer used. | Transaction declined for unknown reason. Please contact support if you think there has been an error. |
| 1A | Additional Customer Authentication Required | Decline response code. Authentication is required. If the transaction falls under PSD2 regulations and was not processed through 3D Secure, retry with 3D Secure. (Applicable only in the European region.) | 3DS authentication needed for your transaction. Please try again with 3DS. |
| 3 | Invalid Merchant | Decline response code. This is used if the merchant is using an acquirer BIN that is not known, i.e. the merchant is not registered to a valid acquirer. Could happen if the acquirer BIN is new and not yet captured. | Transaction declined for unknown reason. Please contact support if you think there has been an error. |
| 4 | Pick up card | Decline response code. This is used when authorisation is declined because card has been closed due to fraud. | Transaction declined due to closed card |
| 5 | Do not honor | Decline response code. This is a generic decline code that does not specify why it is declined. E.g. if card has a temporary block this response code is used. | Transaction declined for unknown reason. Please contact support if you think there has been an error. |
| 5C | Issuer unavailable | Decline response code. The issuer blocks a transaction based on the spend controls set on the card | Transaction declined as transaction type is not allowed. |
| 7 | Pick up card, special condition | Decline response code. This is used when authorisation is declined because card has been closed due to fraud (IMPORTANT: no mention of fraud can be made to the end user!). | Transaction declined due to closed card |
| 10 | Approved for partial amount | Approved response code. This response code is used to indicate a partial approval. Can only be used if the merchant has indicated in the request that they will accept a partial approval. | Approved |
| 12 | Invalid Transaction | Decline response code. This response code is used when data is missing or incorrect in the authorisation message is preventing processing of the authorsation. Examples can be missing security values or non-existing currency code. | Transaction declined for unknown reason. Please contact support if you think there has been an error. |
| 13 | Invalid Amount | Decline response code. This response code is used when the amount of the transaction is not acceptable. Example use cases include if reversal amount is not matching with the original authorisation amount or adjustment is bigger than the original authorisation amount. | Transaction declined due to invalid or incompatible amount. |
| 14 | Invalid card number | Decline response code. This response code is used when the card number from the merchant is nor existing and transaction is declined due to that. This can happen if cardholder makes a typo when buying online or if there is fraudulent attempt to guess valid card numbers ("BIN attack"). | Transaction declined due to invalid card details. |
| 15 | No Such Issuer | Decline response code. First 8 digits of the account number do not relate to an issuing identifier. Reattempt not permitted with same PAN or token. | Transaction declined for unknown reason. Please contact support if you think there has been an error. |
| 30 | Format error | Decline response code. This response code is used when the authorisation message does not comply with format requirements of the card scheme. | Transaction declined for unknown reason. Please contact support if you think there has been an error. |
| 41 | Lost card pick up | Decline response code. This is used when authorisation is declined because card has been closed as lost. | Transaction declined due to closed card. |
| 43 | Stolen card pick up | Decline response code. This is used when authorisation is declined because card has been closed as stolen. | Transaction declined due to closed card. |
| 46 | Contract closed | Decline response code. This response code is used when the card number from the merchant is nor existing and transaction is declined due to that. This can happen if cardholder makes a typo when buying online or if there is fraudulent attempt to guess valid card numbers ("BIN attack"). | Transaction declined due to invalid card details. |
| 51 | Not sufficient funds | Decline response code. This is used when authorisation is declined when there is not sufficient available amount on the card. | Transaction declined due to insufficient funds. |
| 54 | Expired card | Decline response code. This is used when authorisation is declined due to that the card has expired. In case of an online transaction this error is also returned when the expiration date provided to the merchant is incorrect. | Transaction declined due to expired card. |
| 55 | PIN incorrect | Decline response code. This is used when the PIN entered by the cardholder is incorrect. | Transaction declined due to incorrect PIN. |
| 57 | Transaction not allowed for cardholder | Decline response code. This is used if the transaction type is not allowed for the card or is not known. | Transaction declined as transaction type is not allowed. |
| 58 | Transaction not allowed for merchant | Decline response code. This is used if the transaction type is not allowed for the card or is not known. | Transaction declined as transaction type is not allowed by merchant. |
| 59 | Suspected fraud | Decline response code. This is used when the transaction is flagged as fraud by the fraud validation process. (IMPORTANT: no mention of fraud can be made to the end user!) | Transaction declined. |
| 61 | Exceeds withdrawal amount limit | Decline response code. This is used when authorisation is declined due to a spend control. | Transaction declined due to spend controls. |
| 62 | Restricted card | Decline response code. This is used e.g. in cases when merchant has the card token saved ("on file") and tries to make a charge but the token is suspended. | Transaction declined due to restricted card. |
| 65 | Activity count limit exceeded | Decline response code. This is used when a spend control counter prevents usage. | Transaction declined due to spend controls. |
| 68 | Response received too late | Decline response code. This is used between card management and fraud monitoring system, when response from fraud monitoring system has taken too long and card management system responds on behalf. | Transaction declined due to communication error. Please retry. |
| 70 | Invalid transaction; contact card issuer | Decline response code. Visa-specific code used when a contactless transaction is declined due to a usage counter limit and/or required PIN data is not included in the authorization request. | Transaction declined for unknown reason. Please contact support if you think there has been an error. |
| 75 | PIN tries exceeded | Decline response code. This is used when authorisation is declined because the cards PIN counter(s) are locked and need to be released before the card can be used again. | Transaction declined as PIN attempts have been used up. Please contact support to reset. |
| 76 | Wrong PIN, number of PIN tries exceeded | Decline response code. The cardholder has exceeded the allowed number of incorrect PIN attempts. | Transaction declined as PIN has been entered incorrectly multiple times. Please contact support. |
| 78 | Record not found | Decline response code. This is used if the transaction type is not allowed for the card or is not known. | Transaction declined as transaction type is not allowed. |
| 81 | Foreign network error | Decline response code. This is solely used by card scheme in advises to indicate that there has been an error in the network. | Transaction declined due to communication error. Please retry. |
| 82 | Time-out at issuer system / Bad CVV (VISA) | Decline response code. This is used by card scheme during stand in processing and CVV security value validation fails at card scheme. | Transaction declined due to validation failure. This could be due to terminal being offline. |
| 86 | Cannot verify PIN | Decline response code. This used by card scheme during stand in processing when PIN validation fails or can't be done at card scheme. | Transaction declined due to PIN validation failure. This could be due to terminal being offline. |
| 91 | Issuer unavailable | Decline response code. This is used between card management and external ledger system, when response from external system has taken too long and is therefore issuer is deemed unavailable. | Transaction declined due to communication error. Please retry. |
| 93 | Cannot be completed, violation of law | Decline response code. Used for regulatory blocks, e.g., gambling, non-opt-in CNP, or missing second-factor auth for domestic e-commerce. | Transaction declined for unknown reason. Please contact support if you think there has been an error. |
| 94 | Duplicate transaction | Decline response code. This is used when a merchant re-sends an authorisation that has already been processed and is ignored. | Transaction declined due to communication error. Please retry. |
| 95 | No authorisation to match | Decline response code. This is used in cases where it is required that the authorisation message can be matched to a previous authorisation message. | Transaction declined due to communication error. Please retry. |
| 96 | System malfunction | Decline response code. This is used when there is a system malfunction. | Transaction declined due to communication error. Please retry. |
| 9G | Blocked by cardholder / contact cardholder | Decline response code. Cardholder-initiated block; issuer declines authorization and requests contact with cardholder. | Transaction declined for unknown reason. Please contact support. |
| N0 | Issuer unavailable | Decline response code. Used when Visa forces single-request Stand-In Processing, converting 91 or 96 to N0. | Transaction declined for unknown reason. Please contact support if you think there has been an error. |
| N7 | CVC is wrong | Decline response code. A Visa authorization request did not pass CVV2 verification. It is typically used in Card-Not-Present (CNP) transactions when the CVV2 provided by the cardholder does not match the issuer's records. | Transaction declined due to incorrect security code (CVV2). |