Partner Quick Start
Time: ~10 minutes · Difficulty: Beginner · You will get: a successful test paymentWhat you’re going to build
payment_xxx row visible in the TagadaPay dashboard and the test funds reflected on the settlement balance account (for MoR sub-merchants, that’s the partner’s shared balance — see Payouts, balances & fees).
Prerequisites
1. Install the two SDKs
2. Provision a sub-merchant (server-side)
Idempotent. Calling
create() again with the same externalRef returns the existing TPA — safe to retry on network errors.3. Mint a Processing Key for that TPA (server-side)
merchant_42’s processing — never on your other merchants.
4. Tokenize the card (client-side, in the browser)
5. Charge (server-side, with the Processing Key)
What you just built
Common next steps
Add Apple Pay / Google Pay
The wallet APMs use the same primitives in
core-js, plus a small native sheet step. Native vs Stripe routing is explained on the APM page.Add Klarna / iDEAL / Bancontact
Redirect APMs need no client tokenization — you call
payments.process with paymentMethod: 'klarna' and a returnUrl, then redirect the customer to the URL we hand back.Add 3DS where required
For European cards or high-risk transactions, run a 3DS challenge between tokenization and charge.
Discover what each merchant has enabled
Use
paymentSetup.get(storeId) to fetch the method × provider config and render the right buttons per merchant. Get storeId from stores.list({ accountId }).