Getting Started
How It Works - 60 Second Version
A plain-language walkthrough of how Papillae routes and executes payments.
Updated Feb 23, 2026
Here is the whole thing in plain terms.
You tell Papillae what you want to do. You can say it in plain language - "send $200 to Ahmed in Nigeria" - or you can send a structured API call if you are a developer. Either way, Papillae receives your intent.
The routing engine wakes up. It looks at every possible path to move that value. Which chain has the best liquidity right now. Which bridge is fastest for this corridor today. What the fee will be end to end. It has been running transfers and recording what works and what does not, so it knows things about specific corridors at specific times that no static routing table knows. It picks the best path.
Before anything moves, it simulates. The entire route runs as a dry run. Liquidity check. Slippage estimate. Compliance check. If anything fails in simulation, nothing moves and you get an explanation. This is the part that protects you.
If simulation passes, execution begins. Your funds move through a Papillae smart contract deployed on the source chain. The contract handles every hop internally - swap if needed, bridge to the destination chain, hand off to the local off-ramp partner. You signed one approval. The contract handled everything after that.
On the other end, the off-ramp partner - a licensed local financial institution - converts to local currency and delivers to the recipient's bank account or mobile wallet. They receive naira, pesos, or Philippine pesos. They did not need a crypto wallet. They did not need to know any of this happened.
The whole thing fires a webhook back to whatever system initiated it. Done.