Taurus Integration That Connects Taurus-PROTECT to Your Books and Approvals
Protofire builds the Taurus integration for banks, licensed crypto firms and issuers on Taurus-PROTECT. It books transfers in your ledger, drafts rules for your SuperAdmins and matches Taurus statements daily. We built and operated the reserve-data pipeline behind a large auditing firm's 15+ proof-of-reserve and real-time attestation deployments.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
What a Taurus integration adds to Taurus-PROTECT
Once you have chosen Taurus-PROTECT for custody, your Taurus integration has to connect it to your own books. Taurus-PROTECT's HSMs check each request against your governance rules before they sign.
A deposit that is not booked means a client who sees no funds, or a balance that finance cannot match to Taurus' statement. Taurus sends webhook calls in the order it created them, so one failing endpoint can hold back the deposit events behind it. Taurus' docs say that calls older than 24 hours "will no longer be tried" (Taurus). A scheduled read of the transaction list brings an event dropped that way into your ledger.
The set of webhook events also depends on the Taurus-PROTECT release. Taurus' public docs list five webhook types from version 3.56 (Taurus). The pages for versions 3.48 to 3.54 list three (Taurus).
Protofire builds what Taurus' own services and the Temenos connector leave to the firm. Taurus offers operating model support and API guidance (Taurus). Taurus' managed service leaves "the full hosting to Taurus" (Taurus). On Temenos, a connector published by both vendors books positions in the core (Temenos).
Protofire integrates Taurus for firms that have chosen it. For those firms, we build ledger connectors on other cores and the approval rules. We also build the payment legs and the statement matching.
How a Taurus-PROTECT deposit moves from address to MT535 match
Webhooks and a scheduled read deliver each transfer to the firm's ledger. The MT535 and MT536 statements give the daily match a second record of the same holdings.
Ledger, cash and client channels
Taurus-PROTECT and Taurus-CAPITAL
Integration layer
Statements and audit trail
What Taurus-PROTECT provides and what your firm builds
Taurus-PROTECT tags an address with a customer ID, and your firm builds the ledger behind that tag.Taurus' docs describe the customer ID as "for your own bookkeeping" (Taurus).
Keys and signing
Taurus-PROTECT provides: FIPS 140-2 Level 3 or 4 HSMs, MPC as an option, and SaaS, hybrid or on-premises deployment (docs)
Your firm builds: HSM operations and key ceremonies when the platform runs on premises
Approvals
Taurus-PROTECT provides: Governance rules on source, destination and amount, which the HSM checks
Your firm builds: Draft rules from your authority matrix, and approving service accounts in your infrastructure
Events
Taurus-PROTECT provides: Signed webhooks, sent in creation order and retried for up to 24 hours (docs)
Your firm builds: A receiver that answers each call, a scheduled read that books what the webhooks missed, and alerts on the call log
Client mapping
Taurus-PROTECT provides: Customer IDs on addresses, and one address ID per network (docs)
Your firm builds: Client positions in your ledger, keyed on the Taurus address ID and the network
Statements
Evidence
Taurus-PROTECT provides: Audit trail exports
Your firm builds: Your alerting and incident runbooks, your entries in the DORA register, and an exit plan that covers Taurus, the integration and the operator
What a Taurus integration changes for your finance and risk teams
Deposits credited once, after Taurus confirms them
Protofire builds the receiver and the scheduled read that bring deposits into your ledger. A client's deposit is credited when Taurus shows it as confirmed. The receiver filters out a repeat of the same call ID. Each posting is keyed on the transaction and its destination address, because one Taurus transaction can pay several of your addresses.
Client mapping on EVM layer-2 networks
Taurus creates the same 0x address under a separate address ID on EVM layer-2 networks, but only when the address is first created. A layer 2 that is enabled later gets no backfilled addresses (Taurus). So Protofire issues new deposit addresses and tells clients which networks each address accepts.
Governance rules drafted from your authority matrix
Your authority matrix becomes a rules file that gives the source line for each rule. One of your SuperAdmins submits the file, and the quorum approves it. The HSM then enforces the rules. Where you want automated approvals, the approving service account runs in your infrastructure. Its key is held in your HSM or secret manager, and Protofire has no access to it. Test requests run on a test tenant first.
Daily matching of MT535 and MT536 statements
Protofire builds a daily statement match that finance can sign. After your cut-off, we pull the MT535 holdings and MT536 transactions for each address and sum them per wallet. We then match the totals to client positions and to chain balances read outside Taurus. Taurus publishes no sample statement in its docs (Taurus). So identifiers, balance types and closing time are mapped to your instrument master in the first phase.
Held deposits, Bitcoin sweep fees and cash legs
A deposit that fails address scoring or the Travel Rule check goes to a held position in the ledger as soon as the flag arrives. On Bitcoin, a sweep takes its fee from the client funds that it moves, and the ledger charges that fee to you. Circle Mint minting and burning are booked on both legs. Fiat legs run on your payment rails.
Regression runs before upgrades and an owner for each alert
A firm that runs Taurus-PROTECT on premises upgrades on its own timetable, so each release gets a regression run first. Alerts cover failed webhook calls, requests stuck in a state and posting failures. If you choose, Protofire's managed onchain operations team takes these alerts under a written scope. Otherwise your staff take them.
If you're holding a volatile gas token as network fees, then accounting for it is complex. [...] when those tokens end up flowing into accounting and user experience, it creates a problem for the finance teams.
Gagan Mac, VP, Product & Engineering, Arc, Circle · The Protocol Roundtable by Protofire, Episode 4, 45:49Our record: reserve data and a bank custody blueprint
A Taurus statement of holdings is a claim, and your ledger and the chain have to confirm it.Protofire's record here is reserve-data work and a published blueprint that names Taurus.
Reserve-data pipeline for a large auditing firm
Protofire built and operated the reserve-data pipeline behind a large auditing firm's 15+ proof-of-reserve and real-time attestation deployments for asset-backed tokens. The daily Taurus match runs the same check: one system states a holding, and other systems test it. See our proof of reserve service.
Taurus in our In-App Crypto Brokerage blueprint
Our In-App Crypto Brokerage blueprint lists Taurus among the custody providers that a bank can rent. Our integrations hub lists the other custody platforms that Protofire connects.
Order of work with Protofire on Taurus-PROTECT
- Step 1
The receiver and the daily match come first
Protofire builds the receiver, the scheduled read and the daily match in the first phase. They have to work before the first client deposit. - Step 2
Governance rules next, tested before submission
Governance rules and approval keys come next. Users are taken from your identity provider. - Step 3
Payments, tokens and new chains as each product launches
Withdrawals, stablecoin legs and Taurus-CAPITAL tokens follow as each of your products goes live. - Step 4
You own the code, the rules file and the release checklist
The code, the rules file and the release checklist are yours, and your staff keep the approvals. You keep client positions in your ledger. So if you change platform, only the addresses behind those positions change.
How work with Protofire starts
Work starts with three items from you.You send the Taurus-PROTECT release and deployment model that you run, the ledger that Taurus events must reach and a redacted MT535 extract. The first written proposal maps each item to a phase.
- 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.
Taurus facts the integration relies on
- Regulatory status
- Taurus SA is a securities firm authorized by FINMA (FINMA list). Taurus (Europe) Ltd in Nicosia holds CySEC license 465/26, dated 9 March 2026 (CySEC).
- DORA status
- The ESAs named 19 critical ICT third-party providers on 18 November 2025. Taurus is not among them (list).
- Statements
- SWIFT MT535 holdings and MT536 transactions, pulled per address over the API (docs).
Checked November 2026 against Taurus' documentation and website, the FINMA and CySEC registers and the ESAs' list.
Roles of Taurus, your firm and Protofire after launch
Your SuperAdmins approve the governance rules, whether Taurus hosts the platform or you run it on premises.Under the managed service, Taurus hosts the platform, and you control what gets signed through your governance rules. On premises, you own the HSMs, the key ceremonies and the backups.
Protofire's operators get read-only roles by default. The scope of work says whether they can reach the connector's service account. Protofire takes no RequestApprover or SuperAdmin role, no signing key and no recovery role.
A Swiss institution that hands custody to a provider is still answerable for that custody. FINMA says so in its guidance of 12 January 2026 on the custody of cryptobased assets (FINMA). Under DORA, an EU firm keeps a register of information (Article 28(3)). DORA also asks for exit strategies for ICT services that support critical or important functions (Article 28(8), DORA). Your exit plan covers Taurus, the integration and the operator.
When a Taurus firm does not need Protofire
Three cases need little or no work from Protofire.
- Your core is Temenos, and the published connector covers your assets and flows. Taurus says that banks on the connector "no longer need to build such interfaces" (Taurus). So Protofire would add at most a scope check and an independent match against the chain.
- You need an operating model, training and API advice. Taurus sells those itself.
- The open work is HSM installation and the key ceremony, and both belong with your security team and your HSM vendor.
Protofire holds no license of its own. We do not take on licensing or the holding of client assets, and we give no legal opinions on DORA, MiCA or FINMA rules.
FAQ
What is a Taurus integration?
Who can build a Taurus integration for a bank or a licensed crypto firm?
Does Taurus connect to core banking systems other than Temenos?
What changes if we run an older Taurus-PROTECT release?
Is Taurus regulated, and does that change our license?
Can we mint and redeem USDC from Taurus-PROTECT?
Where does Protofire appear in our DORA register of information?
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.
