Circle Integration for Banks, Payment Firms and Licensed Crypto Firms
For banks, payment firms and licensed crypto firms on Circle Mint, CPN or CCTP, Protofire builds three things. They are booking in your ledger, Travel Rule data and a daily match against Circle's statement. Hyperlane's registry marks the Ethereum-to-Vana route "Deployed by Protofire" (merged 15 December 2024).

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
What Circle covers and what a Circle integration adds
Circle mints and redeems USDC and EURC under its own licenses. Circle also sends a signed webhook for each Mint event and delivers one camt.053 statement a day. The bookings, the Travel Rule records and the breaks behind those events are yours. So once you have chosen Circle, a Circle integration covers the rest, and Protofire builds that side.
For example, a wire left for Circle's settlement bank on Friday, and Circle shows the USDC as available on Monday. Your ledger still shows cash in transit.
How Circle Mint, CPN and CCTP connect to the firm's payment hub and ledger
Circle turns a payment instruction into USDC or EURC. Each movement comes back as a booking, matched each morning against Circle's camt.053 file.
Payment hub and back office
Circle account
Chains and wallets
Ledger connector
Travel Rule data and screening
Reconciliation and reporting
Circle webhook behavior and three changes in 2026
Circle's v2 webhooks cover 29 Mint event types, and they arrive at least once, in no fixed order.A redemption marked complete can still come back. If nothing handles these cases, month-end shows a gap between Circle's closing balance and your mirror account.
Three dates in 2026 change the work. Since 6 July 2026, MiCA entities must use mutual TLS on api-eu.circle.com. Enabling mutual TLS revokes the existing API keys at once. Circle's schedule completes the CCTP V1 shutdown on 1 December 2026, and V1 flows need new contracts and APIs (Circle). On 14 October 2026 the EBA classified USDC as a significant e-money token, so your vendor-risk file changes.
Four places where a Circle Mint cycle breaks
A Circle Mint cycle has two cash legs to book, the wire in and the redemption out.Either leg can return. Kostas Asimakopoulos of DDSC named the off-ramp limit on Protofire's Protocol Roundtable.
- Step 1
A wire that Circle cannot match
Your payment hub sends the wire following Circle's wire instructions. If the wire uses a virtual account number, Circle matches it without a reference. Without a virtual account number, the tracking reference goes in the memo, or the wire can come back. The cash waits on a transit account until Circle credits the balance. - Step 2
A payout that Circle's risk engine fails
Circle Mint pays out to recipient addresses registered in advance. Circle's risk engine can fail a payout after submission. Circle can also freeze USDC sent to or from a blocked address (USDC Terms). The connector that Protofire builds screens each counterparty first, and a failed payout opens a case. Today Circle SAS and Circle Singapore pay no self-hosted wallets. - Step 3
A redemption that returns after it is marked complete
A wire that comes back after it was marked complete is re-credited to Mint. The connector reverses the transit entry, and Circle's camt.053 file shows an Unwithdrawal line. - Step 4
A daily statement match that does not balance
Each morning the connector pulls Circle's camt.053 file for the previous UTC day. The opening balance plus the day's entries must equal the closing balance. Circle's day ends at midnight UTC, while RTP and SEPA Instant run at weekends. So finance decides in advance which business day a late redemption belongs to. An unmatched line opens a break, and the daily report lists the break until someone clears it.
I think the bottleneck here we see is only the case of off-ramping, because then we will rely on traditional rails. And this will limit us from offering the instantaneous payout that we might like if, for example, somebody requests that during a weekend.
Kostas Asimakopoulos, Head of Partnerships, DDSC · The Protocol Roundtable by Protofire, Episode 6, 45:51What you get from a Circle integration with Protofire
Each Circle movement booked once in your ledger
Each deposit, payout or returned wire becomes one entry under posting rules that finance agrees, even when Circle sends a webhook twice. Protofire builds the event service and the transit accounts. Circle Mint is the firm's own account, so client tokens left there are held with the firm's own. But MiCA asks custodians to hold client crypto-assets apart (Articles 70 and 75).
A daily report that finance can sign off
Circle's daily file is the statement, and your booking is the mirror, as with a nostro. Protofire archives each raw file and matches it to your bookings, your bank statements and the chain. The daily report ties Circle's closing balance to your Mint mirror account. Treasury sets a limit for the exposure to Circle. Our stablecoin reconciliation guide compares this approach with subledgers.
CCTP transfers booked as two legs
A CCTP transfer is a burn and a mint. The ledger records both legs and books each fee as its own entry. Fast Transfers stop when Circle's global allowance runs out, so transit entries age on Standard times. A V1 flow moves to the current CCTP.
Travel Rule data and holdings reports from your records
The Circle entity that books a payout decides which Travel Rule fields are mandatory. Circle SAS and Circle Singapore require originator, beneficiary, ownership and VASP data on each third-party payout, plus a purpose code. Protofire draws the data from your KYC records, and our EU Travel Rule guide compares the tools. Licensed crypto firms that hold USDC for clients also owe Circle a daily holdings report. MiCA requires that report (Article 22(3), applied to USDC by Article 58(3)), and Regulation 2024/2902 sets the template. Protofire posts the report from your ledger to Circle's Reserve Management API. Your DPO clears the holder fields of the quarterly template.
Circle API access that follows your authority matrix
Your vault or HSM holds the Circle API keys and the mTLS certificate. Protofire allocates keys within Circle's limit of ten per environment and sets the IP allowlist. For mTLS entities, we also keep a rotation calendar for keys that expire after 180 days. Dual approval can be set up in Circle's console or in your systems, and the access map shows which. Protofire's access is read-only by default, and no payout is sent without your approval.
A named owner for each alert
Alerts cover webhooks, payout states, risk denials, returned wires and CCTP transfers waiting for attestation. Each alert has an owner: Protofire's managed onchain operations team, or your staff, who hold the code and runbooks.
Circle issuers, EU status, interfaces and networks
- Issuers
- Circle Internet Financial, LLC issues USDC outside the EEA, and Circle Internet Financial Europe SAS issues it inside the EEA. Circle SAS issues EURC (MiCA redemption policy).
- EU status
- Circle SAS is an e-money institution authorized by France's ACPR. Since April 2026, Circle SAS has also been a MiCA crypto-asset service provider for custody and transfer of USDC and EURC (licenses). The EBA classified USDC as significant on 14 October 2026. The EBA supervises Circle SAS's reserves and redemption plans from 12 November 2026.
- Interfaces
- Circle offers REST APIs and v2 webhooks signed with ECDSA. Since 6 July 2026, MiCA entities use mTLS on api-eu.circle.com. A daily camt.053.001.13 statement has been documented since 27 April 2026 (release notes).
- Networks
- USDC was on 38 blockchains as of 16 September 2026 (USDC). Through Circle Mint, EURC is available on 9 chains (supported chains).
Checked November 2026 against Circle's documentation, legal pages and releases, and the EBA's classification.
Exit from Circle: what Circle keeps and what you can move
Circle keeps the Mint account and its deposit addresses, virtual account numbers, Address Book entries and webhook endpoints.USDC and EURC can move to other wallets and custodians, but the rest remains with Circle. The exit runbook gives each item an owner. Circle's API request logs expire quickly, so your own log and the archived camt.053 files are the audit trail.
EU holders keep a right to redeem at par (MiCA Article 49). For firms outside the EEA, Circle's Mint User Agreement says that Circle may be unable to close an account that holds a balance.
Under DORA, the Commission treats Circle Mint's e-money issuance as a financial service (DORA Q&A 2999). The same answer treats Circle Wallets hosting and the connector as ICT services. Your risk team classifies each service and owns the exit plan. Protofire drafts the technical runbook (DORA guide).
Our record: Hyperlane route, Avalanche Bridge and Chainlink CCIP
Public sources name Protofire for cross-chain transfer work.Cross-chain transfer work applies to the chain leg of a Circle flow: who attests and what each side books.
Hyperlane route between Ethereum and Vana, 2024
Hyperlane's public registry records the route that moves VANA between Ethereum and Vana as "Deployed by Protofire". The record comes from a pull request merged on 15 December 2024. Protofire also built the bridge interface for moving assets into Vana (Vana case).
Avalanche Bridge warden, 2022
In a post on Aave governance on 13 July 2022, Ava Labs named Protofire among the eight wardens of the Avalanche Bridge. The warden role is past, and Protofire runs no validators of its own today.
Chainlink CCIP
Protofire is a Chainlink core contributor and helps maintain Chainlink CCIP. See our CCIP integration page. For USDC alone, CCTP is the route to check first.
How a Circle project with Protofire runs
- Step 1
Review of your Circle setup before the call
Before the call, an engineer reads which Circle products you use, the ledger and hub they must reach, and your authority matrix. A written proposal follows. - Step 2
First phase: booking and the daily statement match
The booking connector and the daily match go in first, because the other modules book through the connector and are checked by the match. Tests cover returns, risk denials, expired CPN quotes and gas failures. - Step 3
Payment flows and data as each product launches
CPN Payouts, Payins or Fiat Payouts, Travel Rule data and holdings reports are built for the products you launch. - Step 4
The code, configuration and keys remain yours
The code, posting rules, configuration and runbooks are yours, and your staff keep the keys and approvals.
How work with Protofire starts
Tell us which Circle products you use, from Mint to CPN and CCTP, and which ledger and payment hub they must reach.Protofire reads that information before the first call. The terms in this section apply to each phase, as set out on how we work.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
When Circle, your bank or your hub vendor is enough
In four cases, Circle, your bank or your payment hub vendor is enough.
- Your bank gives you USDC. Standard Chartered and BNY let clients mint and redeem through the bank.
- Your payment hub ships a Circle connection. FIS, Finastra, Volante and ACI have announced one, and ACI's connection runs as a pilot in Colombia. Where your hub's connection is live, posting rules, the daily match and reporting are what is left.
- Your setup is a plain Mint account. Circle's solutions engineers support Mint customers into production.
- Circle should run the stablecoin side. With CPN Managed Payments, Circle holds the USDC, and the firm works only in fiat.
Protofire holds no license and moves no client funds. We do not open the Circle account, hold keys or approve payouts. Protofire also does not act as a CPN institution or give accounting or legal opinions. After go-live, we operate the integration only under a written scope.
FAQ
What is a Circle integration for a bank or payment firm?
Who can build a Circle integration for a bank or payment firm?
What does Circle leave to the firm?
How is USDC booked when it moves between chains with CCTP?
Can Circle Mint pay into a Fireblocks vault the bank already runs?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
