Split payments
Display inline code and code blocks
Monieswitch Split Payment feature enables automatic distribution of incoming payments across multiple sub accounts while handling commission fees. This powerful functionality is ideal for marketplaces, aggregators, and platforms managing multi-party transactions.
Before you start using the Split Payment
feature, you need to set up your sub accounts and configure the split rules.
How it works
When a payment is made to your Monieswitch account with any of our collections methods, the payment is automatically split and distributed to the sub accounts based on the split rules you have configured.
Subaccounts: A Prerequisite for Split Payments
Subaccounts are essential components that must be set up before implementing split payments. They represent the bank accounts that will receive portions of split transactions, enabling automated payment distribution.
Create subaccount
Subaccounts can be created via the Monieswitch Dashboard (if you signup as a Registered business
) or using the create subaccountAPI endpoint.
curl --location 'https://nini.monieswitch.com/subaccount' \
--header 'Authorization: Bearer {{merchantAPIKey}}' \
--data '{
"name": "Testing",
"bankCode": "000013",
"percentage": 2
}'
When a subaccount created via the API, the subaccountId
is returned.
Configure Split Payment
Split works by attaching subaccountId when creating checkout
or virtual account
curl --location 'https://nini.monieswitch.com/checkout/initialize' \
--header 'x-access-token;' \
--header 'x-pub-key: {{merchantPublicKey}}' \
--data-raw '{
"amount": 1000,
"email": "[email protected]"
"bearer": "account",
"subaccountId": "${subaccountId}",
"currency": "NGN",
"channels": ["BANK"]
}'
Transaction Fee Configuration
Fee Bearer Options
Control who bears the transaction charges for split payments. This setting determines which account is responsible for processing fees.
Available Options
Main Account (Default)
{
"amount": 10000,
"bearer": "account"
}
- Platform/merchant account covers all transaction fees
- Recipients receive full split amount
- Ideal for marketplaces prioritizing vendor satisfaction
Customer
{
"amount": 10000,
"bearer": "customer"
}
- End customer covers the transaction fees
- Added to total payment amount
- Suitable when passing fees to end users
Subaccount
{
"amonut": 10000,
"bearer": "subaccount"
}
- Specified recipient account covers the fees
- Deducted from their split portion
- Perfect for vendor-responsible fee structures
For detailed fee calculations and examples, visit our Pricing page
API
Refer to our API Documentation for integration details
Was this page helpful?