> ## Content Index
> Fetch the complete content index at: https://stablecoininsider.org/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Mint and Redeem PYUSD with Paxos Orchestrations (2026)
- URL: https://stablecoininsider.org/how-to-mint-and-redeem-pyusd-with-paxos-orchestrations/
- Published: 2026-09-26T06:15:23.000Z
- Updated: 2026-09-26T06:15:22.000Z
- Description: Run Paxos Orchestrations for PYUSD: OAuth scopes, Profiles, USD wire mint rules, ad-hoc Create Orchestration, and bank redeem with approved fiat accounts.
- Author: Alexandra
- Tags: Fintech, Stablecoins

Treasury leads that want issuer-side PYUSD inventory cannot stop at a merchant settlement toggle. They need a documented mint and redeem loop against the same platform that issues the token.

The named object is **Paxos Orchestrations for PayPal USD (PYUSD)**: OAuth2 client credentials, Profiles that hold balances, orchestration rules that auto-mint USD wires into PYUSD, ad-hoc Create Orchestration calls for profile-to-bank redemptions, and status monitoring via webhooks or List Orchestrations. That is not PayPal merchant rewards settlement, not Circle Mint USDC, and not Ripple Mint RLUSD.

📌

Stablecoin Insider's framing: use this guide when Paxos is your issuer API for PYUSD mint and redeem. Use How to Enable PayPal PYUSD Settlement for Merchant Rewards when the job is PayPal checkout settlement. Use Circle Mint or Ripple Mint when the asset is USDC or RLUSD.

Facts below come from Paxos docs for [Mint orchestrations](https://docs.paxos.com/guides/developer/orchestrations/mint), [Redeem orchestrations](https://docs.paxos.com/guides/developer/orchestrations/redeem), [Convert orchestrations](https://docs.paxos.com/guides/developer/orchestrations/convert), [Authenticate](https://docs.paxos.com/guides/developer/authenticate), [PYUSD overview](https://docs.paxos.com/guides/stablecoin/pyusd), and [PYUSD mainnet addresses](https://docs.paxos.com/guides/stablecoin/pyusd/mainnet) as of September 26, 2026\. Endpoints, scopes, and asset enums are copied from those pages. No invented fees, cutoffs, or undocumented chains.

### Key Takeaways

- Hosts: api.sandbox.paxos.com and api.paxos.com; OAuth at oauth.sandbox.paxos.com / oauth.paxos.com.
- Assets on Orchestrations rules include USD, PYUSD, USDC, USDG, and USDP as documented enums.
- Mint path: Create Orchestration Rule with source fiat WIRE and destination\_asset PYUSD, then wire using memo\_id.
- Redeem path: Create Orchestration with source\_asset PYUSD and destination fiat bank\_account\_id.
- Operator pitfalls: missing orchestration scopes, unapproved fiat accounts, unregistered crypto destinations, stale ref\_id duplicates.

⚠️

Named downside: Paxos Orchestrations is an enterprise integration. Sandbox deposits do not move mainnet value, production wires reject on memo mismatches, and crypto destinations require Put Crypto Destination Address registration before external delivery.

## Who this is for

Use this path if you are a fintech, PSP, or corporate treasury engineer building PYUSD inventory on Paxos, you already understand wire ops and stablecoin KYC, and you can create OAuth2 API credentials in the Paxos dashboard.

Skip it if you only need PayPal merchant settlement (see [PayPal PYUSD Settlement for Merchant Rewards](https://stablecoininsider.org/how-to-enable-paypal-pyusd-settlement-for-merchant-rewards/)), you are minting USDC on Circle (see [Circle Mint USDC](https://stablecoininsider.org/how-to-mint-and-redeem-usdc-with-circle-mint/)), you are minting RLUSD (see [Ripple Mint RLUSD](https://stablecoininsider.org/how-to-mint-and-redeem-rlusd-with-ripple-mint/)), or you want a consumer-style on-ramp overview (see [USD to USDC on-ramp](https://stablecoininsider.org/how-to-on-ramp-usd-to-usdc/)). For Paxos leadership context, see [Charles Cascarilla: Paxos](https://stablecoininsider.org/charles-cascarilla-paxos/). For a different institutional mint product, see [BitGo Mint](https://stablecoininsider.org/bitgo-mint/).

## What Paxos Orchestrations mint and redeem means

PayPal USD (PYUSD) is issued by Paxos Trust Company, LLC. Paxos publishes PYUSD as an open, fully backed U.S. dollar stablecoin with monthly reserve reports and third-party attestations. Mainnet contract addresses are documented for Ethereum, Solana, Arbitrum, Polygon, and X Layer.

Orchestrations are Paxos's single API surface for fiat and stablecoin conversions. An **Orchestration Rule** watches deposits and auto-runs conversions. An ad-hoc **Create Orchestration** call runs a one-time conversion when funds already sit in a Profile. The older Stablecoin Conversions API is read-only for history; new work uses Orchestrations.

Stablecoin Insider's take: treat Profiles as the balance ledger, rules as deposit automation, and Create Orchestration as the explicit mint or redeem button your ops tooling should call.

| Stage               | Paxos endpoint (from docs)                          | Operator check                                 |
| ------------------- | --------------------------------------------------- | ---------------------------------------------- |
| Authenticate        | POST oauth.../oauth2/token (client\_credentials)    | Save access\_token; expires\_in \~3599 seconds |
| List Profiles       | GET /v2/profiles                                    | Confirm DEFAULT profile id                     |
| Mint rule           | POST /v2/orchestration/rules (USD → PYUSD)          | Save deposit\_instructions\_id + memo\_id      |
| Deposit USD         | Wire (prod) or sandbox fiat deposit                 | Memo must match rule memo\_id                  |
| Ad-hoc mint/convert | POST /v2/orchestration/orchestrations               | Unique ref\_id; profile USD → PYUSD            |
| Redeem              | POST /v2/orchestration/orchestrations (PYUSD → USD) | Approved bank\_account\_id required            |
| Monitor             | Webhooks or GET /v2/orchestration/orchestrations    | Watch COMPLETED / FAILED / REJECTED            |

### Prerequisites before the loop

Create API credentials in the Paxos dashboard and request the orchestration and funding scopes Paxos lists for mint, redeem, and convert. Sandbox base URL is **https://api.sandbox.paxos.com**. Production is **https://api.paxos.com**. Token hosts are oauth.sandbox.paxos.com and oauth.paxos.com.

Minimum scopes called out in the Authenticate guide for mint/redeem/convert include orchestration:read\_orchestration, orchestration:write\_orchestration, orchestration:read\_orchestration\_rule, orchestration:write\_orchestration\_rule, funding:read\_profile, funding:write\_profile, plus transfer scopes for fiat accounts, deposit instructions, and crypto destinations.

Create Orchestration Rule documents valid source\_asset and destination\_asset values that include **USDG, PYUSD, USDP, USDC, and USD**. That enum is why PYUSD is a first-class Orchestrations asset, not a side path.

### Step 1\. Authenticate and list Profiles

Request a bearer token with grant\_type=client\_credentials, client\_id, client\_secret, and a space-delimited scope string. Paxos returns access\_token, token\_type bearer, expires\_in (documented as 3599 seconds), and the granted scope list.

Then call **GET /v2/profiles** on the matching API host. Every account has a DEFAULT Profile. Save the profile id you will fund and convert against. Ops teams often keep separate NORMAL Profiles labeled Mint and Redeem for ledger clarity.

⚠️

Operator pitfall: a token without orchestration:write\_orchestration\_rule will create Profiles successfully and still fail when you POST the mint rule. Scope the client for the full mint/redeem loop before you schedule a treasury pilot.

### Step 2\. Create a USD to PYUSD mint orchestration rule

Call **POST /v2/orchestration/rules** with a unique ref\_id, nickname, profile\_id, source\_asset USD, destination\_asset PYUSD, source.fiat.network WIRE, source.fiat.account\_type SWIFT (or ABA where your region uses it), and destination.profile.profile\_id pointing at the funded profile.

The response returns an ACTIVE rule with deposit\_instructions\_id and memo\_id under source.fiat. Pull full bank details with Get Fiat Deposit Instructions using that deposit\_instructions\_id. Production wires must use those instructions and the memo\_id so the rule can match the deposit.

Optional destination variant: instead of parking PYUSD in a Profile, set destination.crypto.address and network after you register the address with Put Crypto Destination Address. Paxos requires that registration for travel-rule compliance and address approval before external delivery.

### Step 3\. Fund the rule (wire or sandbox deposit)

In production, send USD by wire to the Paxos bank account from the deposit instructions, including the memo\_id. The ACTIVE rule detects the deposit, converts USD to PYUSD, and delivers to the rule destination.

In sandbox, use Paxos's documented sandbox deposit flow to simulate fiat funding for a profile. Sandbox deposits do not create mainnet PYUSD. Always keep crypto\_network populated only for crypto sandbox deposits; omit it for fiat.

Monitor with orchestration webhooks (orchestration.processing, orchestration.completed, orchestration.failed, orchestration.rejected) or poll List Orchestrations filtered by profile\_id.

### Step 4\. Ad-hoc mint or convert when USD already sits in a Profile

When USD is already on-platform, skip the rule trigger and call **POST /v2/orchestration/orchestrations**. Set a unique ref\_id for idempotency, source\_amount as a decimal string, source\_asset USD, destination\_asset PYUSD, and source/destination profile objects. Retries must reuse the same ref\_id or you risk duplicate conversions; a conflicting new ref\_id can create a second orchestration.

The Convert guide shows the same Create Orchestration shape for PYUSD to USDG profile-to-profile moves. Use that when treasury needs to rebalance across Paxos-issued assets rather than redeem to fiat.

### Step 5\. Redeem PYUSD to USD at an approved bank

First create and approve a fiat bank account (Create Fiat Account). Confirm status APPROVED with Get Fiat Account before redeeming.

Then Create Orchestration with source\_asset PYUSD, source\_amount, destination\_asset USD, source.profile.profile\_id for the funded profile, and destination.fiat.bank\_account\_id plus an optional memo. Paxos validates balance and bank status, converts PYUSD to USD, and wires USD to the bank.

For inbound crypto auto-redeem, create an Orchestration Rule with source.crypto.network (for example ETHEREUM), source\_asset PYUSD, destination\_asset USD, and the approved bank destination. External PYUSD sent to the rule's deposit address triggers conversion and withdrawal.

### Step 6\. Verify balances and onchain inventory

List Profile Balances or Get Profile Balance for PYUSD and USD after each orchestration reaches COMPLETED. If you withdrew to an external address, confirm the chain using Paxos's published mainnet addresses (Ethereum 0x6c3ea9036406852006290770BEdFcAbA0e23A0e8, plus Solana, Arbitrum, Polygon, and X Layer addresses in the mainnet guide).

Stablecoin Insider's take: ledger the Profile balance as the source of truth for issuer inventory, then reconcile external wallets separately. Do not treat a pending orchestration as settled PYUSD.

### Sandbox to production pitfalls

- Sandbox hosts and OAuth URLs differ from production. Flip both when you leave sandbox.
- Keep ref\_id unique per intended orchestration; reuse only for true retries.
- External crypto destinations must be registered before rule or orchestration delivery.
- Redeem fails if the fiat account is not APPROVED, even when PYUSD balance looks correct.
- Orchestrations replace Stablecoin Conversions for new mints and redeems; do not rebuild on the deprecated write path.

### How this differs from PayPal settlement and other mint APIs

PayPal PYUSD Settlement for Merchant Rewards is a merchant checkout path that settles in PYUSD with rewards logic. Paxos Orchestrations is the issuer/custody API that creates and destroys PYUSD against USD on Paxos Profiles. Circle Mint mints USDC. Ripple Mint mints RLUSD. BitGo Mint is a separate institutional mint product for other tickers. Pick the named object that matches the asset and the counterparty you actually integrate.

## Stablecoin Insider's take

💡

Stablecoin Insider's take: the teams that win on PYUSD treat Paxos Orchestrations as treasury plumbing, not a marketing checkbox. Wire memo hygiene, APPROVED bank accounts, and registered crypto destinations decide whether the loop closes. The downside is enterprise friction: scopes, KYC, and fiat approvals gate every production redeem, so sandbox confidence only counts after the first live wire matches memo\_id exactly.

[How to Enable PayPal PYUSD Settlement for Merchant RewardsMerchant-side PYUSD settlement path. Different from issuer mint/redeem on Paxos Orchestrations.![](https://stablecoininsider.org/favicon.ico)Stablecoin Insider](https://stablecoininsider.org/how-to-enable-paypal-pyusd-settlement-for-merchant-rewards/)

[How to Mint and Redeem USDC with Circle MintParallel mint/redeem loop for USDC on Circle Mint when PYUSD is not the asset.![](https://stablecoininsider.org/favicon.ico)Stablecoin Insider](https://stablecoininsider.org/how-to-mint-and-redeem-usdc-with-circle-mint/)

---

## FAQ

#### What is Paxos Orchestrations for PYUSD?

It is Paxos's API for converting USD to PYUSD and PYUSD back to USD using Profiles, Orchestration Rules for deposit-triggered automation, and Create Orchestration for one-time conversions.

#### Which assets can Orchestration Rules use?

Paxos documents valid source\_asset and destination\_asset values that include USDG, PYUSD, USDP, USDC, and USD on the Create Orchestration Rule endpoint.

#### Do I need a rule to mint PYUSD?

No. Rules auto-mint when a matching USD wire arrives. If USD already sits in a Profile, call Create Orchestration with source\_asset USD and destination\_asset PYUSD.

#### How do I redeem PYUSD to my bank?

Approve a fiat bank account, then Create Orchestration with source\_asset PYUSD, destination\_asset USD, and destination.fiat.bank\_account\_id. Paxos converts and wires USD.

#### Which chains carry PYUSD mainnet?

Paxos documents mainnet addresses for Ethereum, Solana, Arbitrum, Polygon, and X Layer in the PYUSD on Main Networks guide.

#### How is this different from PayPal PYUSD Settlement?

PayPal settlement is a merchant checkout and rewards path. Paxos Orchestrations is the issuer API that mints and redeems PYUSD against USD on Paxos Profiles.

#### How long does the OAuth token last?

Paxos documents expires\_in as 3599 seconds (just under one hour). Refresh before mint or redeem batches that can outrun that window.

#### Can I convert PYUSD to another Paxos stablecoin without redeeming to fiat?

Yes. The Convert guide shows Create Orchestration examples such as PYUSD to USDG profile-to-profile, using the same Orchestrations surface.

---

[Read Paxos Mint orchestrations docs](https://docs.paxos.com/guides/developer/orchestrations/mint)

Building PYUSD treasury rails? Start with Paxos Orchestrations mint and redeem, then harden memo matching, APPROVED bank accounts, and registered crypto destinations before you flip production hosts.

[Open Paxos PYUSD docs ](https://docs.paxos.com/guides/stablecoin/pyusd) 

This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.