Invoice
One payment request for a specific order and amount.
Create through the merchant APICreate a payment request, share its link and follow the payment from your merchant dashboard.
Customers only see payment methods that pass the checks for your business.
Request one payment for an order or reuse a link for your products and services. Follow received amounts and payment progress in your dashboard.
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 dashboardSchedule a new hosted invoice for each billing cycle.
Payer-authorized automatic debit is not enabledSet up your business, choose how to collect and follow your payments. You can start with a payment link or connect your website through the API.
Open the merchant dashboardUse your merchant account or accept a team invitation, then review your business details.
Start in the merchant dashboardSet the amount and reference, then share the payment link.
Use the dashboard or your integrationReview received amounts, confirmations and payment history.
Verify payment confirmation before delivering an orderThese are the currencies and networks the gateway supports. Available payment methods depend on your business configuration and are checked for each payment request.
BTC · LIGHTNING
LTC
TRC20 · ERC20 · BEP20 · POLYGON · ARBITRUM · AVALANCHE · SOLANA
ERC20 · POLYGON · ARBITRUM · AVALANCHE · BASE · SOLANA
SOLANA
ERC20
BEP20
TRC20
Review the amount and any applicable fees for each payment request before sharing it. Your customer sees the total before paying.
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 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.
Manage account access and verify payment confirmation before delivering an order.
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 depends on the receiving route, pricing source, watcher and confirmation policy 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 receiving route, pricing source and watcher or provider.
The destination depends on the configured receiving route. ZemiaxPay can monitor an external receiving address while recording the payment and ledger facts.
ZemiaxPay monitors external receiving addresses and records payment facts. It never stores signing keys or sends funds from the VPS.