status and status_reason:
Payload Example
Response Fields
Available Codes
Standard declines are listed below. Authentication-specific codes are covered in Incomplete Payments. The samedecline_code can arrive with more than one status or advice_code, depending on the processor and on what it returned, so always read the advice_code of the payment itself.
payment_method_disabled means PayNext never contacted the processor. The saved payment method can’t be charged—either the customer revoked its mandate, or neither the card nor its network token is usable. The message field tells the two apart. There is no processor decline behind it, so retrying the same payment method always produces the same result. Collect a new payment method instead. See Payment Methods.retry_via_another_processor means the decline came from the processor or its acquirer, not from the card, so the same card can succeed through a different processor. It can come with different decline codes, such as processor_blocked. To act on it automatically, route the payment to a second processor in a workflow. See Automatic Failover.Incomplete Payments
Payments that require customer authentication (Cash App, Venmo, cards with 3DS) can end asincomplete if the customer doesn’t finish the flow.
Response Example
For card payments with 3DS, additional context is available in the
three_d_secure object. See 3D Secure for details.Card network response codes
When a Visa or Mastercard issuer declines a card payment, the processor passes along the issuer’s two-character response code. PayNext reads that code and returns it to you as adecline_code and an advice_code.
How the networks classify declines
Both networks tell merchants which declines they may retry, and how often.- Visa puts every decline response code into one of four categories. Category 1 means the issuer will never approve the card, so you must not retry it. Categories 2 (cannot approve right now), 3 (payment details need correcting) and 4 (all other codes) allow up to 20 retries in 30 days. Source: Visa Core Rules and Visa Product and Service Rules, April 2026 edition, section 7.3.6.3.
- Mastercard names six codes (
04,14,15,41,43,54) that end a card-not-present payment for good: you must not retry it with the same card number and expiry date. For merchant-initiated payments, the issuer can also send a Merchant Advice Code:01means you should get updated card details first,02means you should wait at least 24 hours, and03or21mean you should stop. Source: Mastercard Transaction Processing Rules, June 2026 edition.
65 and 78, PayNext checks the card brand and maps each network’s meaning separately.
The network rules set the most you can retry. PayNext’s
advice_code can be stricter. For example, Visa puts 03, 59, 62 and 93 in Category 2, but PayNext returns do_not_try_again for them.Issuer will not approve the card (Visa Category 1)
Issuer will not approve the card (Visa Category 1)
Do not retry these payments with the same card. Ask the customer for a different payment method.
Issuer cannot approve right now (Visa Category 2)
Issuer cannot approve right now (Visa Category 2)
Visa allows a retry later, for example after the customer adds funds or the issuer’s systems recover.
Payment details need correcting (Visa Category 3)
Payment details need correcting (Visa Category 3)
A retry with the same details fails again. Collect corrected or new card details first. Mastercard also lists
54 among the codes you must not retry with the same card number and expiry date.Generic and Mastercard-specific codes (Visa Category 4)
Generic and Mastercard-specific codes (Visa Category 4)
Visa treats any code outside the first three categories as generic. Most codes here are sent only by Mastercard.