Solutions

iGaming payment solutions: one integration for your PSP accounts

OrsunPay is a payment orchestration platform that connects you to licensed PSPs; it does not process or hold funds itself. Operators plug the payment gateway accounts they already hold into one API, so players see the deposit methods those accounts support in each market.

Operator-owned PSP accounts with a single orchestration layer

Deposit lifecycle

  1. Player selects deposit
  2. Session & method fields
  3. Provider authorization
  4. Webhook or API confirmed
  5. Balance updated in your wallet

Controlled payout path

Withdrawal request
PSP eligibility & limits
Payout status in back office

Payout rails follow connector support — not every deposit method can pay out.

Payment requests route through OrsunPay; settlement stays direct with your PSP.

Deposits

Present the payment methods enabled on the player’s merchant profile. Extra fields (for example a mobile number for Swish) are collected only when the method needs them; card entry stays on the PSP hosted page.

The player sees processing until your server receives a signed webhook or a confirmed API status — a return to your site alone is not treated as success.

Withdrawals

Outbound flows depend on what each connector supports — for example payout to a verified prior card payment where the PSP allows it.

Velocity limits and manual review remain with the PSP and your risk team. OrsunPay tracks operation status; it does not replace provider compliance.

How it fits together

Same REST patterns as other verticals: idempotency keys, webhook verification and merchant scoping.

For a player-facing deposit walkthrough, try the software demo on the iGaming cashier page — preview only, no money moves.

Deposit vs withdrawal paths

Deposit

  1. Player picks a method enabled on your PSP account
  2. Checkout asks only for fields that method needs
  3. PSP authorises or redirects the player
  4. Your UI stays pending until a webhook or API confirms

Withdrawal

  1. Separate flow from deposits in your product
  2. Provider rules, limits and reviews still apply
  3. Some connectors pay out only to a verified prior card deposit
  4. Track the final status in one place

Frequently asked questions

Is OrsunPay an iGaming payment provider or gateway?

No. OrsunPay is orchestration software. The PSPs and gateways you contract with authorise and settle payments, and they decide whether gambling traffic is accepted for your licence and markets. OrsunPay connects those accounts through one API, routes each deposit to the right connector and keeps statuses and webhooks in one place.

How does an iGaming PSP integration work with OrsunPay?

You add the credentials of each PSP account in the merchant cabinet and call one REST API for deposits. OrsunPay forwards each session to the chosen connector, verifies signed webhooks and shows the final status. Adding another PSP for a new market needs the provider's own onboarding, not a new integration on your side.

Can I use several PSPs for deposits in different markets?

Yes. Operators often need different providers per country, currency or method. Smart routing and retries send each deposit to the connector that matches the rules you set and fall back when a provider declines or is unavailable. Which methods go live still depends on each PSP approving your licence and markets.

Discuss your payment setup

Tell us about your company, PSP accounts, currencies and markets. We will map what the software can connect and what your providers need to enable.

Discuss your payment setup