Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tagada.io/llms.txt

Use this file to discover all available pages before exploring further.

​
TagadaPay for Partners

Who this is for — Companies who run their own merchant-facing product (PSPs, marketplaces, embedded-payments platforms, recurring-billing tools, virtual terminals) and want to use TagadaPay as their payment infrastructure.Your merchants never see TagadaPay. They see your brand, your dashboard, your support. TagadaPay sits behind your service, processes the cards, returns the money to your merchants’ bank accounts.

​
What you can do as a partner

CapabilityAPI surface
Provision a sub-merchant programmatically (KYB, store, settlement currency)tagada.partners.accounts.create()
Mint an API key restricted to one specific sub-merchanttagada.partners.apiKeys.create()
Discover what payment methods are available for that merchanttagada.paymentSetup.get(storeId)
Tokenize cards / Apple Pay / Google Pay client-side (PCI-safe)@tagadapay/core-js
Charge cards server-to-servertagada.payments.process()
Initiate redirect APMs (Klarna, iDEAL, Bancontact, …)tagada.payments.process({ paymentMethod: 'klarna', ... })
Run 3DS challenges when issuers require themtagada.threeds.createSession()
Submit KYB documents and update requirementstagada.partners.documents.record()

​
You only need two SDKs

┌──────────────────────────┐         ┌──────────────────────────┐
│  @tagadapay/core-js      │         │  @tagadapay/node-sdk     │
│  Browser                 │         │  Server                  │
├──────────────────────────┤         ├──────────────────────────┤
│ • Card tokenization      │         │ • partners.accounts.*    │
│ • Apple Pay tokenization │         │ • partners.apiKeys.*     │
│ • Google Pay tokenization│         │ • paymentInstruments.*   │
│ • 3DS challenges         │         │ • payments.*             │
│ • Wallet availability    │         │ • paymentSetup.*         │
│ • Stripe Express         │         │ • threeds.*              │
└──────────────────────────┘         └──────────────────────────┘
            │                                     │
            └──────────► your stack ◄─────────────┘
That’s it. No checkout sessions to manage, no funnels to deploy, no React framework to opt into. You bring your own UI, your own server, your own merchant-facing product. We handle tokens, processors, and money.

​
Mental model in 30 seconds

You (the partner)              TagadaPay
─────────────                  ──────────

1. Sign up as a partner   ───► partner_id (par_xxx)
   API key                ───► tp_sk_partner_xxx  (full partner power)

2. Provision a merchant   ───► tpa_xxx + acc_xxx + store_xxx (auto-created)
                                each merchant gets their own private namespace

3. Mint a sub-key         ───► tp_sk_xxx (restricted to that one tpa_xxx)
                                this is the key your charging code uses

4. Tokenize browser-side  ───► tagadaToken (PCI-safe, single-use)

5. Charge server-to-server◄─── { payment_id, status, ... }
   with sub-key + storeId
The two-key model (partner key for provisioning, sub-key for charging) is the security boundary — if a sub-key leaks, only one merchant is exposed, never your whole partner account.

​
Where to start

Quick Start

The end-to-end S2S flow in 4 steps: provision → mint key → tokenize → charge. ~10 minutes to a successful payment.

Sub-merchant provisioning

The tagada.partners.accounts.* API: how TPAs, stores, and the orphan accounts row work together.

API keys & authentication

Partner key vs sub-key, scopes, rotation, secrets handling.

Server-to-server payments

Card flow, payment instrument lifecycle, refunds, captures, MIT.

Alternative payment methods

Apple Pay, Google Pay, Klarna, iDEAL — including the native vs through-processor distinction that determines which browser SDK to load.

Payment setup config

The method × provider shape of the runtime config — how to discover what payment methods a merchant has enabled.

Full end-to-end example

A complete partner integration: signup → charge → refund, with all the snippets in one place.

​
What this section is NOT

If you’re building…Use instead
A web checkout for your own storeHeadless SDK or Plugin SDK
A custom checkout page hosted on TagadaPayPlugin SDK
A simple “Buy Now” button on an external siteWeb Integration
Server automation for a single merchant’s storeNode SDK quick start
The “Partners” section assumes you’re acting on behalf of many merchants and need the multi-tenant primitives (TPAs, sub-keys, per-merchant store provisioning).