A multi-merchant payment gateway that routes stablecoin payments straight to your treasury. Hosted checkout, signed webhooks, sweep-direct settlement. No custody account, no monthly fee.
Every payment touches only the chain and a per-invoice address derived from your account. There's no Stabltap-controlled holding account collecting your customers' money.
POST a USDT amount to /v1/invoices with your secret key. We return a unique BSC address and a hosted checkout URL — no JS to embed.
Customer scans the QR (EIP-681 deep-link) or copies the address. The gateway watches the chain and tracks confirmations live on the checkout page.
After 12 confirmations we deliver a signed webhook and sweep the USDT to the treasury address you set. Network gas passed through; nothing held.
Production-grade primitives without the multi-coin sprawl. Built around the rails most merchants actually use.
Funds land at a per-invoice address and are swept on confirmation to the treasury address you control. We don't operate a pooled custody account.
BEP-20 USDT live on day one. Tron next, then ETH and TON. We'd rather ship one chain well than fifty chains badly.
HMAC-SHA256 with a per-merchant secret, replay-safe timestamps, six-attempt retry, dead-letter, and a one-click replay from the dashboard.
Server-rendered, mobile-ready, QR with EIP-681 wallet deep-link, live polling. No JavaScript SDK to integrate or version-pin.
HD wallet derivation isolates every merchant under their own derivation branch. No mixed deposits, no shared address pool.
Token-gated dashboard for hot wallet balance, sweep health, webhook deliveries, and recent errors. Enough to run the gateway without grepping logs.
curl away.Bearer auth with your secret key, JSON in, JSON out. The hosted checkout URL comes back in the response — point your customer there.
No monthly subscription, no setup fee. You pay only when you get paid.
Drops to 0.3% above $100k/month rolling volume — automatically, no negotiation.
Including the ones most gateways skip.
You configure a treasury address per chain. After a payment confirms, the gateway sweeps the USDT to that address. You hold the keys to it; we never do.
Honest footnote: between confirmation and the next sweep tick, USDT sits at a per-invoice address derived from a Stabltap-managed seed — typically minutes. During that window the funds technically touch a Stabltap-controlled key. We sweep on a tight cadence, but it's not "your keys for every second." If that distinction matters to you, run BTCPay self-host.
BSC USDT (BEP-20) is the only rail today. Tron USDT is the next one we're shipping, then ETH and TON. We'd rather support a small set of stablecoin rails properly than carry 350 coins most merchants never touch.
Twelve BSC blocks (~36 seconds) before an invoice is marked paid. The hosted checkout polls live and shows the customer the current confirmation count. Reorgs in that depth are vanishingly rare on BSC; we'll re-evaluate per chain when others come online.
One POST /v1/invoices from your backend with the amount and an optional reference. We return a hosted checkout URL — redirect your customer there. We deliver a signed invoice.paid webhook to your endpoint when it confirms. No JavaScript SDK.
HMAC-SHA256 over timestamp.body, with a per-merchant secret you regenerate from the dashboard. The header is X-Stabltap-Signature: t=<unix>,v1=<hex>. Stale timestamps are rejected. Failed deliveries retry six times over ~7 hours, then dead-letter — replayable from the dashboard.
Not in our current testing posture. Before we onboard real third-party merchants we'll bring KYC, sanctions screening, and tiered volume caps online. Treat the current build as closed beta: friendly merchants, small volumes, full transparency.
Cryptomus and NOWPayments hold customer funds in pooled accounts under their own keys; Coinbase Commerce settles to a Coinbase wallet. We sweep direct to the treasury you control — closer to BTCPay's posture than to a custodial gateway. Pricing is in the same neighborhood as Cryptomus's headline (0.4–0.5%); we just don't make you negotiate to get there.
Not today. The hosted SaaS is the product. White-label deployments are something we'll quote on request once we're past closed beta — but we're not promising an open-source release. If self-host is a must-have, BTCPay Server is the right call.
Sign up, set a treasury address, generate an API key. The first invoice is one curl away.