Most crypto payment processors hold your money by default. I built one where custody is your choice

Hi IH,

I've been building Web3E, a crypto payment gateway built around one idea: you should decide who holds your money — not your payment provider.

Most crypto processors take custody by default. The customer pays them, the funds sit in their pooled wallet, and you request a payout later. That means withdrawal queues, frozen-balance risk, and someone else standing between you and your money.

Web3E flips the default. Out of the box, customers pay straight to a wallet you control and we never touch the key — we just run the infrastructure around the payment. If you'd genuinely rather we hold the balance and pay out on request, custodial mode is one setting away. Either way, it's your call, not ours.

Showing a wallet address is the easy part. The hard part is everything the customer never sees: detecting incoming transactions across 14 chains, counting confirmations, handling reorgs, under- and overpayments, expired invoices, FX-locking the rate for the payment window, delivering replay-proof webhooks, and keeping a double-entry ledger that never double-credits. That's where most of my time has gone.

Where it's at: live, 14 chains (stablecoins + native coins), REST API + hosted checkout, fee-only pricing — no setup or monthly fee.

Right now I care more about honest feedback than customers. If you were picking a crypto gateway:

• What's actually missing from the ones you've used?

• Which features are non-negotiable for you?

• What would make you leave your current provider?

• Would a public typed API (protobuf / ConnectRPC SDKs) matter to you, or is REST enough?

Tear it apart — especially if you've integrated crypto payments or built payment infra yourself.