Inside Soap, Episode 01: The Map
What really happens between the tap of "Deposit" and the money landing in an account? Dozens of systems inside Soap wake up at once. So the Soap team built something unusual: an internal 3D mapping studio where we can rotate, zoom, and trace the entire payment journey end to end. 80 components. 7 layers. 18 payment flows. All in one place.
Explore the map yourself: a simplified, public version with every layer and the payment flows you can play step by step.
What does the path from click to settled funds look like?
The map is how we see the path from click to settled funds, layer by layer:
| Layer | What it does |
|---|---|
| People | Merchants, their customers, and the Soap team. |
| Surfaces | What people actually touch: checkout, onboarding, the merchant dashboard and the SDK. |
| Edge | Where every request enters the system. |
| One backend | Runs every provider, every webhook and every background job. |
| One ledger | Records every charge, dispute and payout. |
| Routing | Moves a payment to the next processor when one says no. |
| Compliance | Checks that run before a single dollar moves. |
Why build a tool just to understand what we built?
This is Inside Soap, Episode 01: The Map. A first look at how we actually understand the system we're building. A single payment crosses the surfaces, the edge, the backend, the ledger, routing and compliance in seconds. Seeing all of it in one place is how the team, and the AI agents that work with us, keep the whole system in view. Read more about how we build in Inside the Soap AI Software Factory.
What's the most complex flow you've ever had to map?
Video script
You just tapped Deposit. Ever wonder what actually happens next?
Every time someone taps Deposit, dozens of systems inside Soap wake up.
Here's what that looks like, sketched out.
Up top: the people. Merchants, players, and the Soap team.
Then the surfaces they touch: checkout, onboarding, the dashboard, the SDK.
Below that, the edge, where every request comes in.
At the core, one backend runs it all: every provider, every webhook, every background job.
Every charge, dispute, and payout lands on one ledger.
Around it, dozens of partners.
If one processor says no, Soap routes to the next.
And compliance checks run before any money moves.
Eighty components. Seven layers. Eighteen flows.
And it's interactive. Click the link, and explore every layer yourself.
Frequently asked questions
What happens after a customer taps Deposit?
Dozens of systems wake up at once. The request comes in through the edge, one backend picks it up and talks to the payment provider, compliance checks run before any money moves, routing picks a processor, and the result lands on one ledger alongside every other charge, dispute and payout.
What is Soap's 3D mapping studio?
It's an internal tool the Soap team built to see the whole payment system in one place. You can rotate, zoom and trace a payment end to end, from the click to settled funds, across 80 components, 7 layers and 18 payment flows.
Why build a map of your own payment system?
A payment touches many systems in a few seconds, and no one can hold all of them in their head. A shared map makes it easier to explain how money moves, to spot where a flow can fail, and to plan changes without surprises.
Why does Soap run on one backend and one ledger?
Keeping every provider, webhook and background job in one backend, and every charge, dispute and payout on one ledger, means there is one place to look when a merchant asks where their money is.
Want to see how your payments would flow through Soap? Book a call.