Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Common raw card-scheme responses behind a declined transaction.
data.code carries a failure code and reason explains why. Codes prefixed SM_ map to the authorisation response returned by the issuer or card scheme, known as the raw acquirer response.
See SeerBit status codes for the full list, and verify a payment for how to read a result before fulfilling an order.
| Type | Raw Responses | Description |
|---|---|---|
| Cancelled | 00: Approved or completed successfully | The transaction was cancelled after being initially approved by the issuer. This can be due to various reasons, for example, if the shopper returns goods after purchase |
| Refused | 01: Refer to card issuer | The transaction was refused by the card issuer. The shopper should contact their bank for clarification. The shopper can try again after resolving the issue with their bank, or use another payment method |
| Refused | 03: Invalid merchant | The transaction was refused by the card issuer. The shopper should contact their bank for clarification. The shopper can try again after resolving the issue with their bank, or use another payment method |
| Refused | 04: Capture card / Pick-up | The card issuer requests to retain the card. This can be due to a suspected counterfeit or stolen card. This reason is used in an E-Commerce environment although it originates from a POS (Point Of Sale) environment |