PaymentIQ orchestration and the Vuch platform
PaymentIQ is a payment orchestration platform — originally built by Sweden's Devcode and now part of Paysafe — that sits between an operator and hundreds of PSPs, handling routing, cascading and unified reporting across all of them. It occupies a different layer than a payment method: PaymentIQ is not how a player pays, it is how an operator manages everyone the player pays through. On the Vuch side, the position is straightforward: our payment rails today are USDT, a fiat payment layer is on the roadmap, and PaymentIQ is the kind of orchestration integration that layer is designed around — not a live, certified connection.
What PaymentIQ is
Large iGaming operators rarely run two or three PSPs; they run fifteen, across markets, methods and backup routes. PaymentIQ industrialized that problem: more than 300 pre-built PSP and method integrations, a rules engine for routing and cascading, fraud and KYC vendor plugins, and one reconciliation view across the whole estate. It became something of a default orchestration layer in European iGaming — operators migrating between platforms often bring an existing PaymentIQ setup, contracts and routing logic included.
PaymentIQ and the Vuch roadmap: two future patterns
Vuch's payments today are USDT: webhook-driven deposits and withdrawals with manual moderation and an explicit status model, feeding the platform's built-in real-time risk engine. The roadmap fiat layer is being designed with two patterns in mind:
| Pattern | When it would fit |
|---|---|
| Native fiat routes only | New brands, or operators content with the fiat layer's own PSP integrations once live; simplest stack, one vendor |
| PaymentIQ behind the fiat layer | Operators with an existing PaymentIQ estate — migrations, multi-platform groups — or needing a PSP that PaymentIQ has and the fiat layer does not yet |
In the second pattern, PaymentIQ would connect as a route behind the platform's payments API, with the operator's existing merchant contracts, routing rules and fraud-plugin configuration surviving intact — the property that matters most during platform migrations, where re-negotiating fifteen PSP contracts mid-move would be the project's biggest risk. Neither pattern is live today; both are published so operators can evaluate the direction.
What the design keeps unified
- One payments API for your team as the target end-state — deposits, payouts and webhooks identical across native and orchestrated routes
- One reconciliation flow — settlement data feeding the same reporting regardless of route
- Risk at platform level — deposit limits and payment rules enforced by the platform's built-in risk engine, with thresholds configurable per jurisdiction, above any orchestration layer
Where to start
If you run a PaymentIQ estate today and are evaluating Vuch, the useful conversation is scoping: which of your routes the fiat layer would need to cover, in what order, and what runs on USDT in the meantime. Certification roadmap and a due-diligence pack are available on request.
Request a demo to map your current payment estate against the Vuch roadmap — especially if you are planning a migration.