Payment orchestration built for marketplace complexity.
Multiple sellers. Multiple providers. Multiple regions. Multiple split rules. Marketplace payments aren't a single integration — they're an operational system that compounds in complexity with every seller you onboard. Tokeflow gives you the orchestration layer to manage it without building a payments team.
Marketplace payments are a different problem.
In a standard e-commerce operation, one entity sells, one entity collects, one provider processes. In a marketplace, every transaction involves at least three parties — the buyer, the seller, and the platform — each with different interests and obligations.
The platform retains a commission. The seller receives the remainder. Tax may need to be withheld. The payment method may vary by region. And if a transaction fails, cascade logic must respect the split configuration — not retry blindly. Most payment integrations were not designed for this.
The problems that compound with every seller you onboard.
Split logic that breaks when you change providers
Commission splits are straightforward until APIs change, you add a second provider, or tax rules require a three-way split. Most platforms hard-code split logic against one PSP — when that breaks, debugging during a seller dispute costs trust.
What this costs you: Engineering fragility. Split logic becomes the most touched, least understood code in your stack.
Seller-level configuration at platform scale
Seller A uses Pix in Brazil; Seller B uses Stripe in the US; Seller C brings their own acquirer. Your platform must support all of this simultaneously — without a custom integration per seller.
What this costs you: Onboarding speed. Non-standard sellers pull engineering into every onboarding.
Operational visibility across a fragmented stack
Each provider has its own dashboard, webhooks, IDs, and decline taxonomy. Answering “what is the approval rate for sellers in category X across all providers?” shouldn't require merging spreadsheets.
What this costs you: Operational overhead that scales with every new provider.
What changes with Tokeflow in your marketplace.
Split-aware orchestration
Define commission, seller share, and tax withholding at the platform level. Tokeflow keeps routing and provider interaction aligned with those rules when you add or change PSPs.
Multi-Provider Orchestration · Smart Routing
Per-seller payment configuration
Each seller maps to a merchant entity with isolated connectors, routing profiles, webhooks, and data. Onboarding is configuration — not a new deploy.
Multi-Tenant Governance · Webhook Normalization
Unified operational layer
One event model, one decline taxonomy, one audit trail — with raw provider payloads stored for disputes.
Webhook & Event Normalization · Audit & Traceability
How marketplaces use Tokeflow.
Multi-seller marketplaces
Independent sellers with different requirements, isolated per merchant, unified view of commissions and transactions.
Service marketplaces & gig platforms
Platform commission, provider payout, and tax withholding — orchestrated across providers with consistent split rules.
Vertical marketplaces
Standardize the buyer experience while allowing per-seller configuration for methods and routing.
Aggregator platforms
Many merchants, one experience — each operates independently under Tokeflow's multi-tenant model.
How a marketplace transaction flows through Tokeflow.
- Buyer initiates payment — card data tokenized; your platform never stores PAN.
- Platform sends split parameters (e.g. 85% seller, 15% platform).
- Routing engine selects PSP from the seller's profile.
- PSP authorizes; soft declines or tech errors cascade to fallback automatically.
- Normalized events to platform and seller webhooks.
- Full audit trail: routing, cascades, responses, splits, deliveries.
const payment = await tokeflow.payments.create({
merchant_id: 'merch_seller_042',
amount: 10000,
currency: 'BRL',
method: 'credit_card',
payment_method: { token: 'tok_card_...' },
routing: { profile_id: 'rp_seller_042_brl', fallback: true },
customer: { id: 'buyer_xyz' },
split: {
rules: [
{ destination: 'merch_seller_042', percentage: 85 },
{ destination: 'platform', percentage: 15 }
]
},
metadata: {
order_id: 'order_78901',
marketplace_category: 'electronics'
}
});
// payment.split_detail → settled amounts per destinationOne view. Every seller. Every provider.
Unified transaction queries
Filter across sellers, providers, and methods from one API — no more merging CSV exports manually.
Routing trace per transaction
See which provider was selected, which were skipped, cascade timing, and decline reasons.
Normalized decline taxonomy
One vocabulary across Stripe, Mercado Pago, Paystack, and the rest.
const results = await tokeflow.payments.list({
status: 'declined',
method: 'credit_card',
currency: 'BRL',
metadata: { marketplace_category: 'electronics' },
created_after: '2026-04-05T00:00:00Z',
created_before: '2026-04-12T00:00:00Z'
});What changes in marketplace operations.
| Without Tokeflow | With Tokeflow | |
|---|---|---|
| Onboarding a new seller | PSP choice, webhooks, split tests | Create merchant → connectors → routing |
| Seller in a new region | New contract, integration, split code | Add connector + routing rule |
| Provider outage | Sellers on PSP go offline | Automatic cascade |
| Seller disputes payout | Dashboard + logs + code | GET /payments/:id/trace with split detail |
| Decline spike investigation | Export & merge dashboards | Unified query + taxonomy |
| Adding Pix for BR sellers | Custom Pix + split updates | Connector + route; split unchanged |
Clear boundaries for marketplace operations.
| Responsibility | Your marketplace | Tokeflow |
|---|---|---|
| Buyer & seller relationships | You own them | — |
| Marketplace UX & checkout | Your brand | — |
| Commission & pricing | Your rules | — |
| Provider integrations | — | Unified API |
| Per-seller routing & fallback | You define rules | Tokeflow executes |
| Webhook normalization | — | One event format |
| Transaction audit trail | — | Full lifecycle + split detail |
Tokeflow doesn't manage your marketplace. It manages the payment layer underneath.
We don't run seller KYC, payouts, or commission policy. Tokeflow provides orchestration so you can route transactions, normalize events, isolate sellers, and stay visible across providers — without hiring a payment operations team. Your marketplace logic stays yours; the plumbing becomes ours.
Running a marketplace? Let’s talk payment architecture.
We’ll map your seller structure, provider landscape, and split requirements — then demo how Tokeflow orchestrates multi-seller, multi-provider transactions in real time. Sandbox access included.