Payment Declined With Code 12: Twelve Checks Before Charging the Customer Again

A code 12 displayed in your screen is not a universal diagnosis. Code meaning depends on the gateway, issuer, transaction type, and sometimes an integration layer in between. First open the provider documentation and the full transaction record rather than interpreting the number from an unofficial list.

Check, in order: transaction ID, whether this is new or retry, amount and currency, test or production environment, operation type, terminal details, authorization expiry, required authentication, duplicate order identifier, timeout between site and gateway, gateway transaction state, and whether a failure notification reached the customer. Each check closes a different risk.

Offer another payment only when the gateway clearly reports a decline. When status is unknown, create a review instead of charging again. This prevents double charges, poor customer experience, and manual refunds.

Source

PCI Security Standards Council