Multi-Chain Checkout UX & Dual Payment Architecture

1. Why Multi-Chain UX Determines Checkout Conversion

Over 62% of retail stablecoin buyers pay either from a mobile wallet on low-fee rails (TRON TRC-20, Base, Polygon, Arbitrum, Solana) or directly from an exchange withdrawal screen (Binance, Coinbase, OKX, Bybit). Forcing buyers onto a single chain or requiring a desktop browser extension reduces completion rates. XPayr solves this with a Dual Checkout Surface:

2. Drop-In Multi-Chain Payment Button (`xpayr-pay-button.js`)

You can embed a pre-configured multi-chain checkout modal on any landing page or SaaS billing view using our zero-dependency SDK or customize it visually in the Payment Button Generator:

<!-- Embeddable XPayr Multi-Chain Payment Button SDK -->
<script src="https://xpayr.com/public/sdk/xpayr-pay-button.js" defer></script>

<div
  data-xpayr-pay-button
  data-amount="149.00"
  data-currency="USDC"
  data-network="base-mainnet"
  data-label="Pay $149 USDC (0.5% Fee)"
  data-theme="emerald">
</div>

3. Querying Active Networks via Remote MCP (`POST https://xpayr.com/api/mcp`)

AI commerce agents and backend services can dynamically inspect supported networks, confirmation targets, and token decimals using the xpayr_list_supported_networks MCP tool:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "xpayr_list_supported_networks",
    "arguments": {
      "environment": "mainnet"
    }
  }
}