Handbook · OPERATIONS

Payment operations

Running a high-risk stack day to day: cascading transactions across processors, building the redundancy so one decline doesn't sink revenue, why two PSPs isn't enough at scale, and how long onboarding really takes. The operational mechanics behind a stack that stays live.

4 articles in this topic

OPERATIONS

What Is Payment Cascading (and Why Your Decline Rate Cares)?

Cascading retries declined transactions on a secondary PSP before the customer sees a failure. Done right, it recovers 5-15% of would-be-lost revenue.

2 min read · May 2026Read article

OPERATIONS

Why high-risk merchants need payment redundancy

One PSP going down means zero revenue. For high-risk merchants, redundancy isn't a nice-to-have — it's the difference between running and not running.

3 min read · May 2026Read article

OPERATIONS

Why established merchants need more than two PSPs

No issues today doesn't mean no issues tomorrow. At scale, PSP concentration risk is the threat that's invisible until it isn't.

3 min read · May 2026Read article

OPERATIONS

How Long Does PSP Onboarding Take for High-Risk Merchants?

The realistic answer is 2-6 weeks per PSP. Documentation, structure, and whether you go in cold or through existing relationships drive each timeline.

5 min read · May 2026Read article

All handbook articles