> For the complete documentation index, see [llms.txt](https://docs-processing.crypto-chief.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-processing.crypto-chief.com/getting-started/readme.md).

# General Information

#### Getting Started

1. Register an account and obtain your merchant ID and API key from the Dashboard.
2. Enable the networks and assets your project will use.
3. Add a master wallet for each blockchain family. CryptoChief can generate the wallet, or your project can register an address and provide its own signer. [Wallet roles and signing](https://docs-processing.crypto-chief.com/managing-wallets/overview.md)

#### RSA key for generated wallets

To generate internal wallets, upload your RSA public key under **Project Settings → RSA Key**. CryptoChief uses it to encrypt exported wallet keys. External wallets use a proof of control signed by the existing wallet key. [RSA key setup](https://docs-processing.crypto-chief.com/getting-started/generating-an-rsa-key-pair.md) · [External wallet registration](https://docs-processing.crypto-chief.com/managing-wallets/external-wallets.md)

#### Enable Networks & Tokens (Required)

Enable the blockchains and tokens you will accept in Project Settings.

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

Test networks are enabled the same way and live alongside the real ones — the list shows every supported network and can be filtered to test networks only. Whether test networks are offered to your project at all is set by the platform operator.

#### 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/static addresses and accept payments within the selected blockchain family.

For an internal master, open **Dashboard → Wallets** or call the wallet generation endpoint with `wallet_type` set to `master`. [Generate wallet](https://docs-processing.crypto-chief.com/managing-wallets/generate-wallet.md)

For an external master, request a registration challenge, sign it with the wallet key and submit the proof. Your signer will receive an HTTPS request for each signature CryptoChief needs. [Register and use an external wallet](https://docs-processing.crypto-chief.com/managing-wallets/external-wallets.md)

#### Test Networks (Recommended First Step)

During integration, work on **test networks** first. They run the same code path as production — the same signing, the same wallet creation, the same order lifecycle and callbacks — so what you validate there is what you get with real money:

* request signing and authentication
* network and token configuration
* wallet creation and callbacks
* full payment flow

There is **no project-wide test mode to switch on**. A project uses real chains and test chains at the same time, and the network on the order decides which one it belongs to: name a concrete network (`ETH_SEPOLIA`, `TRON_NILE`, …) and you get that network. Where the platform picks the asset for you — `fiat` mode, or `ANY_NETWORK` — send `environment: "testnet"` (or `"mainnet"`) to constrain the choice, or leave it out and your project's default applies.

Going live is therefore not a switch: point your orders at mainnet networks and keep the same API key, signing and webhooks.

See [Test Environment](https://docs-processing.crypto-chief.com/getting-started/test-environment.md) for the full walkthrough, including the faucet, and [Environments: mainnet and testnet](https://docs-processing.crypto-chief.com/general/environments.md) for the exact rules.

#### API Authentication & Request Signing

Each API request must include the following **request headers**:

* **Merchant** — your Merchant ID
* **X-CC-Timestamp**, **X-CC-Nonce**, **X-CC-Signature** — an HMAC-SHA256 signature of the request made with your **API key**

The signature is used to verify the authenticity and integrity of each request.

{% hint style="warning" %}
**Important**

The API key must be kept strictly confidential and should never be shared or exposed on the client side.
{% endhint %}

Detailed instructions on how to generate the request signature can be found [**here**](https://docs-processing.crypto-chief.com/getting-started/signing-requests.md).

#### Base URL

All API requests are sent to the following base URL:

{% hint style="info" %}
`https://api-processing.crypto-chief.com`
{% endhint %}
