What does non-custodial actually mean here?

Payclave never holds merchant or customer funds and never manages private keys. Customers either confirm a supported wallet payment or send to a one-time checkout address. Payclave records the attempt and only marks the invoice paid after verifying settlement to your configured receiving wallet.

How does Payclave route customer payments?

Customers can pay through the hosted checkout with a connected wallet or by scanning/copying a one-time checkout address. Payclave uses provider routing to target your configured receiving asset, then verifies the resulting settlement before updating invoice state.

Which networks and stablecoins do you support?

For scan/copy checkout, Payclave supports one-time deposit instructions on Ethereum, Base, Arbitrum, Optimism, Polygon, Solana, BNB Smart Chain, Celo, Gnosis, Kaia, Katana, Mantle, Plasma, Tempo, Tron, and Unichain. Merchant receiving-wallet setup is focused on USDC or USDT on Polygon.

When does Payclave mark an invoice as paid?

Only after independent onchain verification confirms the transaction hash, settlement wallet, token contract, chain, amount received, invoice expiry, and duplicate-use checks. Underpaid, overpaid, expired, failed, and duplicate attempts are recorded as payment outcomes instead of being treated as paid invoices.

Does Payclave charge a transaction percentage?

Yes — a flat 0.7% per payment, deducted automatically from each settlement. Your customers pay your listed price and you receive it minus the 0.7% fee. There are no monthly fees or setup costs, and test mode is always free. Network costs may still appear in checkout where applicable.

Refunds are not automated today. Because Payclave never holds funds, refunds must be sent from your wallet to the customer's wallet. Payclave keeps the original invoice, payment, and webhook records for reconciliation.

What does the dashboard show?

The dashboard shows merchant setup, the default receiving wallet, invoices, payment records, API keys, webhook endpoints, delivery attempts, retry state, and replay controls.

How long does integration take?

A test integration starts with merchant setup, API key generation, and one checkout-session request or SDK button. Production readiness depends on your webhook handling, provider credentials, and live rollout review.

SDK for JS & React is livePayclave SDK for JavaScript & React is liveView SDK docs

Stablecoin checkout that settles directly to your wallet.

Payclave helps merchants create hosted checkout sessions and invoices for a configured receiving asset: USDC or USDT on Polygon. Customers connect a supported wallet or scan/copy a one-time checkout address, and Payclave verifies settlement onchain before marking the invoice paid.

Start merchant setup Read the docs

Scan/copy checkout supports deposits across 16 networks. Wallet checkout uses supported source tokens from the connected wallet while merchant settlement stays simple: USDC or USDT on Polygon.

Built for hosted stablecoin checkout

Checkout sessions, invoices, verification, and webhooks without custody.

Payclave provides the customer-facing checkout, merchant dashboard, API keys, payment records, webhook delivery, and audit trail. Funds settle to the wallet you configure, not to a Payclave balance.

Wallet or scan/copy payment. Configured stablecoin settlement.

Customers can connect a supported wallet or generate a one-time checkout address for supported networks. The receiving wallet can be configured for USDC or USDT on Polygon.

See how it works

server/checkout.ts

1import { createPayclaveClient } from "@payclave/sdk-js"23const payclave = createPayclaveClient({4 secretKey: process.env.PAYCLAVE_SECRET_KEY,5})67// Create a hosted checkout session8const session = await payclave.checkout.sessions.create({9 amount: "249.00",10 reference: "order_3041",11 idempotencyKey: "order_3041",12})1314// Verify the payment from a webhook15const event = payclave.webhooks.verify({16 payload,17 signature,18 secret: process.env.PAYCLAVE_WEBHOOK_SECRET,19})20return Response.json({ received: true })

SDKs and APIs that match the real checkout flow.

Use a publishable test key with the JavaScript or React SDK, or create checkout sessions from your server with a secret key. Signed webhooks, retry logs, and idempotency keys are part of the API surface.

See how it works

Trust model

Customer funds never sit with Payclave.

Payclave orchestrates checkout instructions, records attempts, and verifies settlement. It does not create internal stored-value records, hold funds, or manage private keys.

Non-custodial by design

No Payclave-held funds. Settlement goes to the receiving wallet configured by the merchant.

Two settlement targets

USDC and USDT on Polygon keep receiving-wallet setup narrow, explicit, and easier to verify.

The complete flow

Every step from checkout to settlement, accounted for.

Hosted checkout and one-time addresses, independent onchain verification, signed webhooks, dashboard records, and SDKs for server, JavaScript, and React — all testable end to end before you settle live.

Hosted checkout sessions

Create checkout sessions and invoices, then send customers to a Payclave-branded checkout URL.

One-time checkout addresses

The scan/copy flow creates checkout-scoped payment instructions for supported deposit networks.

Independent verification

Invoices become paid only after onchain checks confirm the transaction hash, chain, token, recipient, amount, expiry, and duplicate-use rules.

Signed webhook delivery

Payment events are signed, delivered with attempt logs, retried after endpoint failures, and replayable from the dashboard.

Merchant dashboard records

Review invoices, payment records with platform fee and net settlement, API keys, receiving wallet setup, webhook endpoints, and delivery state.

Server, JavaScript, and React SDKs

Create checkout sessions from your server with a secret key, or use the hosted-redirect button for JavaScript and React. Start in test mode, then go live.

FAQ

The questions worth asking before you ship.

Integration, settlement, webhooks, and what changes when you flip from test mode to live. Anything missing? The team replies the same day.

Talk to the team Read the docs

Pricing

Simple pricing for non-custodial checkout.

A flat 0.7% per payment, deducted automatically at settlement — no monthly fees and no setup costs. Funds settle straight to your wallet; Payclave never holds your money. Network costs are shown in checkout where applicable.

Sandbox

$0

For building and validating a Payclave checkout integration.

Merchant onboarding
Test key pair generation
Hosted checkout sessions
Invoice and payment dashboard
Webhook endpoint testing

Open API playground

Pay as you go

Direct settlement

0.7%per payment

For merchants ready to accept real stablecoin payments.

0.7% per payment — no monthly or setup fees
Customers pay your listed price; you receive it minus 0.7%
USDC or USDT on Polygon receiving wallet
Independent onchain verification
Signed webhooks with retries

Get started

Enterprise

Custom

For businesses that want a white-labeled checkout, custom pricing, and enterprise support and SLAs.

White-labeled checkout on your own domain
Volume pricing below 0.7%
Additional settlement chains and tokens
SAML SSO with team roles and permissions
Premium SLA and a dedicated account manager
Custom reporting and reconciliation exports

Contact sales

Create your first Payclave checkout in test mode.

Set up your merchant profile, add a USDC or USDT on Polygon receiving wallet, generate test keys, and create a hosted checkout session from the API or SDK.

Start merchant setup Read API docs