June 12, 2026
What scaling fiat-crypto ramps taught me about payments
- Payments
- Crypto
- Product
Moving money between fiat and crypto looks simple from the outside: a user taps "Buy", money leaves their bank, tokens show up in their wallet. Underneath, it's one of the least forgiving problems in fintech — every percentage point of failure is real money and real trust, and the rules change at every border.
Here are a few things I keep coming back to after building ramp products at scale.
Conversion is a function of trust, not just UX
You can shave taps off a flow all day, but on a ramp the biggest drop-off is almost always fear — am I going to lose this money, is this legitimate, why does it need my ID. The interventions that moved the needle most weren't form-field tweaks; they were clarity about what happens next, honest pricing, and visible signals that a regulated entity is on the other side.
Redundancy beats optimization
With 20+ payment providers, no single integration is ever "done." Acquirers degrade, banks throttle, a corridor goes dark for a week. The product that survives is the one that can route around failure — fall back to another provider, another rail, another currency — faster than a user notices. Designing for the failure path is the work.
Compliance is a product surface, not a gate
KYC/KYB and AML/CFT flows are where most ramps quietly bleed users. Treating them as a legal checkbox bolted on at the end guarantees friction. Treating them as a first-class part of the experience — progressive, explained, and tuned per jurisdiction — is the difference between an onboarding funnel that converts and one that doesn't.
Pricing is a promise with a stopwatch
When you quote a user a rate and hold it for 30 seconds, you've made a promise against a market that's moving the entire time. Getting that right means tight coupling between product, liquidity, and risk — and a lot of unglamorous work on the seams between systems.
None of this is unique to crypto. It's just payments, with the volume turned up and the margin for error turned down. That's also why it's some of the most interesting product work I've done.