Payclave SDKs are available

Customers pay with any supported token. You receive USDC or USDT in your own wallet.

Payclave is non-custodial crypto checkout for modern merchants. Customers pay with the tokens already in their wallet, from ETH to stablecoins on supported networks, or use Scan or copy. Payclave converts each payment into USDC or USDT on Polygon, settles it directly to a wallet you control, and verifies it onchain before reporting the invoice paid.

Connected-wallet options depend on the customer's wallet and payment route. Scan or copy can offer one-time deposit instructions on the networks below, subject to route availability. Merchant settlement remains USDC or USDT on Polygon.

Pay with any token

Customers pay with what they already hold.

No swapping or bridging before checkout. Customers pick a token from their wallet, or use Scan or copy on a supported network. The payment route converts it on the way, so you always receive USDC or USDT on Polygon in your own wallet.

250.10 USDTYour serverYour serverPayclavePayclavePays 0.0771 ETHETH → 250.10 USDTVerified onchain+248.35 USDTinvoice.paid · 200 OK

Pay from any token. The customer picks a verified token they already hold, or sends it with Scan or copy.

Customers can pay with verified tokens in their wallet on supported networks when a payment route is available. You receive the invoice amount minus Payclave's 0.7% fee. Network costs may appear in checkout.
What Payclave handles

A hosted payment flow without Payclave custody.

Payclave provides the customer-facing checkout, payment links, invoices, payment records, API keys, and webhook delivery. Settlement reaches the merchant-controlled wallet you configure. Payclave does not hold it or require a later payout.

A hosted checkout your customers can finish.

Customers connect a wallet or use Scan or copy, see the exact amount, token, and network, and follow payment status on a Payclave-hosted page. Your site only needs a link or a button.

See how it works
server/checkout.ts
1import { createPayclaveServerClient } from "@payclave/sdk-server"23// Run this on your server4const payclave = createPayclaveServerClient({5 secretKey: process.env.PAYCLAVE_SECRET_KEY,6})78export async function POST() {9// Create a hosted checkout session10const session = await payclave.createCheckoutSession({11 amount: "249.00",12 externalReference: "order_3041",13 idempotencyKey: "order_3041",14})15return Response.json({ checkoutUrl: session.checkoutUrl })16}

Public keys in the browser. Secret keys on the server.

JavaScript and React integrations use a public key for limited checkout creation. For production orders, create sessions on your server with a secret key. Signed webhooks, delivery attempts, and idempotency keys support reliable fulfillment.

See how it works

Customers pay from the wallet they already use.

Checkout connects MetaMask, Coinbase Wallet, browser wallets, and other wallets through WalletConnect. Customers review the route and fees, then approve the payment in their own wallet. Payclave never receives their keys.

See how it works

No wallet to connect? Scan or copy.

Customers can scan a QR code or copy a one-time deposit address and send from any wallet on a supported network. Payclave verifies the payment onchain before the invoice is marked paid.

See how it works
Agentic payments

AI agents can pay you too.

Every checkout that settles in USDC also answers x402, the open standard for payments over HTTP. An AI agent pays from its own wallet, the money lands in yours, and Payclave verifies it onchain before the invoice is paid. No Payclave fee on x402 payments through December 31, 2026.

Explore agentic payments
PayclaveAI agentAI agent's walletYour settlement walletPayclave verifies, never holds funds
AI agent's walletPayclave verifies, never holds fundsYour settlement wallet
  1. The agent asks for the checkout

    It requests the checkout's x402Url like any other web resource.

  2. Payclave names the price

    A 402 Payment Required response sets the amount, USDC, the network and your wallet.

  3. The agent signs and pays

    USDC moves from the agent's wallet straight to yours. Payclave never holds it.

  4. Verified, then notified

    Payclave confirms the transfer onchain, marks the invoice paid and sends your webhook.

Agents pay in USDC onBBasePPolygonAArc Network
Trust model

Payclave never holds customer payments or merchant settlement.

Payclave creates checkout instructions, records payment attempts, and verifies settlement. It never receives private keys or controls the merchant's settlement wallet. See how funds move.

No Payclave-held funds

Settlement reaches the merchant-controlled wallet configured for checkout. Payclave does not hold it or make a later payout.

USDC or USDT on Polygon

Merchants choose one supported Polygon stablecoin for settlement. Customer payment routes may vary.

Verified before paid

Payclave checks onchain settlement independently before it reports a paid invoice or sends the matching webhook.

Payclave250.10 USDTCustomer's walletYour settlement walletPayclave verifies, never holds funds
Customer's walletPayclave verifies, never holds fundsYour settlement wallet
How Payclave works

A clear path from checkout creation to fulfillment.

Payclave links the customer's checkout, the merchant's settlement, the verified payment record, and the fulfillment event. Test checkout creation and webhook handling end to end before requesting live access.

1. Create a checkout

Create a payment link, invoice, or checkout session, then send the customer to a Payclave-hosted URL.

2. The customer chooses how to pay

The customer connects a supported wallet or requests one-time deposit instructions. Available routes depend on the source token and network.

3. Settlement reaches your wallet

The merchant receives USDC or USDT on Polygon in the configured settlement wallet. Payclave never holds the merchant's settlement.

4. Payclave verifies the payment

Onchain checks confirm the transaction, chain, token, recipient, amount, timing, confirmation state, and duplicate-use rules.

5. Your backend receives a signed event

Payclave signs each webhook, records delivery attempts, retries endpoint failures, and supports manual replay from the dashboard.

6. Your team reviews the record

Review invoices, payment records, platform fees, net settlement, API keys, settlement wallet settings, and webhook delivery status.

FAQ

Practical answers before you integrate.

Learn what Payclave controls, how payment confirmation works, and what changes when you move from test mode to live mode. Contact us if your question is not covered here.

Pricing

One live payment fee. No monthly plan.

Payclave charges 0.7% of each completed live payment. The fee comes from the listed invoice amount, so the customer pays that amount and the merchant receives the remaining 99.3%. The standard checkout has no monthly or setup fee. Network costs are separate and may appear in checkout.

Test mode

$0

Build and validate a Payclave checkout integration without moving real funds.

  • Merchant profile setup

  • Separate test public and secret keys

  • Payclave-hosted test checkout

  • Invoice and payment records

  • Test webhook delivery

Open API playground

Pay as you go

Direct settlement

0.7%per payment

For merchants ready to accept real stablecoin payments.

  • 0.7% per completed live payment

  • No monthly fee or setup fee

  • USDC or USDT settlement on Polygon

  • Independent onchain verification

  • Signed webhooks with retries

Get started

Larger rollout

Talk to us

For businesses evaluating Payclave at higher volume. We will confirm eligibility, current product scope, and written commercial terms before launch.

  • Payment links and Payclave-hosted checkout

  • USDC or USDT settlement on Polygon

  • Independent onchain verification

  • Signed webhooks with retry records

  • Separate test and live modes

Discuss your rollout

Build and test your first Payclave checkout.

Set up your merchant profile, configure a test settlement wallet for USDC or USDT on Polygon, generate test keys, and create a hosted checkout through the API, an SDK, or the API playground.