Case studies

How SquareFi added regulated stablecoin infrastructure through one API

Embedded finance
  • MainUSD

    Live on Polygon and Ethereum

SquareFi is built on a single conviction: launching a modern financial product shouldn't require assembling a different vendor for every rail. Its platform gives fintechs and global businesses accounts, cards, wallets, fiat and crypto conversion, and cross-border money movement through one API and one white-label stack, the unified layer that teams would otherwise stitch together from five or six separate providers. That premise is what took the company from stealth to processing $250 million in transaction volume while operating across more than 150 countries.

Stablecoins were always central to that thesis. For a platform whose job is moving money across borders, a regulated dollar that settles in seconds and reconciles cleanly isn't a feature bolted onto the roadmap. It behaves more like a settlement primitive, the thing other flows are built on top of. The catch is the distance between wanting stablecoin rails and being able to operate them. Issuing a regulated stablecoin, holding and attesting reserves, running redemption, and keeping the whole apparatus compliant is, in practice, a company of its own. SquareFi didn't want to become that company. It wanted the capability, cleanly, under its own brand.

SquareFi embedded Brale to close that gap.

The challenge

Moving value between fiat and stablecoins at production scale takes regulated issuance, custody that satisfies an auditor, reserve management with real banking relationships behind it, on- and off-ramps that clear reliably, and a compliance program that survives the diligence a serious counterparty will run. That layer is a licensing exercise before it's an engineering one. For most teams it's quarters of work and a permanent operating burden, and none of it differentiates the product their customers actually chose them for.

For a company whose entire value proposition is collapsing fragmented infrastructure into one stack, rebuilding the hardest piece of that infrastructure in-house would have been the wrong trade. SquareFi needed a partner that already operated the regulated layer in production and exposed it as something a team could build against, not a roadmap it would have to wait on.

What Brale runs underneath SquareFi

Brale operates regulated stablecoin issuance and orchestration as a single system, delivered through one API. It was a known quantity going in, not a bet. The same infrastructure already settles roughly $500 million a month for Coinflow and issues native stablecoins for Canton Network, where Brale also runs as a validator. SquareFi was integrating against a regulated layer that operates under SOC 2 controls, multi-party custody, and U.S. money-transmission licensing, with production volume already running through it.

Regulated issuance and reserves, without becoming the issuer

SquareFi's stablecoin workflows run on top of Brale's regulated issuance and reserve infrastructure. Brale operates minting, redemption, custody, and the reserve management that keeps balances fully backed, so SquareFi can extend stablecoin capabilities to its own customers without holding the issuance licenses, carrying the reserve banking relationships, or absorbing the regulatory obligations of a stablecoin issuer. SquareFi gets the economics and branding of its own dollar; Brale carries the regulated operating company underneath it.

On-ramps and off-ramps inside one integration

Conversion between fiat and stablecoins is where fragmented stacks usually break, because the ramp provider, the banking partner, and the custody layer are rarely the same system. Brale exposes on- and off-ramp infrastructure through the same API as issuance, so the issuance and redemption cycle for SquareFi's branded dollar reconciles through one system — dollars in, stablecoins out, fiat back on redemption — rather than requiring separate issuance, banking, and custody vendors.

One regulated layer instead of vendor sprawl

The alternative SquareFi avoided is the one its own customers come to it to escape: issuance from one provider, custody from another, compliance tooling from a third, blockchain infrastructure from a fourth, each with its own contract, integration surface, and failure mode. Consolidating that into a single regulated layer meant SquareFi's engineering time went to the platform its customers use rather than to maintaining the connective tissue between providers nobody sees.

For an embedded finance company, using the Brale APIs, the API endpoints are:

  1. 1

    Create API credentials

    Brale Dashboard → Settings → API → Create Application

  2. 2

    Create or use the platform account

    account_id = SquareFi / embedded finance platform account

  3. 3

    Register the customer's bank account as an external address (if debit)

    POST
    /accounts/{account_id}/addresses/external
  4. 4

    Register the customer's Utila wallet as an external address

    POST
    /accounts/{account_id}/addresses/external
  5. 5

    On-ramp $100 from customer bank to customer Utila wallet

    POST
    /accounts/{account_id}/transfers
  6. 6

    Track transfer status via webhook

    Subscribe to Brale webhooks for real-time updates, including transfer.completed

  7. 7

    Transfer MintUSD to another user

    POST
    /accounts/{account_id}/transfers
  8. 8

    Off-ramp $100 from customer Utila wallet back to bank

    POST
    /accounts/{account_id}/transfers

You can find additional resources in the Brale Commons repo outlining different functions of the API used.

Brale underneath, SquareFi in front

Brale is built to disappear into the product. Issuance, custody, compliance, and movement run behind SquareFi's platform; SquareFi keeps its brand, its customer relationships, and its product experience intact. To the businesses building on SquareFi, the regulated stablecoin layer simply works, with no sign of the infrastructure operating it.

The result

SquareFi is live on Brale, connecting stablecoin and fiat workflows inside a single platform, and is building toward deeper issuance use cases where SquareFi and its customers can put branded stablecoins to work in their own products.

The capability SquareFi set out to offer is in market. The regulated infrastructure beneath it is not something SquareFi had to build, license, staff, or defend in diligence, which is precisely the point. The hard layer became a dependency it could rely on rather than a company it had to become.

What this means for fintech infrastructure teams

SquareFi's situation is the common one, not the exception. A platform has a clear customer problem and a roadmap it believes in, then runs into the single layer it can't ship around: regulated stablecoin infrastructure. Building it doesn't just cost time. It turns the team into a different kind of company, one that operates licenses and reserves instead of the product it set out to build.

Brale exists to take that layer off the table. Issuance, ramps, custody, and compliance operate underneath, so the platform in front competes on distribution, experience, and the customers it serves. For SquareFi, that's what made stablecoin capabilities a feature of the product rather than a second business to run. It's the difference between adding stablecoin infrastructure and becoming a stablecoin infrastructure company.

For a platform that moves money across borders, a regulated dollar that settles in seconds is the primitive everything else is built on. Owning that dollar under our own brand — and the economics that come with it — used to mean becoming a stablecoin company. With Brale, it's a capability we switch on.

Anton Lobintsev
Anton Lobintsev
Co-Founder & Chief Product Officer, SquareFi

Features used

  • Stablecoin issuance
  • On-ramp / off-ramp
  • Fiat-to-stablecoin conversion
  • Custody
  • Reserve management
  • Multi-chain gateway
  • API-driven workflows
  • Compliance and reporting workflows
Add stablecoin capabilities without building the issuer stack

Reach out to our team