Sponsor supported token checkout fees only where the token and route allow it.
Mit der Gebührendelegation können Händler gesponserte Gebührenrichtlinien für unterstützte genehmigungsbasierte Tokenflüsse konfigurieren. Für nicht unterstützte Token wird auf die normale Wallet-Zahlung zurückgegriffen.
Fee Delegation is a policy and execution model for supported gasless token payments. It requires merchant policy activation, a compatible deployed router, relayer configuration, and a token that supports permit-style approvals.
Merchant enables fee delegation policy and limits.
Checkout detects whether the selected token supports the required approval flow.
Supported payments use the gasless route and relayer policy.
Unsupported tokens use the normal wallet transaction path.
Who pays gas?
Sponsored gas is paid by the configured relayer or policy wallet. If the token is not supported, the payer uses the standard wallet gas flow.
Operational limit
Fee Delegation is not universal gasless crypto. It only applies to supported token, route, contract, and policy combinations.
FAQ
What problem does this XPayr flow solve?
Fee Delegation is a policy and execution model for supported gasless token payments. It requires merchant policy activation, a compatible deployed router, relayer configuration, and a token that supports permit-style approvals.
Who pays gas or network fees?
Sponsored gas is paid by the configured relayer or policy wallet. If the token is not supported, the payer uses the standard wallet gas flow.
What should merchants not assume?
Fee Delegation is not universal gasless crypto. It only applies to supported token, route, contract, and policy combinations.
Publicly auditable SDKs, cryptographic evidence envelopes, and MCP registries.
Offizieller 21-Tool-MCP-Server
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.
Müssen Sie den Ablauf vor der Produktion prüfen?
Nutzen Sie Testnet Checkout, API-Dokumente, Webhook-Anleitungen und Betriebserklärungen, bevor Sie eine Mainnet-Aktivierung anfordern.