Accept Cryptocurrency Payments. Simplify Global Commerce.
mzapayments gives merchants invoices, payment links, and a modern API to accept BTC, ETH, stablecoins, and more—with sandbox testing built in.
Supported cryptocurrencies
Configurable assets with explicit network labels for accurate checkout instructions.
- BTCBitcoinBitcoin Mainnet
- ETHEthereumEthereum Mainnet
- USDTTether USDTRON (TRC-20) · Ethereum (ERC-20) · BNB Smart Chain (BEP-20)
- LTCLitecoinLitecoin Mainnet
- SOLSolanaSolana Mainnet
How it works
- 01
Create your account
Register, verify your email, and open a sandbox workspace with API keys ready to use.
- 02
Integrate checkout
Create invoices or payment links, or call the Payment API from your backend.
- 03
Confirm via webhooks
Listen for signed webhook events and reconcile orders when payments reach confirmed status.
Built for modern checkout teams
Compose the products you need—from API-first flows to shareable links.
Create and track crypto payments programmatically
Learn moreBill with clear amounts and lifecycle states
Learn moreShareable checkout without custom code
Learn moreInvoice-backed payment experience
Learn moreOperate payments without spreadsheets
Learn moreReal-time payment notifications
Learn moreA few lines to your first invoice
RESTful JSON endpoints with predictable errors. Swap sandbox keys when you are ready for live traffic.
Read the API overviewcurl -X POST "$BASE_URL/api/v1/invoices" \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"orderId": "order_1042",
"amountDue": "149.00",
"currency": "USD",
"description": "Annual plan"
}'Use cases
Transparent pricing
No hidden setup fees on sandbox. Live processing rates depend on volume and asset mix—see the pricing page for the current fee schedule and how estimates work.
View pricingSecurity grounded in what we ship
We describe capabilities that exist in the platform today—not unverified certifications.
Hashed credentials
Passwords are stored using strong one-way hashing; API secrets are never shown again after creation.
Webhook verification
Configure per-endpoint secrets and validate signatures before fulfilling orders.
Rate limiting
Sensitive routes—including contact and auth—use rate limits to reduce abuse.
Security headers
Responses include CSP, frame denial, and related headers via application middleware.
Audit trails
Dashboard actions can be traced through audit logging for configuration changes.
Frequently asked questions
Which cryptocurrencies can I accept?
mzapayments supports BTC, ETH, USDT (TRC-20 and ERC-20), LTC, and SOL in sandbox and live configurations. See the currencies page for network details.
Is there a sandbox?
Yes. API keys are labeled SANDBOX or LIVE. Use sandbox keys with the simulation tools to test webhooks without moving real funds.
How do I authenticate API requests?
Send your secret API key in the Authorization header as a Bearer token. Rotate keys from the merchant dashboard.
Are webhooks signed?
Outbound webhook deliveries use a shared secret configured on each endpoint so you can verify authenticity before updating orders.
When can I request payouts?
Payout requests are available after your account is configured and verified for live settlement. Contact support to enable destinations.
Start accepting crypto payments today
Create a free account, test in sandbox, and go live when your reconciliation and webhook handlers are ready.