Network Developer Portal
For mobile money operators, banks, fintechs, PSPs and switches. You integrate the Ultraner Network protocol once instead of building a separate bilateral connection to every network you want to reach.
This is the participant side of Ultraner, not the merchant product. If you are a business wanting to accept payments, the merchant API is what you want instead.
01
Connect
Ultraner issues your participant record and sandbox credentials. You sign every request with your own key, so we can prove a message came from you and has not been altered.
02
Test
Build against two simulated networks that behave like real ones: they hold balances, refuse what they cannot fund, time out, decline and reverse. Nothing you do here touches real money.
03
Certify
Run the published certification suite. It tests the paths that only matter when something goes wrong, because those are the ones nobody exercises before going live.
04
Go live
A passing run makes you eligible. Production access is then a deliberate decision by Ultraner, covering compliance and a participant agreement, not an automatic upgrade.
Nothing is assumed. A participant that can take funds may have no cross-border payout, and the routing engine has to know the difference before it selects you, not after a payment fails.
Collect
collect
Take funds from an account on your network.
Payout
payout
Credit an account on your network.
Account lookup
account_lookup
Confirm an address resolves before money moves.
Transfer
transfer
Move value between accounts you hold.
Reversal
reversal
Undo an authorization before settlement.
Refund
refund
Return funds after the destination accepted them.
The protocol, the signing scheme, the transaction lifecycle, the error taxonomy, the settlement model and the full certification suite are all published. You should be able to integrate a simulated participant without reading Ultraner's source code or asking us what a response means.
Open the documentation