Guides
Real jobs, real failure cases.
Each guide starts from something you need to ship and works through it on the v4 API, including what happens when a provider times out, a webhook arrives twice, or two systems disagree.
Implementation Guides
How do I build this?
Build your first payout
Send 1,500,000 COP from a wallet to a beneficiary and confirm the final outcome.
10 min →Handle a payout timeout safely
Your request timed out. Find out whether the payout exists and what state it is in, without sending the money twice.
8 min →Build a ledger-backed wallet
Hold a customer balance, reserve part of it for an operation, then consume or release the reservation.
12 min →Accept a local bank-transfer payment
Collect a PSE bank-transfer payment in Colombia and confirm it from webhook evidence and current status.
12 min →Process payment webhooks safely
Verify, deduplicate and act on payment events without turning a webhook into a second financial action.
10 min →Add a second payment provider without rewriting your product
Route pay-ins across more than one provider while your product keeps one payment lifecycle and one API.
12 min →Coordinate a cross-border financial operation
Connect a local collection, a conversion and a destination payout as related legs with their own state.
14 min →Architecture & Operations
How should I think about this failure mode?
For CTOs, heads of payments and operators deciding how money should move when providers are slow, ambiguous or wrong.
A timeout is not a decline
Why transport failure and economic failure are different, and what evidence you need before acting again.
7 min read →When payment failover is actually safe
Failover is a finality problem, not only a routing problem. Where it is safe, where it is not, and what runs today.
9 min read →Why financial state must survive provider disagreement
Your system says pending, the provider says completed. Why the last webhook is not enough to decide.
8 min read →Get sandbox access.
Sandbox access, API credentials and the full API reference are provided during evaluation.