Everything merchants ask before integration, plus the questions that come up on-call after launch. Eleven sections: signup, fees, integration, security, compliance, Lightning, refunds, subscriptions, coins, dashboard, business. Concrete answers with links to the docs.
Yes. Email + password, done. No documents, no verification call, no volume gate. This is a founding commitment, not a stage.
Yes. Any reachable email works. We only use it for security alerts, receipts, and password reset.
Yes — /dashboard/auth/google. Same account either way, linkable from settings.
Yes. We don't collect beneficial-owner info, so your registration is simply the email you used. Cosmetic "company name" in dashboard settings.
TOTP (Google Auth / Authy / 1Password) via /dashboard/account/2fa. No SMS option — we consider it strictly worse than TOTP.
If you've enabled 2FA backup codes, yes — our support flow uses the backup code as secondary proof. Without either email or a backup code, we can't verify you — account recovery is impossible by design.
Yes — from /dashboard/account/danger. Sweep your balances to an external wallet first; deletion is irreversible and wipes API keys, webhook history, and session tokens.
Each OrbChain account = one merchant. If you operate multiple brands, sign up each as its own account — own API keys, own balance, own webhook endpoint.
No tiers. 0.4% on day 1 and day 1,000. Fully published at /pricing.
No. $0 monthly, $0 signup, $0 per-API-key. Only 0.4% on settled volume.
On deposit crediting. Incoming payment minus 0.4% = net credit to your OrbChain balance.
No. Withdraw fees pass through at network-native cost. Full per-chain schedule at /pricing#withdraw-fees.
Depends on coin: BTC_LN sub-second. TRX/SOL/TON under 10s. ETH/USDT_ERC20 ~30s–2min depending on gas. Full queue-backed, never lost, never double-paid.
Nothing. Invoices that expire without payment cost $0.
The same coin the customer paid in. If you invoiced $100 in USDT_TRC20, you receive net 99.60 USDT on your balance.
No. Each billing-period invoice is just a regular invoice — 0.4% applies once when that invoice is paid. No per-subscription surcharge.
Not right now. The tariff is flat to avoid having one group of merchants subsidize another. If your scale is extreme and volume-based pricing becomes a real bottleneck, email [email protected].
At /openapi.json. SDKs auto-generate from it.
Yes — set your merchant account to "test mode" in /dashboard/settings. All endpoints mirror live with testnet/regtest coins.
Sign up, grab the API key, POST the invoice — no waiting list, no review period, no manual approval step. You can ship a test invoice the same minute.
5 retries at 2s, 4s, 8s, 16s, 32s. Every attempt logged to WebhookLog. Failed deliveries replayable from the dashboard.
Same order_id + merchant + coin → same invoice (no dupes). Webhook event_id is SHA-256-derived → retries carry the same id, dedupe on your side with event_id.
Per-API-key: 60 req/s burst, 1,800 req/min sustained on payment endpoints. Payout endpoints: 10 req/min for safety. Override available for documented high-volume flows — email us with the use case.
Expose your localhost via ngrok / Cloudflare Tunnel, set the URL in dashboard, switch on test mode. Or use /dashboard/webhooks/test which dispatches a canned event on demand.
Current live version is V2. We guarantee no breaking changes within a major version. When V3 ships, V2 remains available for at least 12 months in parallel.
Yes — every inbound request gets an X-Request-Id (you can supply one, or we generate one). Stored in AsyncLocalStorage across API → worker → outbound webhooks. Full trace per transaction.
On the hosted service we hold the master seed (KMS-sealed and non-exportable) and sign withdrawals — you don't hold your own private keys, and we won't pretend otherwise. What you control is the exit: every merchant sits on its own non-pooled BIP-44 branch, and you can auto-sweep each settlement to an external wallet only you control and withdraw on demand with no approval. If you need to hold the keys end-to-end, that's a self-hosted deployment. See /self-custody.
Master seed at rest in a KMS-sealed secret. Hot-wallet keys derived per-request, never persisted in plain form.
Yes. Set the hardware-wallet address as your auto-sweep target in settings.
The protection is structural, not a seed hand-off: turn on auto-sweep so every settlement is forwarded to a wallet you already control, keeping your on-platform balance near zero. Whatever has settled is already in your wallet, and each payment's Ed25519-signed receipt proves what you were owed — verifiable offline without us. We don't hand merchants the master seed (it derives every merchant's branch), so your recovery path is having already swept, not a personal export.
Every outbound webhook checks against a private-IP deny-list (loopback, 10.x, 172.16–31.x, 192.168.x, 169.254.x, link-local, multicast). No internal-resource exposure. Follow-redirects is disabled so a public origin can't 302 into an internal target.
No. We log metadata (path, status, duration, merchant_id, request_id). Raw bodies are only retained for webhook dispatch retries and expire with the retry window.
Internal security review and threat modeling is continuous. Third-party audit is on the roadmap — tell us if a specific audit (crypto / web / infra) is a procurement prerequisite and we'll prioritize.
Yes, at /dashboard/api-keys. Rotate without downtime — new key is issued, old key remains valid during your grace window. Revoke old once you've confirmed the new one works.
Yes. Every incoming + outgoing address checked against OFAC + UN + EU sanctions lists before acceptance/broadcast. Merchants notified of rejections via webhook.
Depends on your jurisdiction. OrbChain doesn't impose customer KYC; you're responsible for compliance with your own merchant-of-record obligations. See /aml.
We operate the wallet infrastructure, so we won't claim there's nothing we could be compelled to act on. The real protection is that you don't have to leave funds here: auto-sweep to your own wallet and withdraw on demand mean your on-platform balance trends to zero. We screen destinations against sanctions/denylists and would comply with a valid legal order — but funds you've already swept sit in a wallet only you control.
Globally, with exceptions for OFAC-sanctioned countries. Full list at /aml.
Whether OrbChain is a VASP in a given jurisdiction is a fact-specific legal question we don't assert a blanket answer to. Your own compliance obligations may apply regardless of how we're classified; consult your legal team. See /aml for what we screen.
No. OrbChain is a technology provider, not a tax intermediary. Signed receipts give you cryptographic records for your own accounting pipeline.
Full support. XMR is a legitimate asset with legitimate use cases. Sanction-list screening still applies on outgoing destinations where resolvable.
No. We operate a Voltage-hosted LND node + Boltz submarine swaps. You just accept BTC_LN.
Usually under 1¢ in routing fees. Our 0.4% platform fee still applies.
Lightning payments aren't reversible on-chain; refunds require the customer to provide their own Lightning invoice. Refund flow handles this.
Constrained by our node's channel liquidity — currently ~$5,000 per single invoice. Above that, use on-chain BTC.
Yes. POST /v1/payout with coin: "BTC_LN", destination = recipient's BOLT11 invoice. Sub-second settlement.
Customer's wallet shows "payment failed" and returns the funds. From our side, the invoice stays unpaid. Customer can retry from their wallet or we can regenerate a fresh invoice.
Yes, via Boltz submarine swaps — auto-swap between LN and on-chain BTC when a payout or sweep needs the other layer.
POST /v1/payment/:track_id/refund. Debits your balance, broadcasts back to the original sender, fires payment.refunded.
Yes — pass amount in the refund body. Multiple partials up to the original paid total.
The Ed25519-signed receipt for each PAID payment. On-chain confirmations are the ultimate audit trail.
Not a thing in crypto. Confirmed = final. Refund policy is your call.
No platform-imposed limit. As long as your balance in that coin is sufficient, the refund endpoint remains callable. On Monero, refund availability depends on your ability to re-send to a sub-address the customer provides.
Invoice stays CONFIRMING until full amount lands. Partial credits are never automatic. Reconcile via GET /v1/payment/:track_id and settle with the customer out of band.
Each period the billing-tick issues a fresh invoice. You notify the customer (email/in-app) with the pay URL. Manual pay = tradeoff for no-card-stored.
Default: 1 day, 3 days, 7 days. Configurable per-plan. Each retry = new invoice. After last rung, subscription cancels.
Yes — calculated on plan change and invoiced immediately as a one-off.
Yes. PATCH /v1/subscription/:id { "status": "paused" }. Resume shifts next_invoice_at by the paused duration.
Yes. Subscription settings let you toggle OrbChain-hosted emails or forward the subscription.invoiced webhook and send your own. Most merchants send their own so the brand is consistent.
Subscription runs through dunning, then cancels. Your downstream customer-success is outside OrbChain's scope — we just surface the lifecycle events.
Curated coverage of the chains where real-world payment volume lives. Supporting hundreds of coins means thin monitoring coverage on each — we'd rather ship 22 well than 200 poorly. See the full list at /currencies.
Email us your use case. New chains ship roughly quarterly; priority goes to chains where real customer demand exists.
Not strategic — just not shipped yet. USDT on BSC has real volume; it's on the roadmap.
Customer pays from their wallet, funds land in your Monero wallet — we don't operate a Monero node or custody XMR. Merchants accepting XMR run their own daemon or point at a service. The API surface for invoice/payout is identical.
Yes — you hold the coin after settlement. If USDT depegs you're exposed until you withdraw or swap to something else. Use Auto Settle to auto-convert to a coin of your choice at settlement time.
Not shipped yet. Monitoring pipeline supports multi-EVM in principle; specific rollup rollout depends on demand.
Nothing on the payment side — every dashboard action maps to an API endpoint. The dashboard is a convenience, not a privileged surface.
Same wallet + balances + send/receive, inside Telegram. Open @OrbChainBot, tap "Open wallet", sign in. Convenient for on-the-go merchants.
Role-based team access is on the roadmap. Today: one login per merchant. If you need team access, share credentials + 2FA backups securely and rotate when people leave.
Yes — every admin-level action (API key rotation, webhook URL change, auto-withdraw setting) logged to /dashboard/account/activity.
Theme + accent color + logo in /dashboard/settings/branding. For full control of the checkout surface, use White Label.
No. The 0.4% is deducted at settlement. Your balance statement shows every fee in every transaction — that's the bill.
Yes — /dashboard/statements emits a CSV with every deposit + fee + payout. Pair with the signed receipts for an auditable record.
Independently operated — private, bootstrapped, not investor-funded. Independence is load-bearing to our no-KYC commitment.
We commit to <60-second detection on every component outage (see /status) and public post-mortems on incidents >15 min merchant-facing. A contractual SLA with refund clauses is available for enterprise merchants on request.
Checkout surface: yes, via White Label. Full-platform resale isn't offered — our ops capacity is directed at running one tight platform, not many branded copies.
Still stuck? Email [email protected] — merchant questions get answered within the business day.
