Accept Euro Coin (EURC) and USDC with strict non-custodial software separation.
XPayr operates strictly as non-custodial technical checkout and webhook software — never safeguarding private keys, holding client funds, or operating an omnibus custodial exchange book.
European and cross-border merchants increasingly prioritize e-money token (EMT) stablecoins such as Circle Euro Coin (EURC) and USD Coin (USDC) to eliminate FX drift and align with EEA exchange availability. XPayr supports native EURC and USDC across Base, Solana, Arbitrum, Ethereum, Avalanche, and Circle Arc while maintaining a 100% non-custodial technical software boundary.
Merchant enables EURC and USDC settlement into merchant-controlled EVM, Solana, or Circle Arc wallets.
EEA buyers pay in EURC or USDC via 1-Click Web3 Wallet (including ERC-2612 Permit sem Gas) or regulated exchange withdrawal.
99.5% settles directly on-chain to the merchant wallet without passing through any XPayr-held omnibus account.
Merchant exports EUR/USD invoice records, tx_hash proofs, and @xpayr/payment-evidence envelopes for tax and audit review.
Who pays gas?
Supported EVM chains allow ERC-2612 Permit sponsorship (/gasless), or standard payer-side sub-cent L2/Solana network fees.
Operational limit
XPayr documentation describes technical software architecture, not legal advice; merchants remain responsible for their own corporate tax, invoicing, and jurisdiction-specific regulatory obligations.
FAQ
What problem does this XPayr flow solve?
European and cross-border merchants increasingly prioritize e-money token (EMT) stablecoins such as Circle Euro Coin (EURC) and USD Coin (USDC) to eliminate FX drift and align with EEA exchange availability. XPayr supports native EURC and USDC across Base, Solana, Arbitrum, Ethereum, Avalanche, and Circle Arc while maintaining a 100% non-custodial technical software boundary.
Who pays gas or network fees?
Supported EVM chains allow ERC-2612 Permit sponsorship (/gasless), or standard payer-side sub-cent L2/Solana network fees.
What should merchants not assume?
XPayr documentation describes technical software architecture, not legal advice; merchants remain responsible for their own corporate tax, invoicing, and jurisdiction-specific regulatory obligations.
Publicly auditable SDKs, cryptographic evidence envelopes, and MCP registries.
Servidor MCP Oficial de 21 Ferramentas
Registered as io.github.xpayrcom/xpayr-mcp-server on the Official Anthropic MCP Registry and published as @xpayr/mcp-server on NPM and ghcr.io/xpayrcom/xpayr-mcp-server:latest.
Merkle Payment Evidence & ES256 Tokens
Verify on-chain settlement envelopes with @xpayr/payment-evidence and offline-verifiable ES256 wallet licenses with @xpayr/extension-kit.
30 Open-Source Repositories & RFC 9116
Inspect all 20 REST API v1 schemas interactively at api-docs.xpayr.com, review our 30 repositories at github.com/xpayrcom, and check /.well-known/security.txt & /.well-known/jwks.json.
Precisa comprovar o fluxo antes da produção?
Use checkout testnet, documentos de API, guias de webhook e explicadores operacionais antes de solicitar a ativação da mainnet.