Skip to main content
Draft: specification in progress. Endpoints and fields may change.
Putting USDC cash to work in Treasuries looks like a simple integration. In practice, it involves a cross-network transfer rail, issuer relationships, allocation logic, an auditable record and a clear custody boundary. The API delivers all of this ready to use, without the company handing over its keys.

Building in-house vs. using the API

CCTP without shortcuts

USDC enters and exits through Circle’s Cross-Chain Transfer Protocol, which burns on the source network and mints on the destination network. There is no intermediate liquidity pool and no synthetic asset along the way. The API exposes each step as a record of type cctp.

Issuer integration

USDY (Ondo) and BUIDL (BlackRock) have their own eligibility rules, operating hours and minimums. TESA maintains these integrations and presents both assets in the same position, proposal and record format.

Allocation logic

The company defines the proportions and the rebalancing rules in its own policy. TESA does not recommend allocations or offer a preselected portfolio. When one of the company’s rules is met, for example a spread above the threshold it chose, the software prepares the transaction. The company decides: without approval and signature, nothing changes.

On-chain record

Every operation ends with a verifiable transaction hash. The records endpoint delivers the full trail for audit, accounting and ERP reconciliation.

Compliance boundary

TESA is non-custodial. The API never receives a private key or a signed transaction: it returns unsigned transactions and approval requests. The company keeps the same custodian, the same signing policies and the same internal controls. See Architecture.
The percentages and timeframes on this page are illustrative and may vary with each company’s policy and market conditions.