Skip to content

Kyriba Integration for Treasury Teams Adding a Stablecoin Rail

Treasury teams on Kyriba need payment and statement services for a stablecoin rail without a Kyriba app. Protofire builds both on your host, plus wallet payees, screening and ERP posting. Treasury keeps releasing payments in Kyriba. We have built subgraphs since 2019 and received a Graph Foundation grant in 2021.

Luis Medeiros

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

On this page
  1. Overview
  2. Kyriba connectors
  3. Kyriba 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

Kyriba integration for a rail with no Kyriba app

A Kyriba integration is the code that sends a payment from Kyriba to a stablecoin rail and brings a balance back. Kyriba leaves that code to the firm. For example, your treasury team runs on Kyriba, and a stablecoin rail with no Kyriba app has just been signed.

Kyriba defines two interfaces and expects the rail or the firm to host them. The Payment Initiation Service SPI, released in April 2024, receives payments started in Kyriba and returns their statuses. The Reporting Service SPI, released on 14 August 2026, answers Kyriba's requests for balance, intraday and end-of-day statement reports (Kyriba Developer Portal). Kyriba's overviews open both SPIs to "partners and customers".

Where no Marketplace connector exists, a rail without the two SPI services has no way into Kyriba's cash position. Kyriba's Bank Statement Balances API "will only present the bank balances that have passed checks" (Kyriba Developer Portal). Kyriba's cash balances count the transactions that its Cash Reconciliation process has matched (Kyriba Developer Portal). So when a rail statement is missing a day, that money is left out of the cash position.

Payment and reporting services between Kyriba and a stablecoin rail

A payment released in Kyriba reaches the rail through the payment service. Balances and statements come back through the reporting service, and Kyriba checks them first.

The company

ERP and vendor master

The ERP holds invoices, supplier records with wallet addresses and the ledger that receives postings.

Treasury set-up in Kyriba

The company sets the payment workflows, release limits, Dual Admin approvers and the detection method.
Kyriba

Payment factory

Kyriba validates payments, runs the approval workflow and alerts, and routes payments to banks and providers.

Statements and cash positions

Kyriba checks statements, runs Cash Reconciliation and builds the daily cash position.
The rail or custodian

Rail or custodian

The rail or custodian executes transfers, holds balances and keeps the records that statements come from.
Protofire builds

Payment service

The payment service takes payments from Kyriba, calls the rail and returns each status.

Reporting service

The reporting service answers report requests from rail records and chain reads.

Payee, screening and posting links

These links write wallet payees, connect the screening engine and post to the ERP.

What each Kyriba digital-asset connector leaves to the firm

Kyriba's Marketplace lists connectors for Fipto, Circle and Copper (Kyriba Developer Portal).Where no connector exists, a rail reaches Kyriba through the two SPIs.

Fipto Stablecoin Banking Connector

What its Kyriba page or provider says it covers: Fiat or stablecoin payments started "from Kyriba using existing approval workflows", plus balances, transactions and statuses

What is left to the firm: KYB with Fipto, and activation "via Kyriba or your integrator", per Fipto. Also supplier wallet data and ERP posting.

Circle Stablecoin API Connector

What its Kyriba page or provider says it covers: USDC balances and transaction data from Circle Accounts. Kyriba's Circle page places execution in a future phase, as read on 13 November 2026.

What is left to the firm: Payments from the Circle Account and their posting, for as long as that page places execution in a future phase

Copper Integration

What its Kyriba page or provider says it covers: Consolidation of liquidity across fiat currencies, cryptocurrencies and money market funds

What is left to the firm: Transfers out of Copper, approved in Copper, and a price source and valuation time for each asset

J.P. Morgan Kinexys

What its Kyriba page or provider says it covers: Blockchain Deposit Accounts operated through Kyriba's J.P. Morgan connector, per J.P. Morgan in April 2024

What is left to the firm: Opening the deposit accounts with J.P. Morgan

A rail or custodian with no Kyriba app

What its Kyriba page or provider says it covers: The Payment Initiation Service SPI and Reporting Service SPI

What is left to the firm: Both SPI services, wallet payees, screening and ERP posting

Kyriba interfaces and controls we build against

Developer Portal
43 APIs listed on 11 November 2026, each with a public overview and changelog. The full API Catalog, with schemas and status values, needs a free Kyriba developer account (Kyriba).
API access
OAuth client credentials. Customers generate them through Self Service in the Kyriba application.
Payment Initiation Service SPI
Version 1.0.0, released 4 April 2024. It submits payments to banks or payment service providers and receives their status.
Reporting Service SPI
Version 1.0.0, released 14 August 2026. It covers balance, intraday and end-of-day statement reports, from synchronous or asynchronous bank APIs.
Controls
Fraud Detection SPI and API for an external screening engine. Dual Admin for third parties since May 2025. Audit Trails with requester and approver.
Stablecoin live use
Kyriba and Fipto announced Ledger's and Mantu's live stablecoin payment flows inside Kyriba on 8 June 2026 (Kyriba).

Checked November 2026 against Kyriba's Developer Portal and release, Fipto and J.P. Morgan. Protofire integrates Kyriba for firms that have chosen it.

What a Kyriba integration gives your treasury team

Treasury releases rail payments in Kyriba

Treasury releases a rail payment under its usual workflow and sees the rail's latest status beside it. Protofire builds the payment service on your host. The service accepts calls that it authenticates as coming from Kyriba. The authentication method is confirmed against the full specification during design. A repeated submission gets back the stored status. The rail is searched before a resend, and a poller closes late confirmations.

Rail and custodian balances that pass Kyriba's checks

The balance in your cash position is one that Kyriba has accepted. Protofire builds the reporting service that answers Kyriba's report requests. Each statement comes from the rail's records. For coins at your own addresses, the statement also uses a chain read at the last block before the rail's cut-off. The statement names that block, the cut-off and the cut-off's time zone. Each day opens on the balance at which the day before closed. A report that misses its cut-off is held, and an alert goes out. For an omnibus account, the custodian's records are the source.

A new supplier wallet needs a second Kyriba approver

Under Dual Admin, set-up changes "are only applied to a business process when they are approved by a second user or user group" (Kyriba Developer Portal). Third parties is the entity type that Dual Admin covers today. Protofire builds a sync that writes wallet payees from your ERP vendor master into Kyriba Third Parties as changes waiting for the second approval. Kyriba's Audit Trails keep the requester and the approver. The public overview of Third Parties describes bank accounts and stops there. So where the record stores a wallet address is settled against the full specification during design. Before each payment run, the sync compares Kyriba's payee list with the rail's payee list. Under a rule that you sign, the payment service holds a payment whose address differs.

Screening results next to the payment they concern

Where you set the detection method "External detection engine" in Fraud & Compliance, Kyriba pushes each transfer to your screening engine. Kyriba sends each transfer through the Fraud Detection SPI, and results can arrive later through the Fraud Detection API. Protofire builds the connector to the engine you pick. Your Kyriba administrator switches the external engine on. Protofire's compliance integration work covers the engine side.

Open payments polled and ERP imports checked before a rerun

Kyriba's Batch Status Changed and Routing Status Changed webhooks tell your tools about batches and routed files. The public overviews describe no retry rule for these webhooks. So Protofire polls the Transfers API for each payment that has no final status by an agreed hour. ERP postings go through Data API uploads and process template runs. The task of each run ends as "Complete", "Warning", "Error" or "Cancelled". Each upload includes a batch reference. Before a rerun, that reference is checked in the ERP and the task status is read.

Our record: subgraphs and a Graph Foundation grant

Protofire's record is turning contract events into records that other services query by block.Indexing work applies to a Kyriba integration because a statement for Kyriba's continuity check needs chain state read at a stated block.

Subgraphs since 2019. Protofire has built subgraphs for The Graph since 2019. Our subgraph case study lists open-source subgraphs for protocols including Maker, Curve and UMA. Protofire's subgraph development service has its own page.

Graph Foundation grant, 2021. The Graph Foundation's second grant wave in July 2021 funded Protofire for subgraph development and support (The Graph Foundation). The Foundation's announcement lists the grant as "Subgraph Development & Support".

Kyriba project steps, from one traced payment to handover

  1. Step 1

    Tracing one payment through Kyriba

    You send the Kyriba modules you run, your rail or custodian and one payment to trace, from release to a balance Kyriba accepts. Protofire's first written proposal maps that trace to the Kyriba services described on this page.
  2. Step 2

    Where the services are built and tested

    Kyriba's API Playground uses testing credentials generated after signing in to a free Developer Portal account. Your own environment uses credentials from Self Service. The token and base URLs for those credentials depend on the platform and the environment.
  3. Step 3

    Payee sync, screening link and ERP posting come next

    Next come the wallet payee sync, the screening link and the ERP posting. Your Kyriba administrator switches on the external screening engine.
  4. Step 4

    You own the service code and its tests

    The service code and its tests are yours, on your host. A rail that wants a Marketplace listing takes that route itself. For that route, the build supplies the architecture and data-flow documents and the test logs that Kyriba's certification stages ask for.

Starting a Kyriba project with Protofire

The services run on your host.The Kyriba jobs use client credentials that your administrators generate in Self Service. The payment service uses a rail API credential that your staff issue. All of these credentials are kept in your vault. The payment service sends payments that your staff released in Kyriba. Under a written scope, Protofire operates only the parts that read data, such as reporting and the status checks on open payments. 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.

Five cases where Kyriba connectors or your own team are enough

  • Your rail is Fipto. Fipto's connector is in the Marketplace and is switched on in Sandbox and/or Production "via Kyriba or your integrator" (Fipto). What remains is payee data and ERP posting.
  • You need only USDC balances from a Circle Account. Kyriba's Circle connector brings those balances into the cash position.
  • The work connects an ERP to Kyriba and involves no digital assets. Kyriba's Marketplace lists packaged integrations for SAP, Oracle, NetSuite, Dynamics 365 and IFS Cloud.
  • You use J.P. Morgan's Kinexys deposit accounts. Those accounts run through Kyriba's J.P. Morgan connector.
  • You have not chosen a rail, or you are weighing pay-through against a held balance. Start with our page on stablecoin payments from a treasury system.

Your Kyriba team sets up the Kyriba modules. Kyriba keeps its approvals, checks and platform, and your staff release each payment. Protofire holds no financial or crypto-asset license. Protofire gives no accounting or legal opinion on how your firm treats a stablecoin balance.

FAQ

What is a Kyriba integration for stablecoins?
A Kyriba integration for stablecoins connects a rail or custodian to Kyriba through two SPIs. The Payment Initiation Service SPI sends payments out to the rail. The Reporting Service SPI brings balances and statements back into Kyriba. Protofire builds both services, plus wallet payees, screening results and ERP imports. The firm's treasury team keeps releasing payments in Kyriba.
Who can build a Kyriba integration for a stablecoin rail or a custodian?
Kyriba publishes the interfaces, and the firm or its rail hosts the services behind them. Protofire builds the payment service and the reporting service on the firm's host. Protofire also builds the wallet payee sync, the screening link and ERP posting. Protofire's record is chain-data indexing, with subgraphs for The Graph since 2019.
Can treasury pay from a Circle Account through Kyriba?
Kyriba's Circle page places workflow and transaction execution in a future phase of the connector (Kyriba, read on 13 November 2026). So a treasury team should check that page before planning payments from a Circle Account. The Circle Stablecoin API Connector brings USDC balances and transaction data into Kyriba's cash positions.
Do stablecoin payments pass Kyriba's approvals and fraud screening?
Yes, when the payments leave through Kyriba. Fipto's Marketplace page says every flow remains within Kyriba's validation rules, approval workflows and fraud controls. A rail with its own payment SPI service receives payments that Kyriba submits after the same workflow. Where the firm runs an external screening engine on the Fraud Detection SPI, that engine checks the payments first.
Does our rail need a Marketplace listing to connect to Kyriba?
No. Kyriba's overview opens the payment SPI to "partners and customers", so a company can run its own connector for its own Kyriba environment. A Marketplace listing serves a rail or custodian that wants other Kyriba clients to switch its connector on. Before listing, the provider passes Kyriba's three sequential certification stages: workflow and artifacts, security process, and go live (Kyriba Developer Portal). The listing and the certification remain with the provider.

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.