Paxos Integration for Firms That Mint and Redeem USDG or PYUSD
Protofire builds the firm's own side of Paxos for payment platforms, banks and EU CASPs minting USDG or PYUSD. That side covers wire memo IDs, approvals on API calls, Travel Rule data and a daily CSV match. Protofire engineers helped build the Gnosis Safe web app from 2019 to 2021.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Three jobs Paxos leaves to your own systems
Once you have chosen Paxos to mint and redeem USDG or PYUSD, your Paxos integration has three jobs that Paxos leaves to your side. Paxos mints, redeems and holds the reserves. Your side decides who approves an API call and how finance proves each day's totals.
For example, a client's wire can leave your bank without its memo ID. Your Paxos integration then cannot say where the money went.
Paxos sends such a wire back. Its funding guide says "Deposits with missing or incorrect information will be returned" (Paxos).
Paxos Dashboard approvals apply only in the Dashboard. The Paxos approvals guide says "API-submitted actions and transactions are not affected" (Paxos).
A Paxos rule in force from 30 November 2026 covers saved addresses that lack Travel Rule data. Paxos rejects an above-threshold transfer to such an address with a 403 error, or holds the transfer until the data is added (Paxos).
Left as it is, this setup leaves three problems. Returned wires have to be found by hand, and no second person sees an API mint. Payouts also stop at an address that nobody completed. Our stablecoin treasury payments page covers the treasury product a firm runs on top of an issuer.
Who owns each part of a Paxos integration
A mint starts as a USD wire with a Paxos memo ID and ends as one booking, matched against Paxos's daily CSV.
Payment hub and treasury
Ledger and client records
Issuing entity and Profiles
Orchestrations, events and reports
Event and booking service
Approvals and address book
Report match and MiCA feed
Paxos issuers, API access and events
- US issuer
- Paxos Trust Company, National Association, is a national trust bank chartered by the OCC (Charter No. 25379). It has held that charter since 12 December 2025, when it converted its former New York limited-purpose charter (licenses). It manages USDP and PYUSD (USD stablecoin terms).
- USDG issuers
- USDG is issued jointly by Paxos Digital Singapore Pte. Ltd. and Paxos Issuance Europe Oy. Paxos Digital Singapore is licensed under Singapore's Payment Services Act 2019. Paxos Issuance Europe is an authorized e-money institution supervised by Finland's FIN-FSA (licenses, USDG white paper).
- API access
- The API is REST v2, with OAuth2 client credentials and separate read and write scopes per resource (Paxos).
Checked November 2026 against Paxos's developer documentation, licenses page, USD stablecoin terms and USDG white paper.
What Protofire builds for a Paxos integration
Per-client rules and memo IDs for funding wires
Each funding wire reaches the rule built for its client, and a returned wire is booked back to its source. In Paxos orchestrations, a rule turns a USD wire with a memo ID into tokens at a registered address. Protofire builds the per-client rules and puts the memo ID in each wire template. USD wires do not run at weekends or on US banking holidays (Paxos), so the transit account handles them over those days. Protofire also moves your calls off retired Paxos endpoints.
One booking for each mint and redemption
Paxos sends each event at least once, so a repeated event must not credit a client twice. Protofire builds a consumer that reads each event by ID and drops repeats. The consumer books against the orchestration ID and the orchestration's state. A repeat books nothing. A job compares List Events with the stored events inside Paxos's retry window and books what the webhook endpoint missed.
A second approver on API calls
Protofire builds a maker-checker step in your own systems for API calls. The step runs before a mint, a redemption or a withdrawal, with value tiers from your authority matrix. Where Paxos activates JWS signing, the signing key is stored in your HSM or key service. The approval service uses that key, and Paxos rejects unsigned calls (Paxos).
Travel Rule data on each saved address
Each saved address stores the Travel Rule data that Paxos checks. The US threshold is $3,000 (31 CFR 1010.410(f)), and Paxos's guide sets $30 for its sandbox (Paxos). An orchestration that the rule holds waits with the status detail travel_rule_info_required. Paxos added that status detail on 28 October 2026 (Paxos). Protofire collects beneficiary and VASP fields when an address is saved. We also build a backfill for older addresses, because an incomplete address blocks the above-threshold payouts that use it.
A daily CSV match that finance can sign
Paxos produces its reports once a day, at the UTC hour fixed when reporting is activated (Paxos). Protofire loads both CSVs at that hour and matches lines on UniqueTxID with Direction. We group the legs of one flow by OrchestrationID. Open lines are listed each morning with their age and Profile.
USDG holdings reporting for EU CASPs
Protofire syncs the list of wallets that hold client USDG to the Paxos platform whenever a wallet is added, rotated or retired. The quarterly templates are prepared in EUR at the ECB spot rate, and your staff review and send them.
How the Paxos issuing entity changes the build
The Paxos entity behind a token changes the build in three places: redemption, Travel Rule coverage and MiCA reporting.
For USDG redemption, EEA residents redeem with the Finnish entity, and other holders redeem with the Singapore entity (USDG white paper). Paxos also "reserves the right to issue USDG to customers, or redeem USDG from customers, through either Paxos Digital or PIE when permissible" (terms, 2.2.3).
Travel Rule coverage also differs by entity. As read in November 2026, Paxos's Travel Rule guide covers end users served under Paxos Trust Company, N.A. The guide lists the Singapore and EU guides as coming soon (Paxos).
For MiCA reporting, Paxos tells EU crypto-asset service providers with USDG clients to send quarterly and daily data to Paxos Issuance Europe (Paxos). Daily holdings come from wallets registered on the Paxos platform, which Paxos calls the mandatory channel. Quarterly templates are sent by email and are due on 21 January, April, July and October.
For DORA, Protofire's build counts as ICT development (type S02) in the CASP's register of information. Running the feed adds type S14 (Regulation 2024/2956).
Your counsel decides which Paxos entity your firm contracts with.
Build order for a Paxos project
- Step 1
Orchestration rules and the event service come first
Orchestration rules, memo IDs, the transit account and the event service come first. These parts decide whether a mint books once. - Step 2
API approvals and the Travel Rule address backfill
The maker-checker step goes in front of API calls. The address backfill is planned against Paxos's Travel Rule date of 30 November 2026. - Step 3
The daily CSV match and the EU reporting feed
The CSV load, the match and the morning list of open lines go live. For EU CASPs, the USDG wallet feed and the quarterly templates follow. - Step 4
You hold the credentials and the code
Protofire's services call Paxos with OAuth credentials that your staff issue, store in your own vault and may revoke. The code, configuration and runbooks are yours. Your team runs the integration, or Protofire operates it under a written scope that names each write call we make.
How work with Protofire starts
Send us the Paxos entity you onboarded with, your ledger type and the Paxos endpoints you call today.Protofire's first written proposal sets out the orchestration rules, the approval design for API calls and the Travel Rule backfill of your saved addresses. 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.
Three cases where Paxos needs no build from Protofire
In three cases, a firm can work with Paxos without a build from Protofire.
- You mint and redeem by hand. Paxos says firms can "Mint on demand from our Dashboard, create rules to automate conversions or embed flows using our API" (Paxos). With approvals and the daily CSV, the Dashboard can be enough.
- Your payment-operations platform includes Paxos. Modern Treasury announced on 18 December 2025 that it would integrate Paxos so businesses can "originate, reconcile, and manage stablecoin payments" (Modern Treasury).
- Another stablecoin model fits your firm better. BVNK integration covers payouts across third-party stablecoins, Circle integration covers USDC and Circle Mint, and Monerium integration covers euro tokens tied to IBANs.
Protofire holds no financial or crypto-asset license. Protofire does not open the Paxos account, and it does not sign or approve mints and redemptions. We also do not submit your MiCA reports or advise on which Paxos entity to contract with. After launch, Protofire holds no Paxos credential with write scopes, no JWS signing key and no approver seat. Your admins create each credential in the Paxos Dashboard, where creating a credential can itself need a second approver.
FAQ
What is a Paxos integration?
Who can build a Paxos integration for a payment platform, a bank or an EU CASP?
Do Paxos Dashboard approvals cover API redemptions?
Who issues USDG, and who issues PYUSD?
Can Paxos freeze USDG or PYUSD the firm holds?
Which Paxos endpoints have been retired or deprecated?
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.
