Connect Your Treasury System to Stablecoin Payment Rails

Every payment is approved and released in the treasury system first. The connector accepts only payments the TMS has released, and each instruction carries the release reference, so an auditor can trace any onchain transfer to the people who requested, approved and released it.

When treasury holds a stablecoin balance, the custody platform adds a policy the TMS does not see. A Fireblocks Transaction Authorization Policy sets rules on signers, destinations and amount limits, and by default an address outside Fireblocks must be whitelisted before funds can go to it.

We map TMS roles and limits onto that policy and keep the two in step, so a lowered limit or a leaver's removal applies in both places on the same day. For stablecoins held on an EVM chain in the company's own wallet, a Safe multisig enforces the approval threshold onchain.

A new supplier address gets the checks treasury gives new bank details. The supplier's master record carries a wallet address and a network in place of an IBAN, and a new or changed address is verified out of band, approved by a second person and whitelisted at custody before the first payment.

Each payee address is screened when it is added and again before the payment goes to the rail, on top of the rail's own checks. OFAC adds wallet addresses to the SDN List but says those listings are "not likely to be exhaustive", and its 2021 guidance notes that civil penalties generally rest on strict liability and points companies to blockchain analytics tools.

The screening therefore uses analytics as well as the list, through the provider you choose and our compliance integration work.

The rail, as the crypto-asset service provider, carries the Travel Rule duty. Under the EU Transfer of Funds Regulation it must make sure payer and payee data accompany every transfer, with no minimum amount, and may not execute a transfer before it has done so in full (Article 14(8)).

We have a supplier with a self-hosted wallet prove control of the address by sending a small amount from it or signing a message with its key, both among the methods the EBA's Travel Rule guidelines list for checking who owns or controls a self-hosted address. The connector fills those fields from the supplier master, the LEI included where you hold one.

A stablecoin balance can sit in one of three places, each with a different keyholder. With MPC wallet software the company runs, such as Fireblocks, treasury holds the signing authority and sets the policy. With a regulated custodian, such as BitGo Bank & Trust, a national trust bank, the custodian holds the keys and acts on the company's instructions, and BNY's institutional clients have been able to hold USDC in BNY's custody since June 2026.

With a rail's custodial wallet, as at Fipto, BVNK or Bridge, the balance stays with the rail and the company never handles a key. We wire whichever you choose to the TMS and the rail, and our crypto custody guide compares the models.

The connector's API keys for the rail and the custodian get the care of bank portal credentials: a secrets vault or hardware security module (HSM), each key scoped to the actions it needs, and scheduled rotation. If the paying company is itself a DORA financial entity, such as an insurer or a fund management company, the MPC software it runs is an ICT third-party service with a register entry and contract terms, while a regulated custodian, in our reading, usually falls outside as a financial service. Our DORA third-party risk guide sets out each provider type.

A settlement is posted only once it is final on its chain, meaning it can no longer be reversed. Each onchain settlement is matched to its instruction through the end-to-end reference and the transaction ID the rail reports, and a failed transfer returns to the TMS as an open payment. From the rail's records and an index of the company's addresses, built with our blockchain data indexing tooling, we produce a daily camt.053 statement and, where used, camt.054 notifications, which the TMS matches with its bank-account rules.

The posting rules split each payment into the stablecoin units, the fiat amount at the executed rate, the rail's fee and the network fee, each with a timestamp. They also record which issuer stands behind each token and whether the company can redeem it directly with that issuer, the terms the accounting treatment turns on.

The FASB's proposal of 18 August 2026 notes that an entity using stablecoins to transfer value without presenting them as cash equivalents "generally would have to separately track stablecoin transactions" for its statement of cash flows.

On Episode 6 of The Protocol Roundtable, the host asked Eric Queathem, Founder and CEO of Velocity, what his customers' treasurers require before they keep stablecoin balances, and he expected many of the questions to "come down to things related to accounting principles and things related to how these balances interact with different debt covenants that the organization has." The ledger feed gives your auditor and your lenders a complete record of every stablecoin movement.

Treasury sees stablecoin balances by entity, currency and chain in the daily cash position, next to its bank accounts. Most corridors include a conversion, such as euros into USDC before a payment or USDC into pesos at the payout. The booked rate is the one the rail executed, and we store an independent reference rate beside it, from Chainlink price feeds or your market data provider, so treasury sees the spread on every conversion. For payments that settle in a euro token, our euro stablecoins guide compares seven of them.

On an EU rail, a stablecoin balance earns no interest from its issuer or from the provider: MiCA Article 50 bars both from granting it and counts any benefit tied to the holding period as interest, even one paid by a third party. For cash meant to earn a return, our guide to tokenized treasuries and stablecoins compares the instruments.

The TMS shows the onchain leg and the payout leg as two statuses. Chains settle at any hour, while many bank rails at either end of a corridor keep cut-offs and close at weekends. A payment released on a Saturday can reach a supplier's wallet the same day, while a payout to the supplier's bank account may still wait for Monday.

We monitor each payment until both legs complete, along with rail API health, stuck or failed transfers, address-change requests and custody events. That watch runs around the clock under runbooks treasury approves, with the tooling of our managed onchain operations.