
Online
Keep your storefront. Connect Shopify, WooCommerce, payment links or the REST API. Customers choose supported crypto; you receive shielded ZEC.
Learn more →Plug into what you already run. Payment links and hosted checkout are in Get started below.

Keep your storefront. Connect Shopify, WooCommerce, payment links or the REST API. Customers choose supported crypto; you receive shielded ZEC.
Learn more →
iPad POS for markets and retail. QR checkout, tips, and receipts on any tablet.
Learn more →x402 paywalls and MCP for AI agents. Shielded ZEC — no public payment graph.
Learn more →Get paid below shows the checkout page your customers scan.
Your customers pick the token and network. You receive ZEC straight to your shielded wallet.
Straight to your wallet.
Conversion powered by NEAR Confidential Intents.
Network availability and minimum amounts vary. Transfers on the source chain remain public.
Direct ZEC checkout does not ask for buyer identity; the comparison below covers this route. Other crypto uses NEAR Confidential Intents, and source-chain transfers remain public.
curl -X POST https://api.cipherpay.app/api/invoices \
-H "Authorization: Bearer cpay_sk_..." \
-H "Content-Type: application/json" \
-d '{"amount": 29.99, "currency": "USD", "product_name": "T-Shirt"}'
# Response:
# {
# "invoice_id": "a1b2c3...",
# "memo_code": "CP-C6CDB775",
# "price_zec": 0.12345678,
# "zcash_uri": "zcash:u1...?amount=0.12345678&memo=...",
# "payment_address": "u1...",
# "expires_at": "2026-02-21T13:30:00Z"
# }Every AI agent payment on Base, Solana, or Polygon is a public record. Your agent's operational strategy — what APIs it calls, what data it buys, how often — is visible to anyone.
Zcash shielded payments make all of that invisible.
GET /api/premium — no credentials402 Payment Required — amount, address, memoOrchard shielded tx — sender, receiver, amount encryptedIVK trial decryption — stateless, no custody200 OK — resource delivered