Payment method declined payment_method_declined
What this decline means
The processor declined the stored payment method itself. It sits between a generic decline and an invalid method: the record still resolves, but the processor is refusing to charge it.
Why it happens on subscription renewals
- The card behind the stored method has been closed, frozen, or restricted since it was saved.
- The processor's own risk or compliance layer refuses this method (unsupported card product, sanctioned region, repeated failures).
- The method is technically alive but its issuer declines all recurring or card-not-present usage.
The merchant playbook
- Give it one spaced retry — some method-level declines are temporary freezes that thaw.
- If it fails again, move straight to the card-update path: from the customer's point of view the recovery action is identical to a dead card, and the sooner they re-save a method, the better.
- Read any accompanying processor message — method-level declines often carry a free-text hint (restricted card, unsupported type) more specific than the code.
- On exhaustion, pause rather than cancel: subscribers behind method-level declines frequently return once they notice the service stopped, and a paused contract makes that return one click.
Should you retry?
One careful retry, then treat as hard. A payment method the processor keeps refusing is functionally gone regardless of what the record says.
Common questions
How is this different from card_declined?
Card-declined reports the issuer refusing a charge; payment-method-declined points at the stored instrument itself being refused. In practice the second converts to 'get a new card on file' faster.
The customer says their card works in stores — why does the renewal fail?
In-person and recurring charges travel different rails with different rules. An issuer can approve tap-to-pay while declining card-not-present recurring charges on the same card — the customer's bank can confirm and unblock it.
Related codes: invalid_payment_method · card_declined · expired_card · or see the
full decline-code guide.
Where Moorly fits: Moorly reads the decline reason behind every failed renewal in your existing subscription app and applies the playbook above automatically — the right treatment per code, with a dollar figure on what each failure family costs your store. It starts read-only. Join the early-access list →
Moorly is an independent product by Velun Labs and is not affiliated with Shopify, Appstle Inc., or Seal Subscriptions s.r.o. Code names follow Shopify's public API documentation as of August 2026; bank behavior varies by issuer — always confirm against your own admin.