Skip to article
ecomservices.io
Payment orchestration · How to run this
RoutingCalculatorCascadeCalculatorRetriesCalculator3DS placementCalculatorDeclinesCalculatorAffinityNot on this page yetOptimisationCalculator

Library · Payment orchestration · How to run this

Recover a wallet decline with a card path

How to run thisPayment orchestration4 steps
GuideWallet decline recovery — claim map · Calculator lives in the articleOpen

A wallet decline (Apple Pay, Google Pay, and siblings) often means the wallet path failed — device, bank app, network, or limit — not the same signal as a card issuer soft/hard code. The recover path is usually one clean card form (or a second wallet the shopper chooses), not a cascade of the same wallet token across MIDs.

Pair: Wallet decline recovery — claim map on Orchestration. Card soft vs hard: decline code playbook.

What to do

Show a card path once after a wallet fail — clear copy that the wallet did not go through.

Keep the cart. Do not force a full restart that drops the order.

If the card path soft-declines, then use the soft/hard playbook on that auth — not another wallet hop by default.

What not to do

Do not spray the same wallet token across spare MIDs. Do not treat every wallet fail as NSF. Do not hide the fail and auto-retry the wallet five times. Do not invent a “wallet approval benchmark.”

Related: Orchestration, decline playbook, first-try vs net, 3DS lift. Wallet buyer claims (not checkout fails): wallet vs card CB.

Procedure

  1. Surface the wallet fail clearly.
  2. Offer a card form once; keep the cart.
  3. If the card auth returns a family, use the decline playbook.
  4. Do not hop dead wallet credentials.

Failure modes

  • Cascading the same wallet token across MIDs.
  • Treating every wallet fail as NSF.
  • Silent multi-retry wallet loops.
  • Applying card soft/hard rows before a card auth exists.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

Wallet decline
Apple Pay / Google Pay (or sibling) path failed before or instead of a normal card issuer soft/hard code. Recover with an alternate path — usually card once.

Work with us — We run this job on your accounts. Services

FAQ

If Apple Pay declines, should I cascade the wallet token to another MID?
No. Offer a card (or alternate wallet) path once. Do not hop a dead wallet credential.
Is a wallet decline the same as NSF on a card?
No. Wallet failures are often device, bank-app, or network path issues. Card soft/hard rules are a different map.
Is this the soft vs hard decline playbook?
No. [Decline playbook](/manuals/decline-code-playbook) is next action on a card auth. This page is checkout wallet recovery.