Frequently asked questions

Payzuno is a cryptocurrency payment infrastructure platform. It lets online businesses accept crypto and stablecoin payments, offer card-to-crypto deposits, and settle funds to a wallet the business controls — all through one REST API and a white-label hosted checkout, without running blockchain nodes or managing wallets in-house.

Accepting crypto directly means running nodes, generating an address per order, watching several blockchains for confirmations, pricing volatile assets, screening for compliance, and paying funds back out — each a project on its own. Payzuno packages all of it behind one API and hosted checkout, so a business can accept digital-asset payments in days instead of months.

Online businesses that want to accept crypto or stablecoins: iGaming operators (casinos and sportsbooks), e-commerce stores, SaaS and software vendors, digital-goods sellers, marketplaces, and any merchant treated as high-risk or charged high cross-border fees by card acquirers.

Neither. Payzuno is a payment service provider built around minimized custody. It moves funds from your customers to you and holds balances only briefly before settling them to your own wallet. It does not offer trading, and it never lends, stakes, or reinvests merchant balances.

A card gateway routes an authorization through card networks and banks, and payments can be charged back for months. Payzuno settles on public blockchains: once a payment confirms it is final, there are no chargebacks and no rolling reserve, cross-border works the same as domestic, and settlement is same-day to a wallet you control.

Ether (ETH) and the major ERC-20 stablecoins USDT and USDC are live on Ethereum mainnet, and USDC is supported on Polygon. Any other ERC-20 token can be enabled per deployment by supplying its contract address.

Ethereum mainnet and Polygon are live. Bitcoin and Tron rails exist in the codebase and are enabled per deployment. Because assets are configured per deployment, the exact set available to you is confirmed during onboarding.

Yes. Stablecoins are the most common way merchants use Payzuno because they remove day-to-day price volatility: a customer pays USDC or USDT, and your balance stays denominated in a dollar-pegged asset until you settle it out.

Yes. Any ERC-20 can be registered per deployment with its contract address and decimals, after which invoices can be priced and paid in it and the deposit watcher credits it automatically.

You decide which assets to enable. On the hosted checkout the customer can pick from the assets you have turned on; the page then shows the exact amount, asset, and network to send.

Only briefly, and never for our own use. Each deposit lands at an address generated for that single invoice, and your balance settles out to a wallet you control on your schedule. Signing keys live in dedicated key hardware (HSM/KMS), not on application servers, and every outbound transfer is checked against your policy limits before it can be signed.

You configure a settlement wallet and schedule. Payzuno sweeps confirmed deposits and credits your merchant balance net of fees, then settles that balance on-chain to your wallet — typically same day (T+0) — so funds spend as little time as possible with the provider.

A crypto payment usually confirms within minutes, and withdrawal to your own wallet is available the same day. There is no multi-day banking clearing cycle and no weekend gap — blockchains settle continuously.

Yes. Payzuno supports single and batch payouts on-chain — for example paying iGaming winners or marketplace sellers. Payouts above the limits you set can require approval, balances are tracked per tenant, and a double-entry ledger backs every movement.

Both are handled explicitly. An underpayment leaves the invoice short and is surfaced to you rather than silently marked paid. An overpayment is recorded against the merchant so it can be refunded or credited. Payments arriving after an invoice expires are held, not lost.

No. An on-chain payment is final once confirmed — there is no issuer to reverse it and no rolling reserve held against future disputes. That is a property of the blockchain, not something Payzuno adds. The trade-off is that funds sent to a wrong address cannot be pulled back, which is why the checkout shows the exact amount, asset, and network before the buyer sends.

Pricing is agreed per merchant and depends on volume and asset mix, with separate rates for deposits and withdrawals. Blockchain network fees (gas) apply to on-chain transfers on top of that. We quote against your actual flow rather than a headline rate.

No. Because on-chain settlement is final there are no chargebacks, so there are no chargeback fees and no rolling reserve withheld from your revenue — a structural difference from card processing.

Each invoice is priced from the median of four independent market feeds. If fewer than two agree, the prices diverge beyond a set tolerance, or the data goes stale, Payzuno refuses to issue a quote rather than guess. You can always check the quoted rate against the public market.

Network fees apply to on-chain transfers such as sweeps and payouts. They are treated as a pass-through cost of moving funds and are accounted for transparently rather than hidden in the exchange rate.

No. You can price invoices in fiat and accept stablecoins, keeping your balance dollar-denominated, then settle to your wallet. You never have to pre-fund or speculate on crypto to accept it.

Call the API with the fiat amount and the asset you want to be paid in, show the returned hosted checkout page or QR code to your buyer, and handle the signed webhook when the payment confirms. A full OpenAPI specification is published, and you can run the entire flow on a testnet before touching real money.

Yes — a clean, idempotent REST API. It uses bearer API keys, mandatory idempotency keys on writes, HMAC-signed webhooks, stable machine-readable error codes, and tenant-scoped resources. The OpenAPI spec is available at /openapi.yaml.

Both. You can redirect customers to a white-label hosted checkout (QR, address, amount, network, and a countdown) or render your own checkout from the API responses. The hosted page falls back to Payzuno branding if a merchant sets none.

Yes. You can create keys and run the full deposit, confirmation, webhook, and payout flow against a testnet, then switch to mainnet keys when you are ready. Testing on a sandbox first is the recommended path.

The API is plain REST and works from any language with an HTTP client. A TypeScript SDK is available, and the OpenAPI spec lets you generate a typed client for most languages.

Write endpoints require an Idempotency-Key. Replaying the same key returns the original result instead of creating a second invoice or payout, so a network retry can never double-charge or double-pay.

Payzuno POSTs a signed event to your endpoint at each step — payment detected, confirmed, credited, payout sent. Each request carries an HMAC signature over the raw body and a timestamp; you verify the signature with your webhook secret before acting on it.

Compute HMAC-SHA256 over "{timestamp}.{raw body}" with your webhook signing secret and compare it, in constant time, to the value in the signature header. Reject anything outside a small timestamp tolerance to stop replays. Crediting should always be driven by the on-chain confirmation, never by a webhook alone.

Webhook delivery retries with backoff, so a brief outage does not lose events. You can also poll the payment or order status endpoint to reconcile, which is the authoritative record.

Signing keys are held in dedicated key hardware (HSM/KMS) rather than on application servers, every outbound transfer is checked against per-transfer and per-merchant policy limits before signing, balances are reconciled by a double-entry ledger, and administrative actions are written to a hash-chained audit trail.

Yes. Deposit and withdrawal addresses are screened against a Know-Your-Transaction provider, and screening fails closed — if it is unavailable, the transfer does not proceed rather than slipping through unchecked.

No. Payzuno gives you the compliance controls and the evidence trail — KYT screening, policy limits, responsible-gambling gates, and an audit log — but customer KYC obligations and any licensing or registration requirements remain yours and vary by jurisdiction.

Every administrative and financial action is recorded, and administrative actions are written to a hash-chained audit trail so tampering is detectable. Combined with the double-entry ledger, this gives you a complete, verifiable record of money movement.

Player-level controls let operators block or limit specific players; a blocked player’s deposit attempt is refused before an address is issued and is surfaced through a webhook, so the operator keeps a record.

Card-to-crypto lets a customer pay with a card or a local method such as UPI while you receive crypto. A regulated on-ramp partner collects the fiat and forwards a stablecoin to the deposit address Payzuno generated for the order; you only ever handle crypto.

Yes, where an on-ramp partner supports it. For example, a UPI on-ramp can settle USDC on Polygon to your deposit address. Availability and minimums vary by partner and country and are confirmed per deployment.

No. The on-ramp handles the card or bank rails and delivers crypto on-chain; Payzuno detects that deposit and credits your merchant balance. Your integration and reconciliation stay entirely in crypto.

No — crediting is always driven by detecting the funds on-chain, never by a callback alone. A callback is treated as a hint; the on-chain confirmation is the source of truth.

Yes — iGaming is a core use case. It covers the whole money flow: fast crypto deposits, per-operator pricing, player-level responsible-gambling controls, and batch on-chain payouts for winnings, with a ledger and audit trail behind it all.

Yes. Stablecoin checkout shows the exact amount, asset, and network to the buyer, underpayment and overpayment are handled explicitly, refunds are supported, and clean signed webhooks integrate with your order-management system.

Any business that sells across borders or is treated as high-risk by card acquirers: affiliate and ad networks, software and SaaS, digital goods and gaming, travel and bookings, forex and trading platforms, and freelance marketplaces.

Yes. On-chain settlement works the same domestically and internationally, with no correspondent-bank fees or extra cross-border card charges, and it clears on weekends and holidays.

Talk to us to set up a merchant account and API keys, integrate against a testnet, then switch to mainnet when you are ready. A basic integration — create invoice, show checkout, handle the confirmation webhook — is usually a matter of days.

Payzuno is infrastructure, not a licence. Whether you can accept crypto payments depends on your own jurisdiction and business type. Availability of specific assets, networks, and fiat on-ramps also varies by region and is confirmed during onboarding.

Payzuno is deployed as a managed gateway with per-merchant configuration. Assets, chains, on-ramps, fees, and limits are configured for your deployment rather than being one-size-fits-all.

Use the chat widget on any page or message the team on Telegram at t.me/Payzuno_io. We usually reply within a few minutes.