Bridge Integration for Payment Apps, Wallets and EU E-Money Firms
Bridge leaves onboarding, booking and recalls to payment apps, wallets and EU e-money firms. Protofire builds that side. Customers pass Bridge's terms and KYC, each transfer is booked once, and staff decide the return of each recall. We built and operated the reserve-data pipeline behind 15+ proof-of-reserve 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 your Bridge integration has to handle
Your Bridge integration has to take each customer through Bridge's terms, because Bridge needs that customer as its own customer too. You have chosen Bridge, Stripe's stablecoin API, to move money between bank rails and stablecoins, and this step starts when your first customer signs up. Bridge's docs say customers "need to agree to Bridge's terms of services (ToS) before we can process KYC / B information" (Bridge).
Bridge then approves each customer rail by rail. A transfer on a rail without that approval fails with an error such as missing_required_endorsements (Bridge). Approval for dollars does not extend to euros. So payments stall when a EUR account appears in the app before the sepa endorsement arrives.
Once money starts to move, Bridge reports each movement in its own terms. A bank can recall a deposit that you already credited. Bridge's docs say "Webhooks are currently not supported for funds requests" (Bridge). Unless you poll, Bridge sends you no event about the recall.
Bridge's docs also say the hash at the payment_submitted state "may be preliminary" (Bridge). So a ledger that credits at that state posts on a hash that can change.
A stablecoin payment through Bridge, from customer onboarding to your ledger
A customer accepts Bridge's terms and passes Bridge's KYC. Bridge converts and delivers the money. Bridge reports each state in a signed webhook, which your ledger books.
Customer app and product terms
Customer sub-ledgers
KYC records and cases
Onboarding service
Bridge connector
Event and posting service
Bridge account
Bank rails and chains
What Bridge handles and what is left to your firm
Bridge reports where each customer, payment and recall stands, but your systems do the booking and handle recalls.
Customers
Bridge's side: Bridge holds each customer's terms acceptance as a signed_agreement_id. It runs KYC or KYB and grants endorsements per rail (endorsements).
Left with your firm: Your firm sends each customer through the terms and KYC links, reads each endorsement's requirements and keeps its own product terms in line.
Events
Bridge's side: Bridge signs each webhook with a key per endpoint and retries for up to two days (webhooks).
Left with your firm: Your firm checks signatures, guards against stale events and drops duplicates by event_id. It keeps its endpoint reachable.
Booking
Bridge's side: Bridge reports states, amounts and fees (states).
Left with your firm: Your firm sets posting rules per state, books amounts in whole cents and records a receivable for developer fees.
Recalls and returns
Bridge's side: Bridge tries to return a recalled deposit itself when the funds request arrives before the money movement completes. After that, Bridge offers a return API (funds requests).
Left with your firm: Your firm polls for recalls, links each one to its deposit_id and sends the returns that your staff decide.
Payout name
Bridge's side: Bridge sends each payout under the name set for its rail. SEPA and Faster Payments use the customer's name. USD wires use the developer's name unless customer-named wires, a premium product, are enabled (named payouts).
Left with your firm: Your firm chooses the name where the rail allows a choice and tells payees what to expect.
What you get from a Bridge integration with Protofire
Customers see a payment option after Bridge clears them
The euro account appears in the app only after the sepa endorsement has arrived. Protofire builds customer creation by API or hosted KYC link. Our onboarding service stores a signed_agreement_id per customer and watches each endorsement's requirements. It also drafts replies to Bridge's requests for information from your case records, and your staff send them.
Each payment is credited once, on the right hash
A repeated webhook posts nothing, and a retried call does not become a second transfer. Protofire builds the event receiver and the postings. A payment_submitted event holds the amount in transit. A payment_processed event credits the customer where you book the balance. Returned, refunded and refund_failed each post as their own entry. When a call times out, Bridge returns the original response to the same Idempotency-Key within 24 hours (Bridge). After that, the connector finds the transfer by your client_reference_id.
Payments in transit reported at your daily close
A payment that is still in transit at your close is reported as open, with its age. The posting rule records the event time that Bridge sends and your local posting date as two fields.
Recalls found while a return is still possible
Your staff see a recall as a case. Protofire builds a poller that runs on a schedule you set. We link each recall to its deposit and open a case whenever Bridge's fraud flag is true. A return goes out on a decision that your staff record in the case, and a Bridge wallet that you control funds the return. By then the customer may have spent the USDC, so the rule on who bears that loss is written before launch.
Payout names and Travel Rule data
Payees see the name that Bridge sends for each rail. Where the rail allows a choice, they see the name you chose. Your firm decides which transfers need Travel Rule data. Protofire builds the collection and the submission of that data, and our Travel Rule guide for the EU sets out the EU rules.
Your own coin checked against Bridge's published reserve figures
If you issue a coin through Bridge, your treasury sees supply and reserves on its own schedule. Protofire builds a monitor on Bridge's public transparency endpoint (Bridge). The monitor stores each reading with Bridge's last_updated time and flags a reading older than your threshold. The reserve split is set by API from decisions that your treasury records.
Bridge ownership, licenses and supported coins
- Owner
- Stripe completed its acquisition of Bridge on 4 February 2025 (Stripe).
- United States
- Bridge's US licenses page lists the state money transmitter licenses of Bridge Building Inc. (NMLS ID 2450917). Bridge's docs exclude customers based in New York and limit Texas to first-party orchestration without custody (Bridge).
- European Economic Area
- The CSSF has authorized Bridge Building S.A., Luxembourg, as a crypto-asset service provider (N00000012) and an electronic money institution (W00000024). Both were granted on 29 June 2026, per Bridge's non-US licenses page.
- Coins by region
- In November 2026, Bridge lists only USDC and EURC for EEA users. For other regions, the list adds coins such as USDT and PYUSD (routes).
Checked November 2026 against Bridge's API documentation and legal pages and Stripe's release. Protofire integrates Bridge for firms that have chosen it.
Our record: reserve data for asset-backed tokens
A Bridge build turns Bridge's events into postings, so each posting depends on a correct reading of the data behind it.
Reserve-data pipeline for asset-backed tokens
For a large auditing firm, Protofire built and operated the reserve-data pipeline behind 15+ proof-of-reserve and real-time attestation deployments for asset-backed tokens.If you issue a coin through Bridge, the monitor that Protofire builds on Bridge's transparency endpoint reads reserve figures against your records. Our proof of reserve page describes the service.
How a Bridge project with Protofire runs
- Step 1
Review of your Bridge setup before the call
Before the call, an engineer reads your Bridge setup. A written proposal follows, with the findings and the first step that Protofire recommends. - Step 2
First phase: customer onboarding and booking
Protofire builds the onboarding service, the Bridge connector and the posting rules in the first phase. - Step 3
Recalls, returns and reserve checks as each product launches
The recall poller, the return workflow and the monitor for your own coin come as each of your products goes live. - Step 4
Ownership, keys and operation after launch
The code, configuration and runbooks are yours. The services run in your environment under scoped Bridge API keys that your staff create and keep in your vault. Each transfer, return or reserve split that the services send executes a decision your staff recorded or a rule your firm signed. Your team runs the services, or Protofire operates them under a written scope. A service that Protofire operates holds only read scopes, such as transfer:read and funds_request:read (scopes). The written scope can also include a watch on Bridge's changelog.
How work with Protofire starts
You send your enabled Bridge products, your customer regions and a sandbox webhook log.Protofire's first proposal maps each endorsement, transfer state and event to an onboarding step or a posting rule. 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 Bridge alone, or another provider, is enough
A Bridge integration with Protofire is not the right fit in four cases.
- You take payments on Stripe and need only stablecoin payouts or acceptance. In November 2026, Stripe's Connect stablecoin payouts were a private preview for US platforms that pay individuals and sole proprietors (Stripe). Configuring Stripe may be enough.
- Your volume is still a few payments a month. Booking those payments by hand works until there are more entries than finance can check each day.
- Your customers are based in New York, need custody in Texas, or are EEA users who need a coin other than USDC or EURC. Bridge's docs list those limits, and no integration changes them.
- You have not picked a provider yet, or you want euro IBANs that mint tokens straight to a wallet. Our payout rails comparison sets Bridge beside BVNK, zerohash and others. Our wallet-linked IBAN page covers the wallet model.
Protofire holds no financial or crypto-asset license. Your firm applies for Bridge's own approvals itself, such as the account and customer-named payouts. Your staff decide each return. Your counsel decides how your own terms fit alongside Bridge's.
FAQ
What is a Bridge integration?
Who can build a Bridge integration for a payment app or an EU e-money institution?
Which Bridge entity do our customers sign with?
What happens when a bank recalls a deposit we already credited?
Where does Protofire appear in an EU firm's DORA register?
Who mints, burns and holds reserves when a firm issues its own coin through Bridge?
Can EEA customers use USDT or PYUSD on Bridge?
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.
