Why we built Ramps
At the Plan B conference in Prague in January 2026, we watched a panel of fiat ramp operators describe the same problem from different angles: MoonPay webhooks dropping. Transak events arriving twice. A regional AWS outage that took down reconciliation for thousands of wallet users at once.
These were not edge cases. They were the default. And every operator in the room was building the same workarounds — custom retry tables, dead letter queues cobbled together in Postgres, on-call rotations for 2am webhook failures.
We build global anycast networks for a living. We knew there was a better way.
The problem
Fiat onramps operate globally. Users buy USDT from Singapore. From São Paulo. From Lagos. From Zurich. The transaction is instant. The settlement is on-chain.
But the webhook that tells your wallet backend the purchase completed? That event travels to a single API endpoint in a single AWS region, often on the other side of the planet from the user who triggered it.
When that endpoint is slow, the event is late. When it is down, the event is dropped. When the provider retries, you get duplicates. This is the real cost of building on centralized webhook infrastructure.
What we built
Anycast Ramps is a global edge event fabric built specifically for this problem.
Webhooks from your providers terminate at the nearest of 40+ edge locations on NetActuate's global anycast network. Events are verified against provider signatures, normalized to a single unified schema, and durably persisted before delivery begins.
One integration connects MoonPay, Transak, Kado, Banxa, Coinbase, Stripe, AlchemyPay, and any provider via our JSONPath mapping engine.
Why anycast
We built Ramps on NetActuate's anycast network — the same infrastructure used for global DNS, DDoS scrubbing, and enterprise CDN delivery. BGP anycast means your webhook URL is announced from dozens of locations simultaneously. Traffic routes to the nearest healthy edge automatically. No single region can take your event delivery down.
USDT is decentralized. Its infrastructure should be.
What we believe
- Payment event delivery should be as reliable as the payments themselves
- Decentralized assets deserve decentralized infrastructure
- One integration should handle all your providers
- Every event should be traceable from ingestion to delivery
- Engineers should not be on-call for webhook failures