BitPay alternative with non-custodial wallet payout

Fee structure comparison

BitPay publishes tiered percentages plus per-transaction fixed fees per their public pages, checked October 2026. CXPay uses flat published percentages with a minimum per payment and optional CXCASH discount.

Your effective rate depends on volume, ticket size, and how often payers use CXCASH.

Model a $100 order at $1.00 CXPay standard fee versus BitPay published 2% + $0.25 on smaller tiers, then adjust for your monthly volume tier on their site.

Merchants who educate payers about exact amounts and quote expiry see fewer support tickets. Publish your accepted assets and networks on your store policy page and link to CXPay asset guides. When customers pay with ETH or BTC, remind them that network fees appear separately from the CXPay merchant fee. For audiences comfortable with Aztec, highlight CXCASH as a gas-free alternative through cxcash.app.

Onboarding and compliance posture

BitPay requires substantive business verification per their public pages, checked October 2026. CXPay keeps merchant onboarding lightweight without collecting government ID in the described flow.

Merchants remain responsible for their own legal obligations regardless of processor.

Custody and treasury

CXPay routes sales to your wallet. BitPay can pay out to bank accounts—valuable if you need fiat, irrelevant if you want on-chain treasury.

With CXPay there is no processor balance to withdraw and no payout schedule to wait for: each confirmed payment is already in your wallet. That also means you, not CXPay, are responsible for securing that wallet and for converting crypto to fiat if your accounting requires it.

When CXPay may fit better

Choose CXPay when you want crypto-native settlement, predictable published fees, and WooCommerce or API integrations without KYB document upload.

Choose BitPay when you require fiat settlement and accept their verification process.

The merchant dashboard and GET /reports/payments help you filter by status and time range. Download GET /exports/payments.csv when finance needs a spreadsheet-friendly view. Pair exports with webhook-driven order updates so internal systems stay aligned with on-chain settlement. Because CXPay does not hold balances, your wallet history and CXPay reports together form the reconciliation trail.

Migration considerations

Server integrations should create payment intents with Idempotency-Key headers, persist the returned intent ID on your order row, and only mark paid after payment.succeeded verifies on your webhook handler. Test keys let you exercise the full lifecycle without touching live balances. WooCommerce merchants request the official plugin through the contact form and configure API base URL plus webhook secrets before going live.

Side-by-side comparison

Explore CXPay

• How CXPay works
• Pricing and fee examples
• API quickstart
• Frequently asked questions
• Create a merchant account
• Compare hub

Questions about this page