Invoices
Create a payment request with an amount, currency, reference and expiration.
Create invoices, share a hosted payment page and receive signed status updates from one merchant API.
Payment routes appear only after merchant wallet and watcher readiness checks.
Create a payment request with an amount, currency, reference and expiration.
Send buyers to a focused payment page with the exact route and live status.
Reuse a merchant-owned link to create checkout sessions from one payment setup.
Receive signed status events with persisted delivery attempts and retries.
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 guideOne payment request for a specific order and amount.
Create through the merchant APIA reusable entry point that creates a new hosted invoice.
Manage from the merchant dashboardA merchant-owned address assignment for supported wallet flows.
Available only with configured inventoryCatalog coverage is not a live-rail claim. Checkout exposes only routes that pass wallet, pricing and detection readiness.
BTC on-chain and provider-gated Lightning
Native LTC settlement route
USDT and USDC on configured networks
Ethereum, BNB Smart Chain, Polygon and compatible adapters
TRX and TRC20 token routes
SOL and supported token routes
The hosted checkout exposes the quote returned for that invoice. Rules, route and payment mode remain merchant-specific.
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.
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.
The sending wallet pays the blockchain network fee. ZemiaxPay keeps that cost separate and never guesses it inside the merchant amount.
Authenticate with a scoped key, use an idempotency key for writes and verify every webhook before fulfilment.
/api/v1/crypto/invoicesx-api-key: merchant_keyIdempotency-Key: unique_request_keyVerify HMAC before fulfilmentSecurity controls are part of the payment flow, not optional dashboard decoration.
Merchant keys are hashed at rest, revealed once and limited by explicit scopes.
Webhook signatures, timestamps and delivery identifiers support replay-safe fulfilment.
Invoice, payment, confirmation and ledger records remain separate and traceable.
Availability, custody and payout authority depend on the routes and providers configured for each merchant.
No. A buyer can open the hosted checkout and pay the route assigned to the invoice.
The catalog covers multiple assets and networks. A route appears at checkout only after that merchant has a ready wallet, pricing source and watcher or provider.
The destination depends on the configured receiving route. ZemiaxPay can monitor an external wallet while recording the payment and ledger facts.
Payout planning and approvals are available, but broadcast remains disabled until a real signer or provider is configured and verified.