Skip to content

Stablecoin Reconciliation for Banks, Payment Firms and EMT Issuers: Crypto Subledgers, Custody Reports, Provider Statements or a Ledger-Side Build

Each stablecoin movement leaves three records: a chain event, an entry at the platform that signed or sent it, and a general ledger posting. A bank, payment firm or e-money token (EMT) issuer can tie them together in four ways. The ways are a crypto subledger, the custody platform's own API and reports, a statement the stablecoin provider sends, or the firm's own indexer and matching engine feeding the core banking GL. Cryptio, Bitwave, TRES and Lukka are crypto subledgers, and Circle Mint sends a daily camt.053 as its provider statement. Matching keys, fees, chain coverage, mint and burn handling, audit trail, MiCA reporting, connectors and the owner of each break separate the four ways. Vendor documentation was read on 5 November 2026.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at Protofire · Updated November 2026

TL;DR

Four kinds of route bring onchain stablecoin movements to the general ledger. Each mint, burn, transfer and network fee can then be matched to a ledger posting and to the bank or provider record behind it. Crypto subledgers (Cryptio, Bitwave, Lukka and TRES Finance) match chain, custody and exchange records and sync journals to ERPs such as NetSuite or SAP. Fireblocks agreed to acquire TRES Finance in January 2026 and now sells TRES beside its own custody platform. Custody platforms such as Fireblocks and BitGo expose hashes, fees and statuses and leave the matching to the client. Circle Mint has documented a daily ISO 20022 camt.053 statement covering USDC and EURC since April 2026. Circle Mint's statement is the only provider statement of that kind we found. A ledger-side build indexes the firm's own addresses and posts to its core banking GL, and the firm owns every break.

Protofire sells the fourth route on this page, a ledger-side build. The build consists of indexers over a firm's own addresses, matching rules, and the postings and statements that feed the firm's core banking general ledger. We also integrate the other three routes. We wire a subledger, a custody platform's API or a provider's camt.053 file into the systems a firm already runs. Every option below can therefore involve work for us. None of the vendors named here sponsors or endorses this guide. Protofire is an onchain engineering firm founded in 2016 and part of the Altoros group. Protofire holds no payment, e-money or crypto-asset license and audits no one's accounts. Our stablecoin payout rails guide compares how the payments leave a firm. The custody and core banking integration guide compares the wiring between a custody platform and core banking. The other comparisons are on the guides hub.

Scorecard

How do the four routes compare on keys, fees, chains, reporting and breaks?

Matching keysHash, UID or any metadata field (Cryptio), plus wallet labels kept in the tooltxHash, externalTxId, note (Fireblocks); txid, sequenceId, comment (BitGo)Circle transaction ID, chain, transaction hash, custom reference, IMAD or UETR (Circle Mint camt.053)The keys you join: end-to-end ID, transaction hash, Travel Rule message ID, deposit address owner
Fees and gasAs the tool imports them from chain and custody data; fee handling is not described in the public docs we readNetwork fee per transaction: feeInfo at Fireblocks, feeString at BitGoProvider fees as their own entries (Circle Mint fee codes, BVNK FEE type); network gas is not a listed Circle entry typePosted as a separate line in the token that paid it
Chains90+ (Cryptio); more than 35 (Bitwave); 230+ (TRES, per Fireblocks)Every chain the platform supports, wallet by walletChains the provider supports for its own accountsAn indexer per chain family the firm uses
Mint, burn and reserve matching for issuersSupply tracking of mints, burns and wallet movements (Cryptio)Sees the mint and burn transactions the issuer signs; no fiat or reserve sideMint and redeem entries on the client's Circle account; Circle reports its own reserve weeklyEach mint and burn matched to the fiat receipt or redemption and the reserve account movement
Audit trailBreak logs, roll-forwards, balance attestations; SOC 1 and SOC 2 Type II reports stated by Cryptio, Bitwave, Lukka and TRESPlatform transaction history and audit logs, under the custodian's own controlsA statement file per day, retained like bank statementsThe firm's own logs and retention; no third-party SOC report unless it commissions one
MiCA and EMT reportingNo Article 22 templates documentedNone documentedNone documentedFeeds the firm builds: Article 22 data where it applies, CASP records with hash and token identifier
ERP and GL connectorsNetSuite, SAP, Oracle, Workday, Dynamics 365, Sage, Xero, QuickBooks (varies by vendor); no core banking system namedNone in the custody API; Fireblocks sells ERP-ready data through TRES, and subledgers connect to Fireblocks and BitGocamt.053.001.13 loads into a bank reconciliation engine that reads that version and Circle's supplementary data; other rails by APIPostings in the core banking or ERP format, plus a camt.053 if wanted
Who owns breaksThe firm's finance team, working in the vendor's toolThe firm's operations team, with the custodian's support deskThe provider for its own side; the firm for the match to its ledgerThe firm, end to end
Where it stopsCore banking postings and camt.053 output; bank lines only where the tool ingests bank dataWallets on other platforms; bank statement linesWallets and custodians outside that providerCost basis, fair value and tax lots, unless built
In detail

Where does each route take its data, and what does it leave to you?

01

Crypto subledger

An accounting platform pulls chain, custody and exchange data, matches it and syncs journals to the ERP
Strengths
  • +Matching across sources is built in. Cryptio matches 'by hash, UID or any metadata field' across order systems, ERPs, custodians and onchain data.
  • +Chain and custody coverage is bought ready-made. Cryptio reads 90+ blockchains through verified node runners. Bitwave lists more than 35 blockchains and connectors for Fireblocks, BitGo, Anchorage Digital, Coinbase Prime and Paxos.
  • +Audit evidence comes in a form auditors know. Cryptio produces balance attestations, break logs and roll-forwards, and Cryptio, Bitwave, Lukka and TRES each state SOC 1 and SOC 2 Type II reports.
  • +Cost basis and valuation are included for tokens held on balance sheet. Lukka tracks FIFO, LIFO and specific identification.
  • +Bank-side data is starting to arrive. Cryptio markets reconciliation of onchain movements with core banking systems, and Fireblocks lists 10,000+ banks among TRES data sources.
Trade-offs
  • −Crypto subledgers are built around ERPs. The Cryptio, Bitwave and Lukka connector lists name NetSuite, SAP, Oracle, Workday, Xero or QuickBooks, but none of them names Temenos, Avaloq or FIS.
  • −None of Cryptio, Bitwave, TRES, Lukka or Alloy Crypto documents a bank statement output in camt.053 or MT940. A bank's own reconciliation engine therefore does not receive the result in its usual format.
  • −None of the subledgers documents MiCA reporting templates. Cryptio mentions MiCA only for audit-ready logs.
  • −A third party holds the full transaction history and wallet map. The subledger is an ICT service that a bank, payment firm or CASP lists in its DORA register of third-party arrangements.
  • −The tool flags breaks, but the firm's finance team still resolves each one
  • −The vendor list keeps changing. Fireblocks agreed to buy TRES in January 2026, Integral now trades as Alloy Crypto, and Taxbit's site no longer sells its corporate accounting suite.

A crypto subledger is a layer between the chains and the ERP. The subledger reads wallets, custody accounts and exchange accounts. It labels each movement, for example as a payment, an internal transfer, a fee or a mint. It then values each movement and pushes summarized journal entries to the general ledger. Cryptio's reconciliation product promises to "Reconcile across OMS, ERP, custodian and on-chain data simultaneously", reads "90+ blockchains via verified node runners" and gives finance "balance attestations, break logs and roll-forwards ready for Big 4 auditors across MiCA, SOX and SEC". Cryptio's integration list names Dynamics 365, NetSuite, Oracle Fusion, SAP, Workday, Xero and QuickBooks among ERPs. The same list names Fireblocks, BitGo, Circle, Copper, DFNS and Zodia among custody sources. Cryptio's homepage shows Circle and Paxos among customers. Cryptio's funding announcement of March 2026 named Société Générale's SG Forge, an EMT issuer.

Bitwave's integrations page lists Oracle NetSuite, Sage Intacct, QuickBooks, Xero, Campfire and Rillet as live ERP connectors. The page marks Kyriba and Oracle ERP Cloud as coming soon. Lukka sells reconciliation logic, cost basis and "GL integrations (SAP, Oracle, Geneva, NetSuite, etc.)". Fireblocks entered into an agreement to acquire TRES Finance in January 2026. Fireblocks now offers TRES as its Financial Data product, "natively integrated with Fireblocks". The acquisition release names Bank Frick and Finoa among more than 200 TRES customers. The release also quotes Fireblocks' CEO: "banks and fintechs need reconciliation and controls that align with their existing ERP and ledger systems."

For a bank, the question is which ledger receives the subledger's journals. The connector lists name ERPs. Cryptio's page for banks promises reconciliation "with core banking systems" but does not name one. So a bank whose general ledger is its core banking system confirms the connector with the vendor. Alternatively, the bank maps the subledger's journal export into the core itself, or runs the subledger beside the core for accounting and audit. In that last case, operations reconcile elsewhere. A crypto subledger also counts what it sees, which means the wallets and accounts the firm connects. Bitwave's own blog names FV Bank, a US digital-asset bank, as a customer for client and tax reporting. The TRES release lists Bank Frick, a Liechtenstein bank, without saying what Bank Frick reconciles.

02

Custody platform reports and APIs

The wallet platform that signs each transfer is the source of record, read through its API, webhooks and exports
Strengths
  • +Every transaction has the fields a matcher needs. Fireblocks returns the transaction hash, the client's own externalTxId, a note, source and destination addresses and a feeInfo block that holds the network fee. BitGo returns txid, a per-wallet sequenceId, a comment and feeString.
  • +The vendor documents a balance check. Fireblocks tells clients to wait for COMPLETED, then for a balance event at the same or a later block height, and compare with the chain.
  • +Reorganizations show in the status. BitGo marks a transfer 'removed' after a chain reorganization and 'replaced' when a new transaction supersedes it.
  • +There is no new vendor to assess, because the data comes from a platform the firm has already contracted and put through due diligence
Trade-offs
  • −A custody platform's data covers only the wallets on that platform. Funds at a second custodian, in a rail's wallet or in a self-hosted wallet need another source.
  • −The custody API returns raw data only. The firm or a subledger builds the matching to bank lines or invoices, the journal entries and any camt.053. Fireblocks sells the subledger layer separately, as TRES.
  • −The platform's references are kept in-house. Fireblocks sends customerRefId to the client's AML provider and 'never to the counterparty', and a payer's own reference does not arrive with an ERC-20 transfer.
  • −Edge cases differ by chain. On Fireblocks, a TRX or SOL transfer can reach COMPLETED with no balance event after it, so the balance is polled once.
  • −For BitGo Go Account (OFC) withdrawals, txid holds an internal BitGo hash. The onchain hash is stored in the transfer's metadata under onChainTxId, so the matcher has to read that field.
  • −Field names differ by vendor, so two custody platforms mean two mappings

Every custody platform keeps a transaction record that holds the identifiers a reconciliation needs. Fireblocks' API reference gives each transaction a txHash and an externalTxId. The client sets the externalTxId, which Fireblocks "highly recommends". Each Fireblocks transaction also has a free-text note, addresses, block information and a feeInfo object that holds the network fee. The note is not written to the chain. Fireblocks' balance validation guide sets out the check. The client waits for a transaction with status COMPLETED, then for a balance event "with a blockHeight equal to or greater than the transaction's blockHeight". The client then compares the balance with the chain at that height. The guide adds: "Each balance event contains the full balance, not a delta." Fireblocks sends the customerRefId field only to the client's own AML and transaction-monitoring provider.

BitGo's transfer object holds txid, a sequenceId, a comment, the fee as feeString, the block height, confirmations and a state. The client sets the sequenceId, which is unique per wallet. The state moves from initialized and pendingApproval to confirmed, failed, removed or replaced. BitGo also produces holdings and transaction reports as CSV or PDF, and trust clients receive quarterly statements.

A custody platform's API covers only the platform's own record. A bank still has to join the platform's record to the payment instruction that caused it and to the fiat leg on its bank statement. The bank then has to book the result. A subledger or a ledger-side build does that join, and both read these same custody APIs. The subledgers that do it include the TRES layer that Fireblocks now sells.

03

Statements from the stablecoin provider

The issuer or payment rail reconciles its own book and sends a statement the firm loads like a bank account's
Strengths
  • +The statement fits a bank's existing reconciliation. The firm can load Circle Mint's daily camt.053.001.13 statement into the same engine as its bank statements, where that engine reads version 001.13.
  • +One file covers USDC and EURC. The file shows opening and closing balances (OPBD, CLBD) and a BOOK, PDNG, RJCT or FAIL status on each entry.
  • +Fiat and chain references appear side by side. Each entry lists Circle's transaction ID, the chain, the transaction hash, the client's custom reference and, when supplied, the transfer's reference such as an IMAD or UETR.
  • +Mints and redemptions come from the issuer's own book and have their own entry codes (Mint, Redeem). Circle's own redemption, payout and payment fees arrive as separate entries.
  • +Rails without camt.053 still send structured reports. BVNK delivers CSV, PDF or JSON by webhook or email, daily, weekly or monthly, with a one-hour lag in production.
Trade-offs
  • −Circle Mint was the only provider we found documenting a camt.053. BVNK, Bridge, Fipto and Monerium document REST APIs, reports or webhooks without one.
  • −The onchain keys and the token name are stored in Circle's supplementary data block (SplmtryData), and the standard currency codes read USD and EUR. So the matching engine must be set up to read that block to tell a USDC entry from a dollar wire.
  • −The statement covers the provider's account only. Tokens the firm holds in its own wallets or at another custodian are outside the statement.
  • −A break on the provider's side becomes a ticket to the provider, which resolves it on its own timetable
  • −Timing is end-of-day. Circle's statement covers the prior UTC day, and Circle commits to delivering it by 06:00 UTC, so intraday positions still come from the API.

Circle added documentation for daily camt.053 statements on 27 April 2026, according to its Mint release notes. Circle's statement reference says one camt.053.001.13 file covers "the prior calendar day from 00:00 through 24:00 UTC" and is typically ready around 02:00 UTC. The file is delivered by 06:00 UTC. The file has a separate statement block for each currency. Circle-specific data is stored under SplmtryData/CircleTxn in the fields TransactionId, Token, Blockchain, TransactionHash, CustomReferenceId and ExternalReferenceId. ExternalReferenceId holds the electronic funds transfer reference when one is supplied, for example an IMAD or UETR. A client requests the statement through the reports API with reportType camt053. On Circle's managed payments keys, a separate camt_managed report applies.

Rails other than Circle Mint send structured reports without the ISO 20022 wrapper. BVNK's reconciliation endpoint produces reports that contain a transaction ID, a merchant reference, the transaction hash and fees as their own transaction type. Bridge gives each deposit a deposit_message that the customer "MUST include" in the wire memo, ACH description or SEPA reference. Bridge returns IMAD, end-to-end ID and SEPA reference fields. Bridge also returns a blockchain_memo "only allowed when the payment rail supports memo, e.g. Stellar". Monerium's EURe is minted and burned against SEPA payments. Monerium maps a memo to the ISO 20022 unstructured remittance field (RmtInf/Ustrd, up to 140 characters). Monerium maps a reference to the structured field (RmtInf/Strd, up to 35).

A provider's statement format matters because statements are moving to ISO 20022 on their own timetable. J.P. Morgan's ISO 20022 FAQ says that "the end-of-coexistence period for statements and reporting message is November 2028", while cross-border payment messages between banks on Swift moved in November 2025. A provider that sends camt.053 today uses the format that banks are moving their statements to.

04

Ledger-side buildProtofire's model

Index the firm's own addresses, match each movement to its instruction and post to the core banking GL
Strengths
  • +Covers every wallet and chain the firm uses, whichever custodian, rail or issuer moved the funds
  • +The firm chooses the matching keys. One record joins the payment's end-to-end reference, the transaction hash, the Travel Rule message ID and the wallet's owner.
  • +The build posts in the core banking system's own format and can write a camt.053 in the version the bank's reconciliation engine reads. Subledger connector lists name no core banking system.
  • +For issuers, each mint and burn is matched to its fiat receipt or redemption payment and to the reserve account movement
  • +The firm keeps MiCA record fields, such as the transaction hash and an ISO 24165 token identifier, in its own systems
Trade-offs
  • −The firm owns the code, the indexers and the node access for every chain. The firm also keeps them current through chain upgrades.
  • −ERC-20 transfers have no memo, so attribution on EVM chains depends on per-client deposit addresses or on references held off chain
  • −Every break is the firm's to investigate, with no vendor queue behind it
  • −Cost basis, fair value and tax lots are absent unless the firm builds them. Subledgers sell them ready-made.
  • −Posting rules need a finality threshold for each chain, and ethereum.org puts Ethereum finality at about 15 minutes. A firm that posts earlier has to handle reversals.
  • −Taurus documents booking straight into Temenos for its custody platform. A bank that already uses that pairing may need far less of its own.

A ledger-side build reads the chains directly for the addresses the firm controls. The build uses open-source indexers such as The Graph's graph-node, Substreams, SQD or Ponder, or a commercial data provider. On EVM chains the source is the ERC-20 Transfer event, which "MUST trigger when tokens are transferred, including zero value transfers". The ERC-20 standard also says a mint SHOULD emit the event from the zero address.

The ERC-20 Transfer event has sender, recipient and amount and nothing else, so the business reference comes from elsewhere. That reference comes from a deposit address assigned per client, the custody platform's externalTxId, or the Travel Rule message. The Transfer of Funds Regulation allows the Travel Rule message to go off chain, provided it is sent "in advance of, or simultaneously or concurrently with" the transfer (Art. 14(4)). The EBA's Travel Rule guidelines treat a transfer to or from a self-hosted address as individually identified when "a unique identifier for each transfer is used, such as a transfer hash or a reference number".

In a ledger-side build, the matching engine joins chain events, custody records, provider reports and bank statement lines. The engine posts a transfer only once the transfer is final. For Ethereum, ethereum.org says "It takes about 15 minutes for an Ethereum block to finalize". Rollups and other chains publish their own stages. Network fees are usually paid in the chain's native token, so they post as their own line. The firm keeps a native-token balance on each chain to pay them. Payment chains such as Arc and Tempo are the exception. Arc uses USDC as gas, and Tempo takes fees in stablecoins.

For a CASP, the records follow Delegated Regulation (EU) 2025/1140, which asks CASPs to record "the transaction hash or other identification alphanumerical string". The same regulation asks CASPs to identify crypto-assets with an ISO 24165 digital token identifier or an ESMA-approved equivalent. A CASP keeps these records for five years, and for up to seven on request (MiCA Art. 68(9)).

For some pairings, a vendor route reaches the same result as a ledger-side build. Taurus wrote on 18 December 2024 that with its Temenos integration "Transactions involving digital assets are booked directly in the Temenos core banking system, ensuring real-time booking and reconciliation alongside traditional asset transactions." A ledger-side build makes sense in two cases. One is a firm that holds funds across several custodians, chains or providers. The other is a firm that runs a core banking system no vendor connects to.

Verdict

Which route fits your stablecoin flows?

If your priority is
Several tokens on balance sheet, books in NetSuite, SAP or Xero

your ledger is an ERP that the subledger's connector list names, you need cost basis and audit-ready roll-forwards, and your auditors accept a vendor's SOC reports as part of the control set.

→Crypto subledger
If your priority is
All funds in one custody platform, an operations team that writes its own rules

every wallet you hold is on one platform, and you will build the join to bank lines and the postings yourself or in a subledger on top.

→Custody platform reports
If your priority is
Minting and redeeming USDC or EURC through Circle Mint

most of your stablecoin flow passes through your Circle account, and you want that flow in the bank reconciliation engine you already run, configured to read Circle's supplementary data block.

→Provider statements
If your priority is
A bank or EMT issuer posting to Temenos, Avaloq or FIS across several providers

funds are held across custodians, chains and rails, your general ledger is the core banking system, and you will own the indexers and every break, or pay a firm to run them.

→Ledger-side build
Also consider

Where do treasury systems, accounting rules and the blueprints fit?

  • Treasury systems as the destination: a corporate or payment firm may reconcile in its treasury management system instead of the GL. Kyriba and Circle announced USDC inside Kyriba on 28 April 2026. Today the integration shows supported USDC balances in Kyriba for reporting, reconciliation and liquidity oversight. Kyriba's Circle page lists execution as a future phase. On 8 June 2026 Kyriba and Fipto announced that Ledger and Mantu run live stablecoin payments through Fipto inside Kyriba. Reconciliation of those payments is done in Kyriba. Bitwave lists Kyriba among its coming connectors.
  • Other subledgers: Integral now operates as Alloy Crypto, which has QuickBooks, Xero, NetSuite and Sage connectors. Ledgible, from Verady, covers tax reporting and digital asset accounting. Ledgible connects to Advent Geneva, NetSuite and SEI, among others. Cryptoworth calls itself a crypto subledger for NetSuite, Sage, QuickBooks and Xero. Taxbit now sells tax compliance only, and Coinshift's site no longer offers treasury tooling.
  • Accounting rules for the balances: the FASB's proposal of 18 August 2026 sets out what a stablecoin would need to meet the existing definition of a cash equivalent. The proposal's conditions include an on-demand contractual cash redemption right and a direct redemption right with the issuer for known amounts of cash. The conditions also include segregated reserves of at least one to one in short-term, highly liquid assets. The comment period ends on 19 November 2026. Redeemable stablecoins generally fall outside the fair-value rules of ASU 2023-08. The IFRS Interpretations Committee's 2019 decision on crypto holdings covers only tokens that no party issues and that give the holder no contract. So the IFRS decision leaves fiat-backed stablecoins out. Issuers also reconcile against public reserve data, such as the weekly reserve holdings on Circle's transparency page.
  • Blueprints: the euro stablecoin issuance blueprint covers an issuer's mint, burn and reserve records under MiCA Title IV. That blueprint covers the case where every token has to match a euro in a bank account. The stablecoin payments in your TMS blueprint covers a treasury that raises and reconciles stablecoin payments inside the treasury system it already uses.

FAQ

What is stablecoin reconciliation?
Stablecoin reconciliation matches every onchain stablecoin movement to its general ledger posting and to the record behind it at a bank, custodian or stablecoin provider. The movements are mints, burns, transfers and network fees, and reconciliation brings the balances on all three into agreement. An e-money token issuer also matches each mint and burn to the funds received or paid out under MiCA Article 49.
Which tools reconcile stablecoin transactions with the general ledger?

Four kinds of tool reconcile stablecoin transactions with the general ledger. The first kind is the crypto subledger: Cryptio, Bitwave, Lukka, Alloy Crypto (formerly Integral) and TRES Finance. Fireblocks agreed to acquire TRES Finance in January 2026. Crypto subledgers read chains and custody accounts and match movements. They sync journal entries to ERPs such as NetSuite, SAP, Oracle or Xero.

Custody platforms such as Fireblocks and BitGo expose transaction hashes, fees and statuses by API. Circle Mint sends a daily camt.053 statement for USDC and EURC. A firm can also build its own indexer and matching engine that posts to its core banking system. That own build is the route Protofire builds.

Does any stablecoin provider send camt.053 bank statements?
Yes. Circle Mint has documented a daily camt.053.001.13 statement since 27 April 2026. The statement covers USDC and EURC in one file. A Circle-specific supplementary data block gives the transaction hash, chain and wire reference for each entry. Among the other providers we checked on 5 November 2026, BVNK, Bridge, Fipto and Monerium document REST APIs, reports or webhooks. None of those other providers documents a camt.053 or MT940 statement for stablecoin balances. None of the crypto subledgers we read documents one either.
How do you match an onchain stablecoin transfer to a bank payment without a memo field?

On Ethereum and other EVM chains the ERC-20 Transfer event records only sender, recipient and amount, so the reference has to come from somewhere else. One usual key is a deposit address assigned to each client or invoice. Another is the client reference that a custody platform stores beside the transaction hash. A third is the reference a provider asks payers to put in the fiat leg, such as Bridge's deposit message in the SEPA reference.

Some chains have a memo. Stellar has a memo field, and Solana has a Memo program. The XRP Ledger has destination tags, which stablecoin issuers use to identify the customer to credit. Monerium maps memos and references to the ISO 20022 remittance fields of the SEPA payments it sends when its tokens are redeemed.

When should a stablecoin transfer be posted to the ledger?
A transfer should be posted once it is final on its chain. Final means the transfer can no longer be reversed, and the threshold differs by chain. For Ethereum, ethereum.org says "It takes about 15 minutes for an Ethereum block to finalize". Solana, Tron and rollups such as Base publish their own stages. Custody platforms expose finality as a status. Fireblocks moves a transaction through CONFIRMING to COMPLETED and asks clients to confirm the balance at the same or a later block height. BitGo marks a transfer "removed" if a chain reorganization drops it. A firm that posts before finality needs a reversal rule for those cases.
What does an EMT issuer have to reconcile under MiCA?

An e-money token issuer's mint and burn records have to agree with its fiat receipts, redemptions and the accounts where it keeps the funds received. The reason is that the issuer issues tokens at par on receipt of funds and redeems them at par (MiCA Article 49). The issuer keeps at least 30% of the funds received in separate accounts at credit institutions. It keeps the rest in secure, low-risk assets in the same currency (Article 54). Once a token is classified as significant, an e-money institution that issues it also comes under the reserve rules of Article 36 (Article 58(1)). Under those rules, issuance and redemption are "always matched by a corresponding increase or decrease in the reserve of assets". Under those rules, an independent audit of the reserve of assets is also due every six months (Article 36(9)).

The quarterly reporting of Article 22 applies to EMTs only when they reference a currency other than an EU member state's (Article 58(3)). A dollar token issued in the EU is an example. Even then, the reporting covers only tokens with an issue value above EUR 100 million, or tokens where the supervisor asks. The templates are in Implementing Regulation (EU) 2024/2902. They use quarter-end reference dates, and CASPs pass their data to issuers by the 21st of the following month. One further template is daily.

Does Travel Rule data have to travel on the blockchain?
No. Under the Transfer of Funds Regulation, the payer and payee information "shall not be required to be attached directly to, or be included in, the transfer of crypto-assets" (Article 14(4)). The condition is that the information is sent before or with the transfer, and no minimum amount applies. The EBA's guidelines allow the information to be sent over APIs and other channels. For transfers to or from self-hosted addresses, the EBA's guidelines accept a transfer hash or a reference number to identify a transfer individually. For reconciliation, the Travel Rule message ID is therefore one more key that links an onchain transfer to the payer and payee behind it.
How should stablecoin network fees be booked?
On most chains, a network fee posts as its own line. The reason is that the fee is paid in the chain's native token (ETH on Ethereum, SOL on Solana), separately from the stablecoin amount. So the firm needs a native-token balance on each chain it sends from. Some payment chains differ. Arc uses USDC as its gas token, and Tempo has no native token and takes fees in stablecoins. Custody platforms return the fee on each transaction. Fireblocks returns it in the feeInfo object, and BitGo returns it in feeString. Subledgers read the fee from those sources.
Build it

We index the addresses you hold on each chain and join every movement to its payment instruction, Travel Rule message and wallet owner. Once a movement is final, we post it to your core banking or ERP ledger. We also write a daily camt.053 that your existing reconciliation engine can read. Where you already run a subledger, a custody platform or Circle Mint, we connect their data to the same ledger.

Stablecoin payments booked and reconciled in your systems →

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.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.