Split payments
Installment splitting, per-connection commission, and what neither of them does.
Two unrelated features share the word split, and people arriving from another payment platform usually want a third thing that does not exist here. This page sets the boundary once.
| What you might mean | What it is called here | Where it lives |
|---|---|---|
| One payer pays in several instalments | Installment splitting | POST /payments/{id}/splits |
| Your platform keeps a cut of a merchant's payment | Per-connection pricing | The X-Sync header |
| One payment shared between several merchants | Nothing | It does not exist |
Installment splitting
This has nothing to do with marketplaces. The same payer settles a single payment in two, three or four tranches, charged in sequence.
https://api.wajub.com/payments/{id}/splitsPass split_count for equal tranches, or split_amounts for unequal ones. The two are
alternatives, and split_amounts must sum to the payment total.
curl https://api.wajub.com/payments/trx_CSUGajfv9xh0XQ5wu2lx/splits \
-H "Authorization: sk_test.kZ3qP8mWvL2xR7tB5nY4hC6dF9jS1aG0eU3i…" \
-H "Content-Type: application/json" \
-d '{ "split_count": 3 }'split_count accepts 2, 3 or 4 and nothing else. For uneven tranches, send the amounts yourself.
curl https://api.wajub.com/payments/trx_CSUGajfv9xh0XQ5wu2lx/splits \
-H "Authorization: sk_test.kZ3qP8mWvL2xR7tB5nY4hC6dF9jS1aG0eU3i…" \
-H "Content-Type: application/json" \
-d '{
"split_amounts": [4000, 3000, 3000],
"split_currency": "XAF"
}'Between two and four values, each at least 0.01. One payer, one payment, several charges.
Per-connection pricing
This is the marketplace one. A payment attributed to a connection belongs to that merchant, and your platform is credited the commission configured on the connection.
curl https://api.wajub.com/payments \
-H "Authorization: sk.kZ3qP8mWvL2xR7tB5nY4hC6dF9jS1aG0eU3i…" \
-H "X-Sync: acc_7Yh2MpL4tRb3nP8sZcXv" \
-H "Content-Type: application/json" \
-d '{
"amount": 50000,
"currency": "XAF",
"customer": { "email": "buyer@example.com" }
}'There is no per-request override. The commission comes from the rules attached to the connection, which the merchant accepted and which only change with their agreement, and the payload carries no fee field at all. Account capabilities covers how the rule is chosen and clamped.
The one that does not exist
A single payment cannot be divided between several merchants
There is no split array naming several connections on one payment, on any plan and through any
endpoint. A payment carries exactly one X-Sync header, and the commission engine reads exactly
one connection from the transaction it settles.
A multi-seller basket is therefore several payments, one per seller, each with its own header.
| What that costs you | What to do about it |
|---|---|
| The buyer authorises more than once | Group by seller in your checkout and say so |
| Partial failure is possible | Treat each payment as its own order line, not one atomic basket |
| No shared reference | Put your own basket id in each payment's metadata |
The last row is the one that saves you later. Reconciling a basket after the fact is only possible if every payment in it carries the same identifier of yours.
Paying a merchant out is a third thing again
Neither feature moves money to a merchant's bank or wallet. Funds from a connected payment settle
into that merchant's own Wajub balance, and how they get out depends on the mode: a direct merchant
withdraws for themselves, a lite merchant is paid automatically by Wajub, and a relay marketplace
pays its sellers in bulk — all three are on Paying sellers. Your commission,
meanwhile, has already moved to your own balance without any call on your part — withdrawable once the
sale it came from clears retention.