Crypto payments
Accept crypto payments with the right address for every scenario
Give customers a permanent address for repeat top-ups or a one-time address for a single order. Each payment is recorded against the address it was sent to, so your product and your finance team know exactly what it belongs to.
01 Permanent addresses
A lasting address for customers who pay again and again
A permanent address is linked to one customer, user account or internal balance. It does not change, so the customer can save it and send funds whenever they need to top up.
When to use it
- Prepaid balances and account top-ups in SaaS products
- Player deposits in iGaming, where each player has a personal deposit address
- Customers who pay regularly and prefer to reuse one address
- Internal balances that collect funds from several payments
What your team should know
Because one address receives many payments, every payment is credited to the account linked to that address. Paynexis does not pull funds from customers: each payment is sent by the customer from their own wallet.
02 One-time addresses
A fresh address for each individual payment
A one-time address is issued for one specific payment, such as an order, an invoice or a plan purchase. It belongs to that payment alone, which makes matching it to your records direct.
When to use it
- Checkout for orders with a fixed amount
- Invoices for plan purchases or renewals
- Single deposits tied to a cashier session
- Any payment that must match one internal reference
What your team should know
Show the address only in the context of the payment it was issued for, such as the order page or the invoice. For customers who pay repeatedly, a permanent address is usually more convenient.
03 Comparison
Permanent and one-time addresses side by side
You can use both side by side: permanent addresses where customers return to pay, one-time addresses where each payment has its own reference.
| Aspect | Permanent address | One-time address |
|---|---|---|
| Linked to | A customer, an account or an internal balance | One payment, such as an order or an invoice |
| Payments received | Many, over time | One |
| Typical use | Top-ups, deposits, prepaid credits | Checkout, invoices, plan purchases |
| How payments are matched | To the account linked to the address | To the order the address was issued for |
| Customer experience | Saves one address and reuses it | Uses the address shown for this payment |
| Created through | API or dashboard | API or dashboard |
04 Payment flow
What happens from address to recorded payment
The flow is the same for both address types. What changes is what the address is linked to: an account or a single payment.
-
Issue an address
Your system requests an address through the API, or your team creates one in the dashboard, and links it to a customer or an order.
-
Show it to the customer
Display the address on your checkout, invoice or account page, together with the asset and the network the customer should use.
-
Customer sends the payment
The customer pays from their own wallet. Like any blockchain transfer, the payment needs network confirmation before it is final.
-
Payment is recorded
The payment appears against its address in the dashboard and through the API, so your system can credit the order or the balance.
After the payment. Received funds can be converted or used for payouts within Paynexis. How funds are held and made available: funds are credited to your Paynexis balance after the required network confirmations and can be converted, paid out or withdrawn on the schedule agreed during onboarding.
05 Assets and networks
Show the asset and network with every address
A crypto address is only useful together with the asset and the blockchain network it is meant for. Display both clearly wherever customers see the address.
A payment sent in a different asset, or on a different network, may be delayed or may not be recoverable. Clear instructions on your payment page protect your customers and your support team.
Coverage
- Supported assets
- USDT, USDC, BTC, ETH, TRX, LTC
- Supported networks
- Bitcoin, Ethereum (ERC-20), Tron (TRC-20), BNB Smart Chain (BEP-20), Polygon, Litecoin
- Need something else?
- List the assets and networks your customers use in your application. Availability is confirmed during review.
06 API or dashboard
Accept payments from your product or from the dashboard
Through the API
Create addresses inside your checkout, invoices or account pages, store which address belongs to which customer or order, and check payment status from your backend.
The Paynexis APIIn the dashboard
Create addresses manually, look up incoming payments and give customers the details they need, without writing code.
The Paynexis dashboardCan one customer have both a permanent and a one-time address?
Yes. You choose the address type per scenario. A customer could top up a balance through a permanent address and pay a separate invoice through a one-time address.
Does Paynexis charge customers automatically?
No. Crypto payments are sent by the customer from their own wallet. Paynexis does not pull funds or run automatic recurring charges. For repeat payments, a permanent address lets the customer pay again to the same address.
Which cryptocurrencies can customers pay with?
Supported assets: USDT, USDC, BTC, ETH, TRX, LTC. Supported networks: Bitcoin, Ethereum (ERC-20), Tron (TRC-20), BNB Smart Chain (BEP-20), Polygon, Litecoin.
What happens after a payment arrives?
The payment is recorded against its address and becomes visible in the dashboard and through the API. From there you can convert funds or use them for payouts, under the terms of your agreement: funds are credited to your Paynexis balance after the required network confirmations and can be converted, paid out or withdrawn on the schedule agreed during onboarding.
Continue with
Start accepting crypto payments
Tell us which address types and assets you need. We review your business first, then agree terms and help you go live.