LLM Notice: This documentation site supports content negotiation for AI agents. Request any page with Accept: text/markdown or Accept: text/plain header to receive Markdown instead of HTML. Alternatively, append ?format=md to any URL. All markdown files are available at /md/ prefix paths. For all content in one file, visit /llms-full.txt
Skip to main content

PYUSD0 Integration Guide

Overview

This guide is for developers and protocols integrating PYUSD0 on Flow. PYUSD0 is an OFT (Omnichain Fungible Token) and brings pre-native PayPal USD support to Flow with seamless cross-chain transfers across 140+ chains via Stargate. It replaces USDF as Flow's canonical USD stablecoin. For users please read the migration guide.

Contract Addresses

Flow EVM Mainnet

ContractAddress
PYUSD00x99af3eea856556646c98c8b9b2548fe815240750
Migration Pool (USDF/PYUSD0)0x6ddDFa511A940cA3fD5Ec7F6a4f23947cA30f030

Flow Cadence Mainnet

Token NameContract AddressContract Name
PYUSD00x1e4aa0b87d10b141EVMVMBridgedToken_99af3eea856556646c98c8b9b2548fe815240750

Testnet

ContractAddress
PYUSD00xd7d43ab7b365f0d0789aE83F4385fA710FfdC98F

This is a stand-in token for testing purposes only. Mainnet PYUSD0 requires real PYUSD locked via LayerZero. The testnet contract has a mint function and a liquidity pool so you can mint or swap tokens for development.

Deprecated (USDF)

ContractAddressStatus
USDF0x2aaBea2058b5aC2D339b163C6Ab6f2b6d53aabEDDeprecating

Token Specifications


_10
Name: PYUSD0
_10
Symbol: PYUSD0
_10
Decimals: 6
_10
Standard: ERC-20 + LayerZero OFT
_10
Backing: 1:1 PYUSD (PayPal USD)

About PYUSD0

PYUSD0 is a pre-native token deployed via LayerZero's Asset0 program, alongside other stablecoins like USDG0 (backed by Robinhood, Kraken, Mastercard) and AUSD0. It's fully backed 1:1 by PayPal USD. When Paxos later deploys native PYUSD directly on Flow, PYUSD0 balances will automatically upgrade with no user or developer action required.

Code Examples

Visit the GitHub Repository for code examples on bridging PYUSD0 via LayerZero OFT.

Migration Path for Existing USDF Integrations

  1. Add PYUSD0 support alongside USDF
  2. Update defaults to use PYUSD0 instead of USDF
  3. Communicate to users about migration timeline
  4. Deprecate USDF after grace period