Risk level: High risk
Payment orchestration for other high-risk verticals
VPN, hosting, telecom, adult and the other verticals acquirers call high-risk share one problem: few acquirers take them, and each sets limits and reserves. Orchestration gives the merchant's PSP cards across several acquirers, Open Banking in the EU, and USDT and Bitcoin where cards are closed, cascades a decline, applies limits and the rolling reserve per merchant, and journals every payment for the acquirer and the regulator.
What goes wrong without orchestration
- The merchant depends on one acquirer, and a termination or a lowered limit stops the business overnight.
- The acquirer’s rolling reserve and monthly limit live in a spreadsheet, and the limit is discovered when payments start declining.
- A chargeback or a compliance request needs the payment’s full history, and it is in a provider dashboard the merchant can no longer open.
What orchestration changes
Routing by BIN, country and amount across several acquirers and cascading of a decline to the next; Open Banking (EU, PIS) in Germany, France, Spain, Italy, the Netherlands and Poland without chargebacks; USDT and Bitcoin for deposits and payouts where card acquirers refuse the vertical; limits per merchant, terminal and day and a rolling reserve per merchant, applied by the software within the acquirer’s terms; every payment, refund, chargeback and callback journaled for five years with a trace. The merchant’s PSP enables the methods from the catalogue; the licensed acquirer settles the funds and decides what it takes.
Verticals and methods
- VPN, proxy and hosting: cards with recurring charges by token; USDT and Bitcoin for customers who do not pay by card.
- Telecom and VoIP: cards for top-ups with limits per account against card testing; Open Banking in the EU.
- Adult: cards through the acquirers that take the vertical, with a rolling reserve; USDT and Bitcoin where they do not.
Typical methods
Frequently asked questions
Which verticals does this page cover?+
Who holds the licence?+
Does orchestration get a high-risk merchant approved?+
See the platform on your own flows
Thirty minutes with an engineer, not a sales deck: your providers, your routing rules, your merchants' checkout.
- ✓ Not a financial institution
- ✓ Money never passes through us
- ✓ Built to PCI DSS requirements