# General Information

### **Getting Started**

Before you can use the **Payment Chief API**, you must:

1. **A registered account**
2. **Enable required networks and tokens** in the Project Settings
3. **Create master wallets** for the networks you plan to use

**Enable Networks & Tokens (Required)**

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/static 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](https://docs.jigitbit.com/managing-wallets/generate-wallet)

**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](https://docs.jigitbit.com/getting-started/test-environment)

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.

{% 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.jigitbit.com/getting-started/signing-requests).

**Base URL**

All API requests are sent to the following base URL:

{% hint style="info" %}
`https://api.jigitbit.com`
{% endhint %}