Reference build: a crypto neobank backend
A neobank has to show accurate balances, screen money as it enters and leaves, and disburse funds on demand. This build wires the read, compliance and payout primitives into the account backend so all three run on a single prepaid balance.
面临的挑战
Standing up a crypto neobank usually means a balances API, a separate on/off-ramp screening vendor and yet another payout rail — three contracts and three keys behind one product. The goal is to source account state, ramp screening and disbursement from one key while keeping every credit decision auditable.
- Balances / portfolio / net-worthC2
- Address risk-score / exposureC3
- Transaction screening / KYTC3
- Mass payout / settlementC2
Show balances and net-worth per account
Populate each account view from one balances call spanning BTC, ETH and TRON, with portfolio net-worth derived in the same read so the home screen doesn't fan out to multiple providers.
Screen the ramp flows
Run risk-score on the counterparty at on-ramp and off-ramp, and route settled transfers through KYT for ongoing monitoring. Persist score, confidence and exposure next to each movement so the credit or hold is reproducible.
Disburse with mass payout
Pay out withdrawals and internal settlements in a batch from the same balance, tracking each transfer to confirmation instead of operating separate custody tooling.
该架构交付什么
- Account balances and net-worth sourced from a single read
- On-ramp and off-ramp screened inline with thresholds you control
- Disbursement and account state run on one balance, not three contracts
常见问题
Where does screening sit in the flow?
Risk-score runs at the ramp boundary before funds are credited or released, and KYT keeps monitoring settled activity afterward.
Do balances and payouts share funds?
Yes — reads and disbursement run against the same balance, so account state and payout settlement stay consistent.
充值、拿密钥、上线。
自助开通。支持加密货币或银行卡。按额度计费——重型原语更贵，简单调用很便宜。
获取 API 密钥