Bank-program OS for emerging-market commercial banks approving stablecoin-funded settlement into local business accounts.

1. A $13.5M Series A led by Bain Capital and Variant Fund signals that bank-linked stablecoin settlement in emerging markets has moved from speculative infrastructure to funded deployment.
2. Infinia says the capital will fund regulatory licences across Latin America, Africa, and Asia, which means permissions and compliance expansion are the immediate bottlenecks.
3. The product description centers on bridging traditional banking networks with digital-asset infrastructure for businesses, pulling banks into day-to-day stablecoin operating workflows.
4. A rollout spanning Latin America, Africa, and Asia creates repeatable corridor-activation work that software can standardize above the underlying rail.

Catalyst. Infinia's new funding is explicitly earmarked for regulatory licences and multi-region expansion, showing that local-bank approval and ongoing operating control—not raw rail access—has become the gating workflow.

Build a bank-program desk that sits between the bank, the fintech applicant, and the settlement infrastructure provider. Before launch, it collects partner licences, KYB, corridor rules, purpose-code logic, reserve mechanics, and approval workflows into one committee-ready packet. After go-live, it ingests daily settlement files and exception events to reconcile local-bank credits against stablecoin funding, flag limit breaches, and produce regulator-ready evidence. Banks start with one corridor and one partner, then expand the same control model across additional countries and program types.

What's different. Rail providers help money move, but they do not give the bank a neutral workspace to approve a partner program, memorialize corridor-specific controls, and monitor exceptions after go-live. Generic GRC tools can store documents, yet they do not understand reserve mechanics, settlement evidence, or release conditions tied to stablecoin-funded bank credits. Over time, the product compounds a proprietary map of which partner profiles, control packages, and operating metrics clear bank committees fastest in each jurisdiction.

Jobs to be done

flowchart LR
  Buyer[Bank partnership lead] --> Pain[Stablecoin program approvals stall in email and committee loops]
  Pain --> Product[Bank-program approval OS]
  Product --> Outcome[Faster launches and monitored local-account settlement]

Executive takeaways

• [1][2][3] Infinia’s funding, website, and docs show that the rail problem is no longer just moving stablecoins; it is clearing local KYC/KYB, banking-mandate, and corridor-specific approval friction around rails like Pix and SPEI.
• [5][8][9][10][11][14][15] Regulation makes the approval workflow bank-owned: Brazil is already constraining who can run crypto-linked cross-border settlement, while global and bank-supervision bodies keep pushing functional oversight, daily reconciliations, and stronger third-party controls.
• [18][20][21][23][24][26][27][28] Demand in Latin America is increasingly institutional, but adjacent vendors are moving up-stack from execution. The best wedge is a neutral bank-program approval and monitoring layer, not another payments API.

Market definition

[1][2][4][5][8][9][11][23] The relevant market is bank-owned approval and monitoring software for stablecoin-funded settlement programs: a workflow layer that helps commercial banks review partners, corridor rules, reserve and reconciliation design, and post-launch evidence before local-bank credits are released.

Customer and buyer

[2][8][9][10][20][31] Daily users are transaction-banking partnerships, risk, compliance, and operations teams inside mid-sized Latin American banks evaluating stablecoin-linked business settlement. The economic buyer is usually the head of transaction banking, COO, or fintech-partnership GM who must get committee approval and own the ongoing control evidence.

Buying triggers

• A fintech partner proposes stablecoin-funded settlement into local business accounts and the bank needs a committee-ready package covering licensing, KYC/KYB, account structure, and settlement controls. [1][2][5][8][9][26][27]
• A local-rail rollout such as Pix or SPEI makes speed table stakes, so the gating issue shifts from payment mechanics to who can approve, monitor, and defend the program. [4][5][21][22][26][29]
• Audit, regulator, or bank-oversight reviews require daily reconciliations, beneficial-owner visibility, and bank-owned evidence rather than vendor screenshots. [8][9][10][31][32]

Willingness to pay

Budget is likelier to come from launch-readiness, audit-risk reduction, and treasury-operations efficiency than from a “crypto” line item. Fireblocks reports active bank and PSP implementation, Bain describes global CFO frustration with slow and opaque cross-border rails, Trovata frames reconciliation as a structural ERP-versus-bank gap, and the FDIC is explicitly pushing daily reconciliation and direct record access in certain third-party account structures. [20][33][32][10]

Category dynamics

Growth signal ~93% implied CAGR in cross-border B2B stablecoin transaction value from 2026 to 2035

Validation signals

• Infinia is explicitly raising capital to connect banks to digital-asset rails and expand licenses across Latin America, Africa, and Asia.
• Circle now offers both network-based and managed stablecoin settlement products for PSPs, fintechs, banks, and global platforms.
• Bitso and Trace already market local-rail-plus-stablecoin workflows across Latin America, showing the technical rails are commercially live.
• Fireblocks reports 90% of respondents are taking action on stablecoins and says banks are prioritizing cross-border payment use cases.
• Chainalysis and Bitso both show Latin American stablecoin activity is already large and commercially meaningful.

Regulatory & technical constraints

• Brazil’s Resolution 561 restricts crypto-linked eFX settlement to BCB-authorized institutions and adds segregation and reporting obligations.
• Mexico’s Circular 4/2019 sets specific rules for banks and fintech institutions operating with virtual assets.
• Argentina’s PSAV regime adds formal registration and documentation workflows for virtual-asset providers.
• Bank-third-party arrangements raise operational, compliance, liquidity, and end-user confusion risks that banks must actively govern.
• Banks facilitating stablecoin payments need AML, sanctions, wallet-screening, and Travel Rule processes around the full payment lifecycle.

[1][20][21][23][24][25][26][27][28][31] Competition is strategic rather than category-pure. Rail providers, orchestration networks, and compliance vendors already cover execution, wallets, and monitoring. The open gap is a provider-neutral system of record for bank sign-off, corridor-specific controls, and post-launch exception evidence.

Why incumbents do not win by default

• Rail providers. Infinia, Trace, and Bitso Business solve last-mile money movement and local-rail connectivity, but their incentive is to route flow through their own network rather than preserve a bank-neutral approval record across multiple providers.
• Stablecoin orchestration networks. Circle, BVNK, Bridge, and Zero Hash abstract wallets, liquidity, and fiat conversion well, yet they begin from execution and infrastructure rather than from the bank committee workflow that decides whether a partner program can launch.
• Compliance and monitoring vendors. Fireblocks, TRM, and similar vendors help with wallets, monitoring, and controls, but they do not own the end-to-end bank approval packet tying partner licensing, corridor eligibility, reserve design, and local-account release conditions together.
• Generic bank risk and treasury stacks. Generic bank risk and treasury systems already hold workflow budgets, but OCC/FDIC-style expectations and stablecoin-specific reconciliation needs still require domain logic above document storage and manual controls.

Stablecoin Bank Approval OS should start as a Brazil-first control layer for mid-sized Latin American commercial banks reviewing one stablecoin-funded settlement program into local business accounts. The urgent pain is not rail connectivity alone; it is converting partner licensing, KYB, corridor rules, reserve design, and release conditions into a bank-owned approval packet that can survive committee, audit, and regulator scrutiny. The MVP should handle one bank, one partner fintech, and one corridor by combining diligence intake, policy templates, sign-off workflow, and post-launch daily evidence reconciliation. This wedge is narrower and faster to prove than another cross-border payments API because Pix- and SPEI-linked off-ramp capability already exists while bank approval and monitoring remain bespoke. Go-to- market should target a $5B-$30B bank at the moment a stablecoin-linked SME trade program reaches risk committee or regulator pre-filing, sell a paid pilot tied to one launch, and price per live program or corridor rather than by seats. Research supports an estimated "$315.0M" TAM, "$44.1M" LatAm SAM, and "$3.6M" year-3 SOM, but those figures assume stablecoin settlement remains concentrated in institutional treasury and trade corridors where approval pain is acute. The biggest disconfirming risks are that bank policy variation makes deployments too services-heavy, or that rail providers bundle enough shallow governance tooling to block standalone budget. Public inputs still do not identify named live bank design partners, baseline rejection or exception rates, or real procurement cycle times, so the first 90 days must collect committee artifacts and close at least one paid pilot before stronger investor conviction is warranted.

Problem

• Commercial banks evaluating stablecoin-funded settlement still stitch together outside-counsel memos, spreadsheets, email threads, and vendor dashboards to decide whether one partner program is safe enough to launch.
• After launch, the bank often lacks its own daily evidence tying local-account credits, reserve mechanics, and exception handling together, which slows audits and keeps expansion to new corridors or providers risky.

Solution

• Provide a bank-owned workspace that collects partner licences, KYB, account structure, corridor rules, reserve logic, and committee approvals into one versioned launch packet for a single program.
• Add read-only ingestion of provider events and bank settlement files so operations can reconcile daily activity, flag breaches, and export regulator-ready evidence without depending on rail-vendor screenshots.

Why we win

• The startup sells into the approval and evidence gap between rail execution, generic GRC, and crypto monitoring tools: the bank needs a neutral system of record, not another payment network.
• A Brazil-first wedge aligns the product with the sharpest regulatory pain, where authorized-institution, segregation, and reporting requirements make reusable control templates valuable immediately.
• Each deployment compounds approval outcomes, corridor templates, and cross-provider exception data that are hard for any single rail vendor or in-house workflow to replicate quickly.

Milestones

flowchart LR
  Wedge[Brazil first bank approval wedge] --> MVP[One bank one corridor approval and evidence MVP]
  MVP --> Proof[Faster committee sign off and daily reconciled evidence]
  Proof --> Expansion[Multi corridor multi provider bank governance platform]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 8 of the first 15 beachhead banks must describe stablecoin-program approvals as a current multi-team project rather than a theoretical future workflow.
• At least 2 of the first 5 qualified bank opportunities must sign paid pilots before demanding a bundled rail-vendor solution.
• The first 2 pilots must cut either approval-cycle time by at least 30% or audit or evidence-prep hours by at least 50%.
• One common control schema must cover at least 80% of approval fields across the first Brazil and Mexico deployments without custom code per bank.
• Provider and bank data feeds must support automatic reconciliation of at least 80% of monitored settlement and exception events in pilot scope.

Open diligence questions

• Which exact documents, thresholds, and sign-offs do 3 named Brazil or Mexico banks require before first live stablecoin-funded settlement approval?
• Who owns budget and procurement for this project: transaction banking, COO, risk, or digital partnerships?
• How much of the approval packet can be templated across banks versus rewritten with local counsel each time?
• Will rail providers such as Infinia, Trace, Bitso, or Circle-class partners co-sell and share data, or build their own shallow governance tooling?
• What are the current baseline metrics for days to approval, committee cycles, and hours spent assembling audit or regulator evidence?

Model sanity

• Revenue engine. Base-case revenue comes from scaling from 3 paying bank logos in Y1 to 10 by Q4Y3 while average logo value rises as second-program and reporting scope attach inside existing banks.
• Must go right. The company must prove one production Brazil program and one repeatable rail or counsel referral motion by Q4Y2 or the sales-cycle sensitivity dominates the model.
• Model breaks if. If committee reviews slip by one to two quarters and gross margin stays in the mid-60s because template reuse fails, the downside case turns cash negative before seed-ready proof.
• Next-round proof. The seed story is strongest once 5 paying bank logos, 2-plus production conversions, Mexico-ready templates, and clear expansion revenue inside existing banks are visible.

Scenarios

Sensitivity

flowchart LR
  CommitteeStageBanks[Committee-stage banks] --> PaidPilots[Paid pilots]
  PaidPilots --> ProductionLogos[Production bank logos]
  ProductionLogos --> ExpansionScope[Second corridors and reporting scope]
  ExpansionScope --> Revenue[Revenue]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Cash and runway]

Flags: The base case still assumes five new bank logos land in Y3, so at least one referral or co-sell channel must become predictable rather than opportunistic. · Per-logo revenue assumes some banks add a second corridor or partner plus reporting scope; if banks remain single-program, Y3 revenue falls toward the downside case. · Gross margin only approaches the 70% target late in Y3, so persistent local-counsel or template-rewrite work would keep the model services-heavy. · The company holds GTM headcount flat after the first partnerships hire; if founder-led selling does not scale with partner introductions, pipeline capacity becomes the bottleneck. · Cash is modeled as EBITDA, so implementation prepayments, security or compliance capex, and billing timing could shift actual runway.

• Bank sales drag. Regional banks may agree with the thesis but still take quarters to approve new software and new stablecoin programs. Mitigation: Start with banks that already have a live fintech-partnership team and an imminent committee review, and co-sell through infrastructure providers that create the project in the first place.
• Rail-vendor bundling. Infrastructure vendors like Infinia could extend their own dashboards into basic bank approval and monitoring features. Mitigation: Stay vendor-neutral and own the bank's cross-partner governance record, committee workflow, and multi-provider operating evidence rather than raw rail execution.
• Jurisdiction sprawl. Rules across Latin America, Africa, and Asia may diverge enough to make the product feel like a consulting business. Mitigation: Begin with one region and one program archetype, codify reusable control templates, and make local rule logic configurable instead of hard-coded.