apayDistribution and technology for licensed partners
apay does not hold a licence and does not want yours. We bring platforms that need modern payments, the switch that routes their volume, and a connector contract that makes integrating your bank a fixed-scope project. You bring the licence, the scheme memberships and the settlement.
What partners provide
- Merchant acquiring or PSP licence in the target market
- Card scheme acceptance, wallet tokenisation (Apple Pay, Google Pay) or local scheme access
- Optionally: virtual collection accounts, payouts, card issuing
- Sandbox credentials and API documentation for the connector
- Merchant onboarding rules, pricing and settlement terms
What apay provides
- A running switch with hosted checkout, dashboard, webhooks and routing
- The connector implementation against your API, tested in sandbox before go-live
- Merchant pipeline: platforms and marketplaces onboarded through apay
- Technical merchant support, integration docs and SDKs
- Reporting for reconciliation and scheme compliance
Three ways to partner
Card and wallet acceptance
Your acquiring is exposed as an apay connector. Merchants integrate once and can be routed to you by country, currency or card type.
Virtual accounts and payouts
Collection accounts under a master account, credit notifications and payout instructions, reconciled by apay for marketplaces and wallets.
Cards-as-a-service
Instant virtual cards for platform users with push provisioning to Apple Wallet and Google Wallet through your issuing processor.
Target markets and partner types
| Market | Partner profile | Rails | Status |
|---|---|---|---|
| Singapore, Hong Kong | Virtual banks, BaaS programmes, PSP licence holders | Cards, Apple/Google Pay, PayNow, FPS | in discussion |
| Philippines, Indonesia | BaaS banks, virtual account issuers | Cards, GCash, virtual accounts, InstaPay/PESONet | in discussion |
| UAE | Platform banks, digital banks | Cards, Apple/Google Pay, AED accounts | in discussion |
| Kazakhstan, Uzbekistan, Armenia, Georgia | API-first banks, AIFC licensed PSPs | Cards, local transfers, payouts | in discussion |
| Global card processors | Stripe, Adyen, Checkout.com, Airwallex and 50+ others | Cards and wallets | connector ready |
How an integration runs
1. Scoping (1 week)
We map your API to the apay connector contract and agree the commercial model. You receive the requirements document and the due-diligence pack.
2. Sandbox (2 to 4 weeks)
apay builds and certifies the connector against your sandbox: authorise, capture, refund, webhooks, 3DS, wallets.
3. Pilot (4 weeks)
One or two apay merchants go live on your rails with capped volume. Reconciliation and settlement reports are verified daily.
4. Scale
Routing rules send you the traffic you want. Joint go-to-market for platforms in your market.
Read the partner overview Integration requirements Due-diligence pack Contact partnerships