Shopify added a new reason code to its GraphQL Admin API on November 4 that tells subscription apps when a card processor has refused to accept any more retries on a saved card. Starting with API version 2027-01, a revoked customer payment method can come back with the reason RETRY_DECLINED, and Shopify’s developer changelog tells app builders to treat it as a sign that the buyer needs a different payment method. Earlier API versions still report these cases as TOO_MANY_CONSECUTIVE_FAILURES.
Stores that bill subscriptions through Authorize.Net Automated Recurring Billing (ARB) or NMI’s Recurring module do not get that flag from Shopify. They need the same discipline in their own setup, and the two gateways handle a failed recurring charge in quite different ways. This guide covers what each gateway documents, the decline codes that mean stop, and where a store or developer can pause billing until the customer supplies a new card.
What Visa’s rules say about retrying a decline
Visa sorts issuer decline codes into four categories in Table 7-2 of the Visa Core Rules and Visa Product and Service Rules (April 18, 2026 edition, section 7.3.6.3). Category 1, “Issuer will never approve,” covers codes such as 04 (pick up card), 14 (invalid account number), 41 (lost card), 43 (stolen card), 46 (closed account) and R0, R1 and R3, the stop payment and revocation orders. After a Category 1 response, Visa says a merchant “must never resubmit” an authorization or account verification for the same payment credential.
Categories 2, 3 and 4 cover temporary problems such as insufficient funds, data errors such as an expired card, and generic codes. Visa permits up to 20 reattempts in 30 days for those. Section 1.7.2.1 of the same rules adds that a merchant retrying after a decline must not intentionally manipulate data from the original request, such as the merchant category code or the e-commerce indicator. Payment companies including Adyen describe Visa charging excessive retry fees when those limits are broken.
For an autoship brand, a Category 1 decline on a monthly renewal means the card on file is finished. Charging it again next month, or the next night, breaks the rule.
How Authorize.Net ARB handles a failed payment
ARB submits scheduled subscription payments at about 2:00 a.m. Pacific time on each billing date, according to Authorize.Net’s recurring billing documentation. A subscription can be Active, Suspended, Terminated, Canceled or Expired.
Authorize.Net documents several situations that suspend a subscription:
- The first payment in a new subscription is declined, rejected or returns an error.
- The first payment after the subscription is edited, for example with new card or shipping details, is declined, rejected or returns an error.
- An active subscription receives an Account Closed (ACL) or Contact Card Holder (CCH) response, which Authorize.Net’s ARB support article says suspends it.
The same support article says a suspended subscription must be reactivated before the next scheduled payment or it is terminated, and a terminated subscription cannot be revived. Trying to reactivate before the payment information is updated produces an error. Authorize.Net does retry recurring transactions that hit internal gateway errors until they process, but its documentation does not describe ARB re-running a card decline on its own.
The exception is a legacy feature called Automatic Retry. Authorize.Net’s Automatic Retry article says it can no longer be turned on for new accounts, and accounts that enabled it cannot switch it off. With Automatic Retry, a failed payment suspends the subscription indefinitely rather than terminating it, and the gateway retries the failed payment only after the merchant updates the payment details and reactivates the subscription. It does not bill twice for intervals missed while the subscription sat suspended.
Where ARB tells you something failed
ARB can send a Failed Transaction Notice, a Subscription Suspension email and a Subscription Termination email, which are switched on in the Merchant Interface under Recurring Billing and Configure ARB Email Notifications. Developers can subscribe to the webhook events net.authorize.customer.subscription.failed, .suspended and .terminated, listed in Authorize.Net’s webhooks reference.
Because ARB itself does not hammer a declined card, the bigger risk in an ARB setup usually sits in code around it. A cart plugin, subscription app or custom script that reacts to a failed-payment notice by charging the stored customer profile again, or by reactivating a suspended subscription without new card details, can produce exactly the repeat attempts Visa prohibits. Developers should check what their integration does when one of those webhooks arrives.
Account Updater on Authorize.Net
Authorize.Net’s Account Updater checks card details stored in subscriptions and updates them, running once a month. Its results can be pulled through the getAUJobSummaryRequest and getAUJobDetailsRequest API calls. An updated card number or expiry date can turn what would have been a decline into an approval. A closed account has no new details to pull, and in ARB the ACL response suspends the subscription. EC4IM’s earlier guide to Authorize.Net Account Updater 2.0 settings goes further into configuration.
How NMI Recurring handles a failed payment
NMI’s approach puts more of the burden on the merchant. In its Recurring help article, updated November 6, NMI says the system does not automatically retry a failed payment. Instead, the subscription tries again on the next scheduled charge date. On a plan set to charge a fixed number of times, failed payments do not count toward the total and are carried to the next scheduled date.
That means an NMI subscription keeps presenting the same card on every billing date until someone pauses, edits or deletes it. Nothing in that article says the module stops on its own after a hard decline. For a card that came back lost, stolen or closed, each later billing date is another attempt on a credential Visa says must never be resubmitted.
The NMI response codes that mean stop
NMI’s response code list includes several codes that speak directly to recurring billing:
- 261, “Declined-Stop all recurring payments”
- 262, “Declined-Stop this recurring program”
- 263, “Declined-Update cardholder data available”
- 264, “Declined-Retry in a few days”
The same list has 250 (pick up card), 251 (lost card) and 252 (stolen card), which describe the same situations as Visa’s Category 1 codes 04, 41 and 43, along with 223 for an expired card. A subscription that returns 261, 262 or one of those three codes is a candidate for an immediate pause and a request for a new card. Code 264 is the issuer saying a later attempt may work, which fits within Visa’s limits for temporary declines.
Pausing an NMI subscription
In the NMI Merchant Portal, a subscription is paused under Recurring, then List Subscriptions, by opening the customer’s subscription and checking “Subscription is paused.” NMI says merchants can pause one subscription or all of them. Merchants who sign up for Receive Recurring Reports get a daily email that lists declined and errored recurring transactions individually, and NMI also offers webhooks for recurring events.
NMI’s Automatic Card Updater, found under Settings, Transaction Options, Automatic Card Updater, can check cards in all active recurring subscriptions. Subscriptions whose cards come back as requiring customer contact or as closed accounts are paused automatically. NMI lists Visa, Mastercard and Discover as supported and American Express as not supported, so Amex subscribers need a separate check.
Customer Vault billing
Stores that bill NMI Customer Vault tokens from their own software, rather than through the Recurring module, get no scheduling or retry behavior from NMI at all. NMI describes the Vault as storage that does not process transactions on a schedule, so every retry decision belongs to the store’s code. That code should read the response code on each declined charge and stop on the hard-decline codes above. EC4IM covered moving stored cards between the two gateways in its guide to Authorize.Net CIM and NMI Customer Vault migrations.
What a stop rule should do
The details differ by platform, but a workable stop rule on either gateway has the same parts:
- Read the decline reason on every failed renewal instead of treating all failures alike.
- On a never-approve decline (NMI 250, 251, 252, 261 or 262, or a suspension after an ACL response in ARB), stop charging that card and pause the subscription.
- Send the customer a request to update the card, and resume only when a new payment method is on file.
- For temporary declines, space out any retries and keep the count well inside Visa’s 20 attempts in 30 days, counting every attempt from every system that touches the card.
- Check that no plugin, app or script is retrying on top of the gateway’s own schedule.
Two gateways, two different gaps
Shopify’s RETRY_DECLINED value shows a processor refusing further charges and a platform passing that signal to app developers. Authorize.Net ARB already avoids re-running declined cards by itself, so the work there is making sure surrounding code honors suspensions and does not charge the customer profile behind ARB’s back. NMI’s Recurring module tries the same card again on every billing date until a person or the card updater pauses it, so the work there is catching stop codes and pausing fast. On both, the rule from Visa is the same: once an issuer says it will never approve a card, the next charge should go on a different one.
Sources
- Shopify developer changelog, RETRY_DECLINED added to CustomerPaymentMethodRevocationReason (November 4, 2026)
- Visa Core Rules and Visa Product and Service Rules, April 18, 2026 edition
- Adyen Docs, Mapping to Visa system integrity fee categories
- Authorize.Net, Recurring Billing developer documentation
- Authorize.Net, What is Automated Recurring Billing (ARB) and how to use and configure it? (KA-04444)
- Authorize.Net, What is the Automatic Retry system for Automated Recurring Billing (ARB)?
- Authorize.Net, Webhooks developer documentation
- NMI, Recurring via the Virtual Terminal, Plans and Subscriptions
- NMI, Payment API response codes
- NMI, Automatic Card Updater Settings
- NMI, Getting Started with Automatic Card Updater
- NMI, Customer Vault