Invoice-to-wallet release controls for import distributors using stablecoins to pay suppliers without breaking AP policy or audit.

1. Oversubscribed funding around a control-layer company shows institutions are budgeting for operational software, not just new stablecoin access points.
2. Protect’s promise to screen sanctions, fraud, and policy violations before funds move turns pre-release decisioning into the category’s core workflow.
3. Unify’s single-ledger model across banks, custodians, wallets, and exchanges means stablecoin activity is now owned by finance teams that need controller-grade systems.
4. Claimed 99.41% payment coverage and tens of billions in monthly volume prove the workflow is already large enough for vertical software today.
5. More than 10,000 connected institutions and $30 billion safeguarded assets imply stablecoin ops is escaping crypto-native teams and becoming a mainstream finance-operations market.

Catalyst. Range’s funding and product claims show that institutional stablecoin usage has reached finance-owned workflows, making pre-execution approval and unified ledger evidence the next blocker for commercial payments.

Build an ERP-linked control layer that sits between AP workflow, payment provider, wallet or custody account, and the general ledger. For each proposed stablecoin payment, the product checks invoice status, vendor identity, approved wallet address, sanctions and policy rules, funding source, and separation-of-duties requirements before funds move. It creates an auditable case record with who approved what, the on-chain transaction details, FX basis, fees, and journal entries, then syncs the outcome back into ERP and close workflows. Customers start read-only with reconciliation and release evidence, then activate execution approvals and provider routing across banks, custodians, and OTC partners.

What's different. This is not another wallet, on-chain analytics dashboard, or cross-border payout API. The company owns the missing handoff between approved invoice and executed wallet transfer: counterparty-wallet binding, pre-release policy checks, maker-checker controls, and ERP-grade evidence. That workflow becomes sticky because it accumulates the customer’s approval graph, supplier-wallet map, exception patterns, and posting logic across multiple payment providers rather than one rail.

Jobs to be done

flowchart LR
  Buyer[Controller at import distributor] --> Pain[Urgent supplier payments bypass AP controls]
  Pain --> Product[Invoice-to-wallet release layer]
  Product --> Outcome[Faster supplier settlement with audit-ready control]

Executive takeaways

• Stablecoin rail supply is improving faster than controller-grade release controls.
• The strongest wedge is binding invoices, approved counterparties, wallets, and audit evidence before funds move.
• Budget is fragmented across rails, custody/policy, and crypto-accounting vendors, leaving room for an invoice-first control layer.
• Regulation increases implementation friction but also strengthens the need for documented approvals, screening, and reconciliation.

Market definition

A controller-grade stablecoin payment control layer sits between ERP/AP workflow and wallet, custody, or payment rails to enforce release policy, bind counterparties to approved wallets, and return audit-ready evidence to finance systems.

Customer and buyer

Primary users are controllers and AP operations leaders at import-heavy distributors; the economic buyer is the CFO or VP Finance; treasury and finance-systems leads shape implementation because the workflow touches both payment execution and close processes.

Buying triggers

• Urgent supplier settlements expose the mismatch between 24/7 stablecoin rails and slower AP approval processes. [19][100]
• A treasury or CFO stablecoin pilot creates immediate demand for wallet screening, evidence capture, and cleaner reconciliation. [4][9][12]
• Audit or compliance teams flag that wallet payments sit outside standard invoice approval and maker-checker controls. [16][95][96][99]

Willingness to pay

Budget is likely to come from enterprise finance-ops and compliance software lines already used for quote-led AP automation and digital-asset tooling; buyers will accept custom pricing when rollout starts with read-only evidence and measurable control gains. [64][70][95]

Category dynamics

Growth signal ≈65% CAGR in stablecoin market cap since 2021

Validation signals

• Range’s oversubscribed Series A shows investors will fund treasury, risk, and compliance layers around stablecoin usage, not only rails.
• Fireblocks reports that stablecoins already account for nearly half of transaction volume on its platform and that most surveyed firms are taking action.
• Stripe Treasury’s stablecoin accounts in 101 countries show mainstream PSPs are normalizing stablecoin balances and transfers for businesses.
• Conduit already models counterparties, payment methods, quotes, and offramps, suggesting the missing layer is orchestration rather than primitive rail access.
• Triple-A explicitly markets stablecoin cross-border payments to importers and exporters, validating the trade-payments use case.

Regulatory & technical constraints

• Customer and counterparty onboarding requires KYB/KYC documents, verified payment methods, and sometimes enhanced compliance documentation before funds move.
• Corridor launch depends on supported assets and operational onramp/offramp configurations, so coverage is not universal.
• Wallet screening and configurable exposure thresholds are table stakes for enterprise launches.
• Stablecoins create accounting, tax, and operational complexity that finance teams must solve alongside payment speed.

Competition is high but fragmented. Rail providers own execution, custody and policy vendors own wallet governance, and crypto-accounting platforms own post-trade books. No obvious incumbent owns the invoice-to-wallet approval graph for importer finance teams.

Why incumbents do not win by default

• ERP/AP suites. They own invoice approvals but do not natively manage wallet screening, counterparty-wallet binding, or onchain evidence across multiple stablecoin rails.
• Payment and stablecoin providers. They move money and expose onboarding and quote APIs, but they are optimized around execution rather than controller workflow and cross-provider AP governance.
• Wallet and policy platforms. They enforce asset movement rules well, but they start from wallets and keys rather than invoice context, vendor terms, and ERP posting logic.
• Crypto accounting tools. They reconcile after funds move and help with close, but they do not prevent a bad release before execution.

Stablecoin supplier payments are moving into finance-owned workflows faster than import distributors can extend AP controls to wallet releases. The first customer should be a $100M-$500M U.S. or European electronics or industrial-parts importer that already routes urgent Asia supplier payments through an OTC desk or stablecoin payment provider and processes 200+ overseas invoices per month. The product should start as an invoice-to-wallet control layer that binds approved invoices, counterparties, and wallets; runs sanctions and policy checks; captures maker-checker approvals; and returns journal-ready evidence to ERP before funds move. The coherent buying trigger is an urgent supplier settlement or internal-audit finding that exposes wallet payments as an unmanaged exception to normal AP policy. The initial proof point is not raw payment volume; it is a pilot that cuts urgent-payment release time, catches policy exceptions before execution, and produces audit-ready evidence for nearly every stablecoin payment. The company should not build custody, onchain analytics, or a general AP suite first; it should stay provider-neutral and own the release-control gap between ERP and payment rails. The main disconfirming risks are that stablecoin usage remains concentrated in too few corridors and that rail vendors or AP suites add good enough approvals before this company proves cross-provider value. Research still leaves gaps on which corridors convert first, who inside finance owns wallet-release approval day to day, and current exception rates, so the first 12 months should emphasize design-partner evidence over broad hiring.

Problem

• Import distributors testing stablecoin supplier payments still split invoice approval, beneficiary verification, wallet screening, and ERP booking across email, spreadsheets, provider portals, and finance systems.
• When a supplier needs after-hours or urgent settlement, controllers must choose between slow bank wires and wallet releases that bypass maker-checker policy and create audit exposure.

Solution

• Insert an ERP-linked control layer between AP workflow and OTC, custody, or payment providers to verify invoice status, vendor identity, approved wallet, funding source, and policy thresholds before any release.
• Create a case record with approvals, screening results, on-chain transaction details, FX, fees, and journal-ready evidence, then sync the outcome back into ERP and close workflows.

Why we win

• The wedge starts from invoice context and ERP posting logic rather than from wallets, keys, or post-trade reconciliation, which matches how controllers buy and evaluate risk.
• A provider-neutral approval graph, supplier-wallet registry, and exception history can become sticky across OTC desks, custodians, and stablecoin payment rails.
• Read-only launch plus approval gating reduces trust friction versus asking finance teams to automate fund movement on day one.

Milestones

flowchart LR
  Wedge[Importer invoice-to-wallet pilot] --> MVP[Release control and evidence MVP]
  MVP --> Proof[Faster approvals, fewer exceptions, audit-ready close]
  Proof --> Expansion[More entities, more providers, adjacent trade workflows]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least half of qualified target accounts already piloting stablecoin supplier payments will pay a separate control-layer budget before volumes are large.
• Controllers require wallet-specific approval and evidence workflows that current rails, AP suites, and accounting tools do not cover well enough.
• One ERP plus one execution-partner integration can launch a pilot in six weeks or less.
• Paid pilots can improve urgent-payment release time by at least 30% while delivering 90%+ complete audit evidence.
• Cross-provider supplier-wallet binding and approval history remain valuable even if individual providers add basic screening and routing controls.

Open diligence questions

• Which corridors and supplier profiles create the highest share of urgent stablecoin exceptions today?
• Does the CFO, controller, or treasury lead actually sign the first software contract when wallet release controls are the problem?
• How much verified wallet and journal-mapping work is needed before internal audit approves production use?
• Which provider or ERP partners will co-sell a neutral control layer instead of bundling shallow approval features?
• What share of early customers are truly multi-provider, making neutrality a must-have rather than a nice-to-have?

Model sanity

• Revenue engine. Base-case revenue comes from growing from 2 production entities at M12 to 36 by Q4Y3 at about $100K blended annual value per live entity.
• Must go right. Partner and founder-led sales must convert corridor pilots into governed production in roughly six months so customer growth outruns hiring.
• Model breaks if. If providers bundle good-enough controls and the business exits Y3 closer to 30 entities at lower pricing, cash compresses toward the downside low point.
• Next-round proof. The next financing is justified once Q4Y2 shows 8 production entities, one partner-sourced deployment, and one second-entity or second-corridor expansion.

Scenarios

Sensitivity

flowchart LR
  Leads[Qualified importer accounts] --> PaidPilots[Paid corridor pilots]
  PaidPilots --> Customers[Production entities]
  Customers --> Revenue[Subscription plus usage revenue]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> EBITDA[EBITDA]
  EBITDA --> Cash[Ending cash]
  Partners[Rail and ERP partners] --> PaidPilots

Flags: The model depends on partner-assisted deployment scaling from 8 production entities at Q4Y2 to 36 at Q4Y3; if referrals lag, revenue per FTE falls back below benchmark quickly. · Blended ARPU assumes live entities reach more than entry subscription pricing through usage and module attach; if customers remain near $60K-$75K ARR, the funding ask likely needs to rise. · Gross margin is held at the 70% plan target even though early ERP and provider onboarding may remain more services-heavy until templates standardize. · Cash stays positive on a $2.8M seed, but the downside case shows that one bad year of slower conversion would leave very little room before the next raise.

• Adoption timing. Stablecoin supplier payments may remain concentrated in a limited set of corridors and industries longer than expected. Mitigation: Start with customers already running urgent or hard-to-bank supplier corridors and keep the product multi-rail so ROI also comes from exception control and audit speed.
• Incumbent bundling. AP suites, payment providers, or custodians could add basic screening and reconciliation once stablecoin volume grows. Mitigation: Own the cross-provider invoice-wallet binding, approval graph, and ERP evidence layer that are harder for any single rail vendor to generalize.
• Workflow trust gap. Controllers will reject the system if wallet mappings or ledger outputs are even occasionally wrong on high-value payments. Mitigation: Launch read-only first, require human approvals and dual controls, and invest early in deterministic wallet verification and exception handling.