ZamaPay
DashboardDemo
Pricing
Log in

Private checkout infrastructure for crypto merchants

ZamaPay gives merchant products a hosted crypto checkout, wallet-gated project console, encrypted Zama settlement, and finality-safe webhook release without mixing payment state into the merchant app.

Log inView integration flowRead docs
ZamaPay workspace
Project: merchant-prod
live rail
ZamaPay merchant console screenshot
Checkout readiness25%
Hosted checkout

120 cUSDT

Create
MerchantMerchant checkout
Invoiceinvoice-1b7460
Privacyencrypted amount check
ReleaseInvoice minted
Invoice minted

Merchant creates a hosted checkout from the ZamaPay console.

Project configured
Checkout link issued
Encrypted payment accepted
Finality-safe webhook

The payment layer stays outside your app

Merchant products keep their catalog and fulfillment logic. ZamaPay owns the payment rail, hosted checkout, settlement privacy, and callback truth.

Checkout components
Checkout components
Merchants create projects, issue checkout URLs, and keep invoice state in one operational console.
Confidential settlement
Confidential settlement
Payment amount checks stay encrypted on the Zama rail until the authorized merchant decrypts.
Fulfillment webhooks
Fulfillment webhooks
Release digital goods only after payment truth, chain finality, and webhook delivery agree.

A checkout operation loop you can see

Configure a project, send the buyer through hosted checkout, wait for finality, then release fulfillment from the merchant backend.

Create projectproject live
Merchant console

Merchant configures checkout, callback URL, and settlement authority.

Buyer pays120 cUSDT
Hosted checkout

Hosted checkout keeps the merchant app out of payment infrastructure.

Verify rail2 / 2 blocks
Finality monitor

Operator projection waits for payment truth and finality-safe confirmation.

Release orderrelease ready
Webhook callback

Webhook dispatch tells the merchant backend when payment is finality-safe.

Create projectproject live
Merchant console

Merchant configures checkout, callback URL, and settlement authority.

Buyer pays120 cUSDT
Hosted checkout

Hosted checkout keeps the merchant app out of payment infrastructure.

Verify rail2 / 2 blocks
Finality monitor

Operator projection waits for payment truth and finality-safe confirmation.

Release orderrelease ready
Webhook callback

Webhook dispatch tells the merchant backend when payment is finality-safe.

A developer boundary that stays clean

Merchant products integrate through a compact backend contract. ZamaPay keeps checkout, private settlement, and webhook truth outside the product codebase.

integration contract
Merchant project handoff
One direction of dependency: merchant product to ZamaPay, never the reverse.
Merchant frontend
catalog, buyer journey, order copy
Merchant backend
order id, callback endpoint, fulfillment release
ZamaPay
checkout session, payment truth, finality, encrypted settlement
POST /api/orders/checkout
-> merchant backend
-> ZamaPay /api/projects/{projectId}/checkout-sessions
-> hosted checkout URL
-> webhook release event

Start from the payment project.

Create a project, open hosted checkout, and wire a production webhook endpoint.

Log in