Describe your business. I'll configure the right rule.
Try every payment engine against a real sandbox, no code required.
Describe your business. I'll configure the right rule.
Money moves: inbound or outbound
A customer pays into your wallet (inbound), or you initiate a payout from it (outbound). Either way, Ocuula intercepts the transaction and applies your rule at that moment.
Simulate a customer payment arriving. Watch Ocuula receive it and split it. Your server does nothing.
A rule decides how the money splits
Before any transaction, you define a rule: who gets what and how. Pick an engine below, configure it, and test it with real sandbox money.
Divide any payment by percentage instantly.
Pay fixed GHS amounts, remainder goes to a designated recipient.
Hold funds until a threshold, then split.
Better splits as your 30-day volume grows.
Automatically pull money from a customer wallet on a schedule, then split it.
Or pay out many people in one go
When you need to settle with multiple parties at once (vendors, drivers, creators), batch lets you trigger up to 100 splits in a single API call instead of looping one by one.
Combine multiple rules and amounts into one request. Ocuula processes each and tells you what passed and what didn't.
Under the hood
Every payment, regardless of engine, runs through the same infrastructure. You don't configure any of this. It just works.
If a payout fails (say the network dropped or the provider had a hiccup), Ocuula quietly tries again, up to 5 times. You write zero retry code.
If the payment provider keeps failing, Ocuula stops sending requests to it and waits 30 seconds before trying again. A bad moment stays a bad moment, not a full outage.
If a payout fails for good (like a wrong account number), it gets saved in a list instead of disappearing. You can review it and resend when ready.
Send a unique key with each split request and Ocuula won't process it twice, even if your server accidentally sends the same request more than once.
Sandbox only. No real money moves.