01
Checkout and invoices
Request a one-time address for each order or invoice and show it on your payment page.
Map your scenarios
Decide which payments use permanent or one-time addresses, where conversion fits and where payouts start.
Integrations
Work through the API, the dashboard or both
Paynexis gives developers an API to build crypto payments into your product, and gives operations and finance teams a dashboard to run them day to day.
01 The API
Crypto flows inside your own product
Use the API when payments and payouts should happen inside your checkout, your account pages or your back office, without manual steps.
02
Account balances and deposits
Link a permanent address to each customer or player account so repeat top-ups are attributed automatically.
03
Conversion
Request conversions between supported assets from your treasury or payout logic.
04
Payouts and mass payouts
Send single payouts when requests are approved, or submit many transfers as one batch.
Developer resources
- API documentation
- Shared with your team during onboarding.
- Access
- Integration access is provided after your application has been reviewed and commercial terms are agreed.
02 Integration path
How an integration usually goes
Four stages, from deciding which flows you need to handing daily work to your team.
-
-
Get access
Once your application is accepted and terms are agreed, you receive integration access and documentation.
-
Build and test
Connect your backend, store which address belongs to which customer or order, and test each flow end to end.
-
Go live
Open the flows to customers and hand day-to-day operations to the dashboard.
03 The dashboard
Day-to-day operations without code
The dashboard is where operations and finance teams work with Paynexis directly: no development needed.
- Look up incoming payments by address or reference
- Create permanent and one-time addresses manually
- Convert balances between supported assets
- Send single payouts and prepare mass payouts
Some businesses use only the dashboard, for example when crypto volumes are handled by a small finance team.
04 Who uses what
A typical split of work
Every business divides this differently. This is a common starting point.
| Team | Works through | Typical tasks |
|---|---|---|
| Product and engineering | API | Address issuing at checkout and in accounts, payment status in the product, automated payouts |
| Finance | Dashboard, sometimes API | Reviewing received funds, conversions, payout runs, reconciliation |
| Operations and support | Dashboard | Looking up payments for customers, manual addresses and payouts |
| Compliance and management | Application and review | KYB application, ownership details, agreeing commercial terms |
05 Security basics
Integrate safely from day one
Credentials stay on your server
Call the API from your backend only. API credentials must never appear in a browser, a mobile app, a repository or a shared document.
No seed phrases, no private keys
Paynexis never asks for wallet seed phrases, private keys or passwords, and the application form does not collect them.
Access on a need-to-know basis
Share dashboard access only with the people who need it for their work, and review that list when roles change.
Verify before you pay out
Validate recipient addresses, assets and networks in your system before a payout request is sent.
Do I have to use the API?
No. You can work entirely in the dashboard. The API is for businesses that want payments and payouts inside their own product.
When do we get API access?
After your application has been reviewed and commercial terms are agreed.
Where is the API documentation?
API documentation is shared with your team during onboarding, after your application has been reviewed.
Can the API and the dashboard be used together?
Yes. A common setup is to automate the main flows through the API and use the dashboard for reviews, manual actions and reconciliation.
Plan your integration with us
Describe the flows you want to build in the application. After review and terms, your developers receive access and documentation.