Invoices
Create a payment request with an amount, currency, reference and expiration.
Crypto payment gateway
Accept crypto payments with one checkout.
Create invoices, share a hosted payment page and receive signed status updates from one merchant API.
Payment routes appear only after merchant receiving-route and watcher readiness checks.
Hosted checkout
Preview
MerchantYour business
Awaiting invoice
Amount to paySet by invoice
Payment method
Asset and network selected from ready routes
Live payment statusDetection and confirmations update this checkout.
Hosted checkout
Send buyers to a focused payment page with the exact route and live status.
Payment links
Reuse a merchant-owned link to create checkout sessions from one payment setup.
Webhooks
Receive signed status events with persisted delivery attempts and retries.
Choose the payment flow
Start with an invoice or reuse a payment link.
Both flows use the same checkout, payment state and webhook delivery pipeline. The merchant controls the order reference, expiration and callback behavior.
Read the integration guideInvoice
One payment request for a specific order and amount.
Create through the merchant APIPayment link
A reusable entry point that creates a new hosted invoice.
Manage from the merchant dashboardRecurring invoice schedule
Schedule a new hosted invoice for each billing cycle.
Payer-authorized automatic debit is not enabled
How to accept crypto payments
Go from merchant setup to a verified payment flow.
Use the dashboard for setup, keep keys on your server and verify every signed event before delivering the order.
Open the merchant dashboardCreate a merchant
Set the merchant identity and payment defaults before opening a route.
Start in the merchant dashboardGenerate a scoped API key
Create an integration key with only the permissions your server needs.
Reveal once, then store it server-sideCreate and verify
Create an invoice, send the hosted checkout and verify signed webhook events.
Use idempotency for writes and HMAC for eventsAvailable payment routes
Use only the routes ready for your merchant.
Checkout exposes a route only after its receiving address, pricing source and watcher pass the readiness checks.
USDT / TRC20
Stablecoin route available when the merchant receiving route is ready
LTC / LTC
Native Litecoin receiving route with confirmation tracking
BTC / BTC
Bitcoin on-chain receiving route with confirmation tracking
Fees and totals
Show the amount before anyone pays.
The hosted checkout exposes the quote returned for that invoice. Rules, route and payment mode remain merchant-specific.
Gateway fee
The amount is calculated from the fee rule configured for the merchant and invoice. ZemiaxPay does not publish a universal percentage that may not apply to your account.
Exact payer total
Hosted crypto invoices default to a net target: the checkout shows the exact amount to send, the gateway fee and the merchant amount before payment.
Network fee
The sending wallet pays the blockchain network fee. ZemiaxPay keeps that cost separate and never guesses it inside the merchant amount.
Gateway controls
Make every payment state actionable.
Merchant operations stay tied to records returned by the payment lifecycle instead of invented dashboard metrics.
Payment status management
Track pending, confirmed, wrong-amount, overpayment and expired states from the invoice and signed event history.
Flexible fee rules
Apply merchant fee rules while keeping the sender network fee separate from the merchant net amount.
Reconciliation-ready records
Keep the invoice, payment, transaction hash, confirmations and ledger entry connected for review.
Merchant API
One request creates the payment flow.
Authenticate with a scoped key, use an idempotency key for writes and verify every webhook before fulfilment.
Create invoice
POST
/api/v1/crypto/invoicesAUTH
x-api-key: merchant_keySAFE
Idempotency-Key: unique_request_keyEVENT
Verify HMAC before fulfilmentCreate invoices and read payment state from your server with scoped credentials.
Use the first-party server-side client source included in this repository.
Verify timestamped delivery signatures before fulfilling an order.
Security
Protect access, payment state and delivery.
Security controls are part of the payment flow, not optional dashboard decoration.
Scoped access
Merchant keys are hashed at rest, revealed once and limited by explicit scopes.
Verified events
Webhook signatures, timestamps and delivery identifiers support replay-safe fulfilment.
Auditable payment state
Invoice, payment, confirmation and ledger records remain separate and traceable.
FAQ
Before accepting your first payment.
Availability depends on the receiving route, pricing source, watcher and confirmation policy configured for each merchant.
Does the buyer need a ZemiaxPay account?
No. A buyer can open the hosted checkout and pay the route assigned to the invoice.
Which cryptocurrencies can a merchant accept?
The catalog covers multiple assets and networks. A route appears at checkout only after that merchant has a ready receiving route, pricing source and watcher or provider.
Where do received funds go?
The destination depends on the configured receiving route. ZemiaxPay can monitor an external receiving address while recording the payment and ledger facts.
Where are received funds held?
ZemiaxPay monitors external receiving addresses and records payment facts. It never stores signing keys or sends funds from the VPS.
Merchant checkout