apayBank partner overview
A two-page brief for banks, virtual banks and licensed payment institutions considering a partnership with apay.
The proposition in one paragraph
apay is a payments platform for digital platforms in Asia and the CIS: marketplaces, messengers with commerce, SaaS and wallets. Merchants integrate apay once (API, hosted checkout, dashboard, webhooks) and apay routes their card, wallet and local-method payments to licensed partners. apay operates a payment switch proven at scale with large merchants and banks, fully auditable, and the partner bank keeps the regulated activities: acquiring, settlement, account holding, issuing. apay is a distribution and technology partner, not a competitor and not a licence seeker.
Why banks partner
- New merchant segment without new sales cost. Platforms come to apay for the developer experience; apay brings them to the bank already integrated.
- Modern rails on top of your core. Apple Pay, Google Pay, hosted checkout, smart routing, 3DS, tokenisation and reconciliation delivered by apay, integrated with your APIs once.
- Fixed-scope integration. One connector contract (authorise, capture, refund, webhooks, optional virtual accounts and payouts). apay writes and certifies the connector against your sandbox.
- Portfolio visibility. Every merchant, payment and dispute is visible to the bank through the dashboard and reports, supporting AML monitoring and scheme reporting.
What each side provides
| apay | Partner bank |
|---|---|
| Running platform: API, checkout SDK, dashboard, webhooks, routing, vault | Licence(s) and scheme memberships in the market |
| Connector implementation and certification against the bank’s API | Sandbox and production API access, documentation, test cards |
| Merchant acquisition, technical onboarding and support | Merchant underwriting rules, KYB/KYC decisions, MCC policy |
| Reconciliation and settlement reports, dispute workflow | Settlement to merchants, funds handling, dispute handling with schemes |
| Monitoring, fraud rules, 3DS orchestration | Risk limits, reserve policy |
| Compliance pack: security controls, PCI scope, data flows | Regulatory reporting |
Commercial models
- Referral and technology fee. The bank contracts merchants directly; apay earns a per-transaction platform fee and an integration fee.
- Payment facilitator under the bank. apay (or its licensed affiliate) is a PayFac or master merchant; the bank prices apay wholesale; apay onboards sub-merchants under the bank’s rules.
- White label. The bank offers “bank-branded” developer payments powered by apay to its own clients; licence fee plus revenue share.
Pilots typically start with model 1 in one market with two merchants and capped volume, then move to 2 or 3.
Products in scope
- Acquiring: cards (Visa, Mastercard, local schemes), Apple Pay and Google Pay, local wallets and real-time payment schemes (PayNow, FPS, GCash, InstaPay, UPI and similar).
- Accounts: virtual collection accounts under a master account, credit notifications, payout instructions, daily reconciliation.
- Issuing: instant virtual cards for platform users, push provisioning to Apple Wallet and Google Wallet, through the bank’s issuing processor (Thredd, Paymentology, Marqeta and similar).
Timeline
| Phase | Duration | Output |
|---|---|---|
| Scoping | 1 week | Connector mapping, commercial term sheet, due-diligence pack exchanged |
| Sandbox integration | 2 to 4 weeks | Certified connector: authorise, capture, refund, webhooks, 3DS, wallets |
| Pilot | 4 weeks | Two merchants live with capped volume, daily reconciliation verified |
| Scale | ongoing | Routing rules, joint go-to-market |
Next step
A 45-minute call with the bank’s digital or fintech partnerships lead and one API owner. apay shares the integration requirements and the due-diligence pack in advance and demonstrates a live sandbox payment from a phone through the bank-side connector contract.
Contact: partners@apay.to