Ocuula|Playground

Ocuula Playground

Try every payment engine against a real sandbox, no code required.

AI Rule SetupPreview

Describe your business. I'll configure the right rule.

1

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.

Inbound Payment SimulatorWebhook

Simulate a customer payment arriving. Watch Ocuula receive it and split it. Your server does nothing.

3

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.

Batch SplitBatch

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.

Retries on failure

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.

Stops when things go wrong

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.

Nothing gets lost

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.

No duplicate payments

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.