oblodai is a crypto payment gateway that lets a business take cryptocurrency the same way it takes cards: create a payment, show the customer a QR checkout, get a signed webhook when it confirms, and withdraw settled funds through a single API. Under the hood every deposit is watched on‑chain, credited to an immutable double‑entry ledger, swept into hot wallets, and paid out — while the actual private keys live in a separate, locked‑down signer that verifies each transaction against its own policy before it will sign anything.

The merchant API is Heleket‑compatible in shape (POST /v1/payment, /v1/payout, the {state, result} envelope, familiar field names and statuses) so migrating is mostly a base URL and a key — but authentication is upgraded to HMAC‑SHA256 + timestamp instead of a legacy md5 sign.

• 🌐 12 network families — EVM chains, Bitcoin & UTXO coins, Tron, Solana, TON, and more, with native and token (ERC‑20 / TRC‑20 / SPL / jetton) assets.
• 📒 Double‑entry ledger as the source of truth — balances are derived from an immutable journal that nets to zero per asset; a reconcile job re‑verifies integrity continuously.
• 🔐 Keys never touch the API — the core is watch‑only; the isolated signer verifies the real transaction bytes (RLP / BIP143 / Solana message / TON cells) against destination, amount, and chain before signing, behind caps and velocity limits.
• 💵 Integer money, everywhere — minor units end‑to‑end (big.Int, NUMERIC(78,0), decimal strings on the wire). No float ever touches a balance.
• ↩️ Full money lifecycle — invoices, fiat‑priced payments, automatic over/underpayment refunds, payment links, splits, referrals, and batch payouts.
• 🛡️ Dual‑control payouts — 2‑of‑2 co‑signing, kill‑switch, and daily caps for outbound funds.
• 🔔 Signed webhooks + SSE — HMAC‑signed, idempotent, retried event delivery, plus SMTP / Web Push / Telegram notifications.
• 🏗️ Fail‑closed in production — the stack refuses to boot with any dev stand‑in (static rates, plaintext seed, cleartext signer dial, missing admin token…).

Type‑safe clients for the REST API — payments, payouts, balances, webhook signature verification, and configurable retries — in five languages:

CMS & e‑commerce plugins (WooCommerce, and more) accept oblodai payments with HMAC‑verified, auto‑registered webhooks.

curl -X POST https://api.oblodai.com/v1/payment \
  -H "X-Public-Id: <your-merchant-id>" \
  -H "X-Signature: <hmac-sha256>" \
  -H "X-Timestamp: <unix-seconds>" \
  -H "Content-Type: application/json" \
  -d '{"amount": "49.99", "currency": "USD", "order_id": "order-1001"}'

You get back a hosted checkout URL and a payment id; oblodai handles the on‑chain detection and sends you a signed webhook the moment it confirms. See the full documentation →.

  merchant users ──▶  web (Next.js)  ──▶  backend (Rust BFF) ──┐  users, 2FA, staff RBAC,
                                                               │  dual-control, AML, SSE
  merchant servers ── HMAC /v1 API ──────────────────────────▶│
                                                               ▼
                                                       core (Go engine)   ledger, invoices,
                                                    api / worker / indexer payouts, sweep,
                                                               │           treasury, webhooks
                                                    gRPC (mTLS + HMAC), closed segment
                                                               ▼
                                                       signer (Rust)       keys, policy,
                                                                           tx binding, audit

A modular monolith over a single Postgres for the payment engine, an isolated signer VM for custody, and a Rust BFF for the merchant product — deployed with Docker, Helm, and OpenTofu/Terraform, with Prometheus alerts and Grafana dashboards.