CapabilityFor banks

    Stablecoin settlement for banks and payment companies

    Short answer

    Add stablecoin rails beside your existing operations, with your compliance team in control.

    At a glance
    ComplianceAML, KYC, Travel Rule and sanctions checks before any rail
    Decisionsstay with your compliance team
    Scopewritten, tests first
    Termone quarter per outcome
    Paymenton accepted milestones
    IPpasses to you

    Bank-backed and fiat-backed stablecoins with custody and HSM key vaults, CBDC-linked designs and CBDC integration for banks (corporate wallets, payroll, ATM and POS), asset management infrastructure for banks (AssetBridge), permissioned chains with regulator validator nodes, account abstraction, fee engines, regulatory reporting. Sold through existing relationships only.

    Architecture

    How the pieces fit

    The bank owns

    Bank systems

    • Core ledger
    • Payment flows
    • Compliance team and its tools
    • Customer accounts

    We build

    Settlement layer

    • Routing with fallback
    • Accounting bridge and reconciliation
    • Custody with HSM key vaults
    • Fee engine and regulatory reporting

    Separate compliance layer

    AML, KYC, Travel Rule and sanctions checks run before any rail. Decisions stay with the bank's compliance team.

    Agent controls

    Mandate, spending limits, human approval above the limit, full action log.

    Chosen in scoping

    Rails and partners

    • Licensed issuers
    • On and off ramp partners
    • Stablecoin networks
    Indicative. The written scope names every system that is connected; nothing else is.

    Where the settlement layer touches core banking

    The settlement layer sits next to the bank's existing systems. It does not replace the core ledger. The touchpoints are agreed in the written scope, and nothing is connected that the scope does not name. They usually include:

    • Ledger and accounting. On-chain activity is reconciled to the bank's ledger through an accounting bridge.
    • Payment instructions. Payouts start in the bank's existing payment flows and are routed to stablecoin rails where the scope allows, with fallback when a partner is unavailable.
    • Custody. Keys are held with custody and HSM key vaults.
    • Fees. A fee engine applies the bank's own fee rules.
    • Reporting. Regulatory reporting draws on the same records.
    • Channels. Where a CBDC-linked design is in scope: corporate wallets, payroll, ATM and POS.

    How compliance stays separate from the stablecoin rails

    Compliance runs as its own layer between the bank's systems and the rails.

    • AML, KYC, Travel Rule and sanctions checks run in one orchestrated flow before a payment reaches a rail.
    • The bank's compliance team keeps its own tools, rules and decisions. We connect to them; we do not replace them.
    • Evidence for each transaction is stored with the payment record, so a payment can be followed from instruction to settlement.
    • Regulated activity runs through licensed issuers and partners. The licence picture for each market is confirmed during scoping.
    • Where AI agents or automated rules move money or make decisions, each one has a written mandate, spending limits, human approval above the limit and a full action log the bank can audit.

    What the bank owns and what we build

    The bank owns

    • The customer relationship and the accounts.
    • The core ledger.
    • Compliance policy and every compliance decision.
    • The choice of issuers and partners. We are vendor agnostic and take no vendor commissions.
    • The regulatory relationship and approvals.
    • The IP in the deliverables, which passes to the bank under the framework services agreement.

    We build

    • Routing to regulated on and off ramp partners, with fallback.
    • Multi-chain settlement.
    • Compliance orchestration that connects the bank's own checks.
    • The accounting bridge and on-chain reconciliation.
    • Custody integration, the fee engine and regulatory reporting, where they are in scope.
    • Dashboards for operations and finance, plus monitoring and runbooks for handover.

    The acceptance gate

    Nothing goes live and nothing is invoiced until it passes its gate.

    1. A written scope names one measured outcome, its baseline, the deliverables, exclusions, dependencies and acceptance tests.
    2. Each deliverable is a milestone inside one quarter, with its own tests.
    3. The bank's named owner accepts each milestone against its tests, with evidence attached.
    4. Regulatory dependencies and the bank's own approvals are part of the gate. Where a regulator must sign off, the milestone waits for that sign-off.
    5. Only accepted milestones are invoiced. Tests do not change without approval from both sides.

    How we work with banks

    Banking work runs through existing relationships. It starts with a discovery call, then a written scope with acceptance tests. No price is given before the scope.

    Proof

    Where have we done this before?

    All work
    Case · Banking · Central Asia

    Bank-backed stablecoin layer, with Visa

    Problem
    A Visa partner bank wanted crypto inside its own products.
    Built
    Business case review and a stablecoin design on AssetBridge.
    VisaStablecoinCBDCBank-issued stablecoin
    Phase 1 accepted; phase 2 approved, pending regulator.

    Next step

    Start with a scoping call

    A 30 minute call with Oleg. After it you get a written scope with acceptance tests, before any build starts.

    Oleg Pun

    CEO, Vareger

    Oleg Pun, CEO, Vareger