Skip to main content
When a payment isn’t approved, respCode and respText say why. The codes come from the processor the merchant’s MID is set up on, so the same reason has a different code on each one: respProc tells you which. Start from the situation below, then look the exact code up under Every code, by processor.
Handle answers by respStat first (A approved, B try again, C declined, E the gateway couldn’t complete it: see Reading a payment response). Use the codes to tell the customer why, and to decide whether asking for another card will help.

By what to do

The codes for the gateway’s own checks and the most common processors. – means that processor has no code for it.

Approved

Try again in a moment

respStat is B, or the processor or its link is briefly down. Look the order up first if you aren’t sure the first attempt failed, then send it once more.

Ask for another payment method

The card issuer said no. Sending the same card again won’t change that, and card brands charge for repeated attempts.

Check what was entered

Fix the request or the setup

Not the customer’s card: the request or the merchant’s setup needs attention. Don’t ask the customer for another card.

Recurring payments

Retrying a decline

  • B (try again): a temporary problem. Retry once after a few seconds; if the first attempt might have gone through, look the order up first (Inquire).
  • C (declined): don’t send the same card again in the moment. The card brands limit retries of a declined card: Visa charges for more than 15 attempts on one card in 30 days, and never approves some declines (lost or stolen card, closed account, fraud). Ask for another payment method instead.
  • Recurring payments: space retries out over days, not minutes, and stop when the code says to stop (see Recurring payments).
  • Follow the card brand’s advice when it’s given: declineCategory 1 means never retry this card; Mastercard’s merchAdviceCode says when to retry or to stop (see Reading a payment response). Mojo Payments’ own recurring billing follows it.

Every code, by processor

Each processor’s complete list, as it answers: respCode, the respStat it comes with, and respText word for word. Mojo Payments shows these unchanged.
Checked before the request reaches a processor: card number, amounts, the merchant’s setup, voids and refunds.
The processor Mojo Payments MIDs are usually set up on.
The same codes as North.
If you get a code that isn’t listed, email hello@paymentsmojo.com with the order id, the time, respProc, respCode and respText.