Split payments
How installment splitting on a single payment works, and how marketplace-style revenue sharing actually works with Sync today.
Two different things share the word 'split'
There is no single-payment feature that divides one payment's proceeds across multiple
subaccounts by an inline split array. What exists today: 1. Installment splitting (POST /payments/{id}/splits) — the same payer pays a single payment in 2–4 tranches over time.
Unrelated to marketplace revenue sharing. 2. Sync per-account pricing — when you operate a
payment on behalf of one subaccount (via X-Sync), that subaccount's configured pricing
(percentage/fixed fee) is applied automatically. This covers "platform keeps a cut of this
subaccount's payment" — it does not support splitting a single payment's proceeds across
multiple subaccounts.
Installment splitting
curl https://api.wajub.com/payments/trx_01JXXXXXXXXXXXXX/splits \
-H "Authorization: sk_test.2a7c5e91b0d34f68" \
-d '{ "split_count": 3 }'
# Or with explicit amounts (must sum to the payment total):
curl https://api.wajub.com/payments/trx_01JXXXXXXXXXXXXX/splits \
-H "Authorization: sk_test.2a7c5e91b0d34f68" \
-d '{ "split_amounts": [4000, 3000, 3000], "split_currency": "XAF" }'split_count accepts 2, 3, or 4. Use split_amounts instead for unequal tranches (2–4
values, each ≥ 0.01). The customer is charged for each tranche in sequence.
Sync per-account pricing (revenue kept by the platform)
curl https://api.wajub.com/payments \
-H "Authorization: sk.xxxx" \
-H "X-Sync: acc_7Yh2Mp" \
-d '{ "amount": 10000, "currency": "XAF", "email": "client@example.com" }'The subaccount's own pricing.percentage_fee/pricing.fixed_fee (configured at
onboarding) determines what the platform retains — there's no per-request
override and no multi-subaccount cart-splitting today.
Multi-seller carts
If your platform needs a single checkout to pay out to several different sellers at once, that
isn't currently supported as a single API call — you'd need to create separate payments per
seller, each attributed via its own X-Sync header.
Was this page helpful?