Skip to content

Temenos Integration for Booking Custody and Stablecoin Movements

Protofire builds the adapter that posts custody and stablecoin movements into Temenos, with cash legs and a daily match. The work is for banks, wealth managers and payment or e-money firms. We built and operated the reserve-data pipeline behind 15+ proof-of-reserve and real-time attestation deployments for a large auditing firm.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. When a deposit posts
  3. Temenos facts
  4. What you get
  5. Why Protofire
  6. How it runs
  7. How work starts
  8. Not the right fit
  9. Related guides and services
  10. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

How a platform deposit becomes a Temenos booking

A Temenos integration decides how your core books a deposit that your custody or stablecoin platform reports. You have chosen that platform for client tokens, and your core is Temenos.

Temenos already has objects for digital assets. Its Transact APIs list crypto assets among security instruments and keep a blockchain id for each securities customer (Temenos). But the platform's events do not fill in the booking. The booking still needs the instrument for each token, the client behind each deposit address and the booking date of each posting.

Taurus has its own link to Temenos, which our Taurus integration page covers. Other platforms connect to Temenos through an adapter.

How platform events become Temenos security transfers

A deposit starts at the platform and ends as an inbound security transfer in a client portfolio. Cash legs are sent through Temenos Payments.

Temenos

Temenos core banking

Temenos holds instruments, securities customers, portfolios, accounts and the general ledger, and runs the nightly close of business.

Temenos Payments

Temenos Payments sends the fiat legs of ramps, payouts and treasury moves as ISO 20022 messages.
Custody and stablecoin platforms

Platforms

Taurus connects through its own link, and other platforms connect through the adapter.
Protofire builds

Posting adapter

The adapter reads platform and Temenos events, maps each address to a customer and portfolio, and posts each transfer once.

Statements and daily match

Holdings statements use platform and chain data, and a three-way match queues each break by owner.

Three Temenos behaviors that decide when a deposit posts

Chains keep settling while Temenos closes the day.Temenos ends each day with a close of business process, which runs through Transact's system services (Temenos). So a deposit that arrives during the run needs a booking date that the core accepts.

In Temenos, a credit waits to be counted in the working balance until it is "fully authorised" (Temenos). And a call to Transact that gets no reply ends in error TGVCP-001. Temenos describes that error as "Unable to get the response from Transact" (Temenos).

After a lost reply, nobody knows whether the transfer exists until something checks. If the setup is left as it is, finance can end up booking deposits by hand. A retry after a lost reply can also duplicate a transfer that already posted.

Temenos facts we build against

Digital-asset objects
The Transact APIs cover security instruments including crypto assets, securities customers with a blockchain id, inbound and outbound security transfers, positions and book cost (Temenos).
Interfaces
Temenos offers REST APIs and events. By Temenos' count, release R24 has 3000+ APIs and 250+ events, against "Few APIs" before R19 (Temenos). OFS, the Transact message service, "allows the system to process transaction and query requests" (Temenos).
Deployment
Temenos SaaS is "Delivered on Microsoft Azure and Amazon Web Services (AWS)" with an annual update service (Temenos).
Payments messages
Temenos Payment Hub is "Built to support ISO 20022 standards" (fact sheet).
Digital-asset providers
Temenos' Digital Assets & Crypto category lists Taurus. Temenos has solution-provider pages for Fireblocks and Dfns, but none for Ripple Custody, BitGo or Circle.

Checked November 2026 against Temenos' documentation, developer portal and releases. Protofire integrates digital-asset platforms with Temenos for firms that run it.

What your back office gets from a Temenos integration

Each deposit posts once, to the right client

A confirmed deposit becomes an inbound security transfer in the right client portfolio. If the same platform event arrives again, the adapter posts nothing. Protofire builds the adapter that posts. We also build the address register, which ties each deposit address to a securities customer and a portfolio.

Withdrawals block the client's position until the chain settles

The client's position is blocked while a transfer is in flight. Protofire blocks the position when the order is accepted and posts the outbound transfer at final status. If the chain transfer fails, we release the block.

Weekend deposits take the next Temenos business date

A Saturday deposit takes the next Temenos business date instead of being posted in the middle of the close. Protofire converts block time to the booking center's date and records that date on the transfer. Your Temenos team confirms that Transact accepts the date.

Cash legs and statements in ISO 20022 messages

Ramps, payouts and treasury moves are sent as ISO 20022 messages through your payment hub. Your securities back office gets holdings and movement statements. Protofire builds these statements from platform and chain data rather than from the adapter's own postings.

Each break in the daily match has an owner

Each morning, the adapter compares three records for each token: the Temenos positions, the platform's balances and the chain at the cut-off block. MiCA asks a custodian to keep client and firm crypto-assets apart "on the distributed ledger" itself (MiCA Article 75(7)). So the match reads the chain too. A difference that remains after the named fee lines goes to a break queue, aged by owner.

Regression tests before each Temenos update

Protofire runs postings, statements and the match before each Temenos update reaches production. We run them again before each platform release. Temenos SaaS ships an annual update (Temenos). Under a written scope, we also watch event consumers, posting errors and breaks against runbooks that your teams approved.

From platform event to Temenos posting, step by step

  1. Step 1

    Confirming the Temenos release and deployment

    The release and deployment are confirmed before a posting rule is written. The full design needs a Temenos release with REST APIs and events, such as R24 or Temenos SaaS. On a release before R19, the adapter posts through OFS, and its rules are reused on the REST APIs after an upgrade. On Temenos SaaS, Protofire checks which event topics and extension fields your subscription lets the adapter use.
  2. Step 2

    Each event is stored once, and each posting has its own key

    A message can arrive again after a consumer fails, so the adapter skips event ids that it has already processed. Temenos' sample event payloads include an id and a sequenceno (Temenos). Postings use a separate key, made of the platform transaction ID, the receiving address and the output or log index, since one chain transaction can pay several client addresses.
  3. Step 3

    The adapter matches the client before it posts

    The adapter runs the screening you set up. Then it maps the deposit address to a securities customer, a portfolio and a company. Transact rejects a posting for the wrong company with the error "Invalid company specified" (Temenos). So a firm with two booking centers ties each omnibus wallet to one company. A posting restriction can also stop a posting, and the runbook sends those postings to the account officer.
  4. Step 4

    Postings wait for the authorization that finance sets

    Finance decides which postings a service user may authorize. Your bank holds that service user and its credentials. A Temenos narrative line holds 34 characters (Temenos), but an EVM transaction hash has 66. So the hash, the network and the token identifier go into extension fields.
  5. Step 5

    The adapter checks Temenos before a retry

    After a lost reply, the adapter first reads Temenos back by its own reference. A second attempt that returns TGVCP-005, "Transfer Already Authorised", counts as done (Temenos).
  6. Step 6

    Your Temenos team keeps control of the core

    Your Temenos team, or the firm that delivers your project, sets up the core from Protofire's specifications. That setup covers products, instruments, customers, close of business and upgrades. The platform holds the keys under its contract with you. Protofire owns the adapter, statements and match until your team takes them over. We read Temenos without write rights, unless your signed scope adds them.

How work with Protofire starts

You send us the platform you chose, your Temenos release and deployment, and the flows you need.An engineer works through these inputs first. The written proposal then maps each flow to a deliverable. 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.

Four cases where Protofire's Temenos adapter does not fit

  • You run Taurus, and its link to Temenos covers your assets and networks. Temenos calls that link a "ready-made integration" (Temenos). Your Temenos team configures the link. Protofire adds statements, cash legs or a chain match where the link leaves them open.
  • The work is the Temenos core itself: products, Arrangement Architecture or close of business. The work can also be an upgrade or a migration. Temenos sells those services (Temenos).
  • Your bank runs a release before R19 and upgrades during the project. In that case the build should target the new release, or the OFS layer gets built and then retired.
  • Your volume is at pilot level. Then a daily statement file from the platform can be booked by hand each morning.

Protofire holds no license, client assets or keys. We do not take on accounting or legal opinions or changes to your Temenos configuration. We take no signing, approval, administrator, key-holder or recovery role on a platform.

An asset cannot realise its full value unless the cash leg can settle with comparable certainty. Nor will a new platform scale if it cannot connect to existing infrastructure, liquidity and custody arrangements.
Sasha Mills, Executive Director, Financial Market Infrastructure, Bank of England · Speech at the Hogan Lovells and Global Digital Finance Digital Assets Summit, 1 October 2026

FAQ

What is a Temenos integration for digital assets?
A Temenos integration for digital assets connects a custody, stablecoin or tokenization platform to Temenos core banking. Deposits and withdrawals post as security transfers in client portfolios or as account entries. Cash legs post through Temenos Payments. Protofire builds the adapter, the statements and the daily match, and your Temenos team keeps the configuration.
Who can build a Temenos integration for a bank or an e-money institution?
Temenos and Protofire build different parts of a Temenos integration. Temenos sells implementation, advisory and migration services of its own (Temenos). On the digital-asset side, Protofire builds the posting adapter and the cash legs. Protofire also builds the statements and the daily match, from specifications that your Temenos team applies.
Can Fireblocks, BitGo, Ripple Custody or Circle connect to Temenos?
Yes, these platforms can connect to Temenos through an adapter on the Transact APIs and events. Fireblocks names "Temenos Infinity" as its integration (Fireblocks), with no published booking into Temenos core banking. Protofire's Fireblocks integration page covers the Fireblocks side. Dfns joined Temenos Exchange in September 2024. A bank can run the Taurus link and a second platform side by side. Our integrations hub lists the other platforms.
How are stablecoins and e-money tokens booked in Temenos?
Stablecoins and e-money tokens are booked in Temenos under one of two models, and finance picks the model. The adapter then books the model that finance chose. In the first model, the token is a security instrument with positions in portfolios, which the Transact APIs allow for crypto assets. In the second model, the token is held on an account in a currency code that your Temenos team sets up. This applies if your configuration supports that model. Finance and the auditor decide the treatment.
Do a bank, a private bank and an e-money institution book differently?
Yes, each of the three books client tokens differently. A bank books client crypto as positions in securities portfolios. A deposit token that the bank issues is booked as a deposit, which our tokenized deposits service covers. A private bank adds book cost. A token transferred in from another custodian arrives without the client's purchase cost, so that cost goes in through Transact's securities book cost adjustment (Temenos). An e-money institution keeps customer balances as accounts in Arrangement Architecture. Its safeguarded funds may be held in a separate credit-institution account. In that case, the cash legs to that account are sent as pain.001 instructions. That bank's camt.053 and camt.054 reports come back for the match.
Which ISO 20022 messages does a Temenos back office get for digital assets?
For crypto booked as securities, a Temenos back office gets two messages: semt.002 for holdings and semt.017 for movements. A camt.053 covers cash legs and a stablecoin booked as a cash account. The transaction hash is sent in supplementary data, because reference fields stop at 35 characters.
Where does Protofire appear in a Temenos bank's DORA register?
Protofire appears in the register of information through its ICT service contract. DORA asks banks, payment institutions and e-money institutions to list each ICT service contract in that register (Articles 2 and 28, DORA). In the template of Regulation 2024/2956, building the adapter is ICT development (S02). Operating the adapter adds ICT operation management (S14). Your risk and legal teams decide what is filed. Temenos is not on the ESAs' list of 19 critical ICT providers of 18 November 2025. The EU entities of Microsoft and AWS are on that list, and Temenos SaaS is delivered on those two clouds. A Temenos SaaS client checks which of these providers is in its own chain. Our DORA third-party risk guide explains the classes.

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.