General Information
Getting Started
Before you can use the Payment Chief API, you must:
A registered account
Configure security settings in the Dashboard (upload an RSA public key and copy an API key)
Enable required networks and tokens in the Project Settings
Create master wallets for the networks you plan to use
RSA Key Setup (Required)
To securely manage sensitive data, each project must have an RSA public key configured.
Mandatory Step: Before accessing any private keys or creating master/transit wallets, you must upload your public RSA key in the Project Settings → RSA Key section of the Dashboard.
Without an RSA public key configured for the project, the platform cannot encrypt or return any sensitive wallet data.
If you are not familiar with RSA key generation, please refer to the dedicated guide here, which provides detailed instructions for creating an RSA key pair.
Enable Networks & Tokens (Required)
After the RSA key is uploaded, you must explicitly enable the blockchains and tokens that will be used to accept payments.
By default, all networks and tokens are disabled for a new project.
To enable them, open Project Settings → Networks in the Dashboard and activate:
required blockchains
required tokens for each blockchain
Wallets Setup (Master Wallet Required)
Once the required networks and tokens are enabled, you can create a master wallet for the target blockchain network.
A master wallet is required to generate transit addresses and accept payments within the selected blockchain family.
You can create a master wallet in two ways:
Via Dashboard: Dashboard → Wallets
Via API: using the corresponding master wallet creation endpoint
Test Environment Recommendation
During integration, it is strongly recommended to use the test environment first.
The test environment uses test networks and test assets, allowing you to safely validate:
request signing and authentication
network and token configuration
wallet creation and callbacks
full payment flow
More detailed information about the test environment, available networks, and limitations can be found here
After successful testing, you can switch to production networks.
API Authentication & Request Signing
Each API request must include the following authentication parameters in request headers:
Merchant ID — identifies your merchant account
Signature — a cryptographic signature generated using your API key
The signature is used to verify the authenticity and integrity of each request.
Important
The API key must be kept strictly confidential and should never be shared or exposed on the client side.
Detailed instructions on how to generate the request signature can be found here.
Base URL
All API requests are sent to the following base URL:
https://api-processing.crypto-chief.com
Last updated