Enterprise MPC-CMP Custody · Regulated Operator Ready

Connect Cofre Fireblocks MPCs to XPayr Non-Custodial Checkout (0.5%)

Pair XPayr Checkout Duplo, 24 storefront plugins, and HTTP 402 agent paywalls with your existing Fireblocks MPC-CMP treasury — liquidando 99.5% directly into your Fireblocks vault accounts without creating a second custodial processor silo.

Começar grátis na Testnet 🧪 Test in Live Sandbox ⚙️ Gerador de Código em 8 Linguagens 👛 All 12 Wallets & Exchanges
Checkout FlowEnterprise MPC Vault Settlement + WalletConnect v2
Protocol StandardMPC-CMP · Policy Engine · WalletConnect v2 · Travel Rule Ready
Tolerance / Split99.5% Direct On-Chain Settlement to MPC Vault Addresses
XPayr Fee0.5% Flat · $0/mo · Non-Custodial

Fireblocks Integration Architecture

Zero Fireblocks API Key Exposure Needed for Inbound Settlement

You never hand Fireblocks API co-signer credentials to XPayr. Simply whitelist and assign your Fireblocks omnibus or per-business-unit deposit addresses as your XPayr destination wallets.

Preserve Fireblocks TAP Policies, AML Screening & KYT

Because 99.5% lands directly on-chain in your Fireblocks vault, your existing Chainalysis/Elliptic KYT rules and Transaction Authorization Policy (TAP) workflows trigger natively.

Sub-Ledger Metadata + @xpayr/payment-evidence Reconciliation

Match Fireblocks inbound vault webhooks with XPayr order_id, player/account metadata (/player-deposits), and NetSuite/ERP JSON exports (/accounting) via deterministic tx_hash.

High-Conversion Merchant Use Cases

Enterprise SaaS, fintechs, regulated trading & prop platforms, global marketplaces, and licensed operators already standardizing on Fireblocks MPC.

Supported Rede Blockchains

Ethereum Base Arbitrum Polygon Optimism Solana TRON BNB Smart Chain Avalanche Bitcoin TON Circle Arc

Supported Stablecoins & Tokens

USDC EURC USDT PYUSD DAI BTC ETH SOL TRX

REST API v1 Session Payload

Create a checkout session pre-optimized for Fireblocks via POST https://xpayr.com/api/v1/payments or the xpayr_create_payment_session do MCP:

{
    "amount": "99.00",
    "currency": "USD",
    "preferred_network": "ethereum",
    "preferred_token": "USDC",
    "checkout_mode": "exchange_qr",
    "underpayment_tolerance_pct": 1,
    "underpayment_tolerance_max_usd": 0.5,
    "order_id": "ord_fireblocks_4082",
    "webhook_url": "https://merchant.example.com/webhooks/xpayr",
    "metadata": {
        "wallet_corridor": "fireblocks",
        "settlement_model": "99.5_pct_non_custodial"
    }
}

Related Engineering Blueprints

Corporativo e SLA Hub → EU MiCA & Compliance Hub → Player & Account Top-Ups → Multisig & Vault Planner →

Compare Other Wallets & Exchanges

MetaMask Phantom Trust Wallet Coinbase Wallet WalletConnect Rabby Tonkeeper TronLink Binance QR Bybit QR OKX Kraken Safe{Wallet} Squads Ledger

Cofre Institucional MPC da Fireblocks Checkout — Perguntas Frequentes

Does XPayr require read/write access to our Fireblocks API workspace?

No. Inbound XPayr checkout settlements only need your public Fireblocks vault deposit addresses, keeping your MPC key shares and Fireblocks API keys 100% isolated inside your security perimeter.

How do we correlate Fireblocks vault deposits with specific customer orders?

XPayr tracks each checkout session on-chain and delivers signed X-XPayr-Signature webhooks containing both order_id, customer metadata, and the exact tx_hash observed in Fireblocks.

Can institutional buyers pay an XPayr B2B invoice from their own Fireblocks workspace?

Yes — institutional buyers can either connect via Fireblocks WalletConnect v2 or whitelist your invoice destination address for a direct vault transfer.