One KYB. Every PSP. Portable by design.

The lock-in problem, unlocked

Most platforms onboard their merchants directly into Stripe Connect, Adyen MarketPay, or Airwallex Platform. It works, until you want to renegotiate pricing, add regional coverage, or launch in a market your PSP doesn't serve. Switching means re-collecting every document from every merchant. Most platforms never do.

Tapped Onboard fixes this at the data layer. You collect each sub-merchant's business record once, inside a white-labelled flow we host for you. The record lives in your Tapped workspace, encrypted with a key scoped to your platform, GDPR-compliant, owner-of-record documented. Tapped then forwards the exact fields each PSP asks for, in the shape they expect, whenever you want to route a merchant to a new rail.

You stay portable. Your merchants stay unbothered. Your finance team stays free to optimise cost.

What "PSP-agnostic" looks like in practice

• Collect once, route anywhere. One branded KYB flow, one set of documents, one UBO disclosure. Route to Stripe Connect, Adyen, Airwallex, or Tapped's own APAC acquiring at the merchant, market, or transaction level.
• Switch without re-asking. Move a merchant from Stripe to Adyen because Adyen is cheaper in EU, no email to the merchant, no new forms. Tapped has the data; Tapped sends it.
• Cost-optimise per market. Run Stripe in US, Airwallex in AU, Adyen in EU, Tapped in APAC, all from one sub-merchant record. Route new merchants to the lowest-cost provider for their country and MCC.
• Own your customer relationship. The sub-merchant record is in your Tapped workspace, on your contract. If you ever leave Tapped, you take the data with you in a documented export format.

How the data path works

A merchant signs up in your product. Your app calls Tapped Onboard with the merchant's Tapped ID, the target PSP, and the market. We translate our canonical KYB schema into the PSP's required payload, attach the required evidence files from encrypted storage, and submit against the PSP's onboarding API. Status flows back through webhooks.

// One record, many destinations
await tapped.onboard.route({
  submerchantId: 'sub_7kQ2',
  destination: 'stripe',       // or 'adyen', 'airwallex', 'tapped'
  market: 'SG',
  mcc: '5812'
});

// Later: the same merchant, a different PSP, no new data collected
await tapped.onboard.route({
  submerchantId: 'sub_7kQ2',
  destination: 'adyen',
  market: 'MY',
  mcc: '5812'
});

Every route call is idempotent, logged, and auditable. Your merchants never see a second form.

The data that travels (and the data that doesn't)

Tapped stores the minimum needed to onboard across PSPs: business registration, UBO structure, director KYC, bank details, tax IDs, and supporting evidence files. Each field is classified by the jurisdictions that require it, so we never hand more than a given PSP can legally receive.

• Encrypted at rest with per-tenant keys (customer-managed keys on Enterprise).
• Encrypted in transit to every PSP, over mutual TLS or scheme-specified equivalent.
• GDPR, PDPA, APPI compliant, DPAs signed, SCCs where relevant, data residency configurable per region.
• Right-to-deletion honoured even across routed PSPs: a delete request propagates to every active destination.
• Audit log of every field read and every outbound submission, surfaced in your dashboard.

What you ship in a sprint

1. Day 1–3. Embed the Tapped Onboard flow, either as an iframe under your domain or as native React / mobile components. Theming uses your brand tokens.
2. Day 4–7. Wire the routing decision. Most platforms start with a static map (US → Stripe, APAC → Tapped) and add rules later.
3. Week 2. Pilot with 5–20 sub-merchants across two destinations. Watch them land in both PSP dashboards from one record.
4. Ongoing. Add or swap PSPs as your cost model evolves. The merchant side of the product doesn't move.

Tapped as a destination, too

In the APAC markets where Tapped operates as a licensed acquirer, Singapore, Philippines, Malaysia, Indonesia, Thailand, Hong Kong, Vietnam, and Japan, routing to "tapped" activates Tapped's own acquiring relationship. Same onboarding record, same KYB data, same sub-merchant ID, but now the card flow goes through Tap Core, not a third-party PSP. Most platforms use Tapped as the default APAC destination and reach for Stripe or Airwallex only for markets we don't yet cover.