Mintcash
Concepts

Cascading

When a provider declines or fails, MintCash can retry the same charge against the next provider in line — without your code knowing.

Cascading is what happens when the first provider says no. Instead of surfacing a failed to your application, MintCash re-attempts the same charge against the next provider in the merchant's routing priority. The payment doesn't terminate until every eligible provider has had a chance — or until a non-cascadable error stops the chain.

The flow

Rendering diagram…

From your side, this is one charge with one final webhook. The cascade is internal — you don't see the intermediate decline.

What's cascadable

Not every failure triggers a cascade. Some errors mean "try someone else", others mean "this charge is dead".

ResolutionCascade?Why
provider_errorYesThe PSP itself failed — another one may succeed
issuer_decline (soft)YesIssuer rejected via that PSP — re-route may pass
provider_fatal_errorYesPSP-side outage
insufficient_fundsNoCard-level — another PSP won't fix it
card_expiredNoCard-level
lost_or_stolen_cardNoCard-level — also a fraud signal
antifraud_errorNoStops immediately
invalid_pan / invalid_cvvNoCustomer-input issue

The full mapping lives in the errors reference.

What you see

  • One payment record. The payment.id doesn't change during cascading.
  • One terminal webhook. You get either payment.succeeded or payment.failed once the cascade finishes — not one per attempt.
  • One audit trail. The intermediate provider attempts are recorded server-side and visible in the dashboard, but they don't pollute your webhook stream.

Cascading is one-shot per request

Cascading covers the single in-flight charge — provider A failed, so we try provider B. It does not mean we retry later. For time-spaced retries on recurring charges, see Retries.

Controlling the cascade

You can configure cascading behaviour per merchant:

  • Enable / disable — turn cascading off if you want every provider decline surfaced immediately
  • Eligible providers — limit which providers participate
  • Order — overlay a priority order on top of your routing rules

Changes flow through your account manager.

See also

  • Routing — how the first provider is picked
  • Retries — time-spaced retries for recurring charges
  • Errors — full taxonomy of resolutions and which ones cascade