# Static address

> A permanent deposit address for one customer and one asset. How CryptoLike credits every transfer to it and how it differs from a one-off payment.

Source: https://cryptolike.net/glossary/static-address
Updated: 2026-09-25

A permanent deposit address issued to one customer for one asset, with no fixed amount and no deadline, where every incoming transfer is credited separately.

## How it works in CryptoLike

CryptoLike creates a static address with `POST /v1/addresses`, given a `coin_id`, your `customer_id` and an optional `label`. Every transfer to it is credited to your balance after the asset's [confirmations](https://cryptolike.net/glossary/confirmations). You receive `deposit.pending` when a transfer is seen and `deposit.confirmed` when it is credited, with the platform fee in `deposit.fee` and the credited sum in `deposit.net_amount`.

There is one active address per asset and customer: a second request for the same pair is `409 conflict`. To issue a new address, archive the old one in the cabinet — the archived address keeps receiving. `GET /v1/addresses/{id}` returns the deposit history with `total_received`, `tx_count` and `last_deposit_at`. A transfer rolled back by a chain reorganisation sends `deposit.reverted`; a transfer held for compliance review sends `deposit.on_hold`.

## Static address or payment?

CryptoLike offers two ways to receive funds: a one-off [payment (invoice)](https://cryptolike.net/glossary/crypto-invoice) for an order, and a static address for balances, top-ups and recurring funding. Both are created with one API call and report through signed [webhooks](https://cryptolike.net/glossary/webhook); they differ in amount, deadline and events:

| Aspect | Payment (invoice) | Static address |
|---|---|---|
| Amount | fixed, `payer_amount` | whatever the customer sends |
| Time limit | `ttl_expires_at` | none |
| Statuses | `new`, `pending`, `paid`, `underpaid`, `expired`, `cancelled` | per deposit: `pending`, `confirmed`, `reverted`; `on_hold`, then `confirmed`, `returned` or `rejected` after a compliance review |
| Events | `invoice.*` | `deposit.*` |

## Example

A CryptoLike static address is created once per customer and asset: store the returned `address` in your user profile and show it to the customer every time they top up. `coin_id` comes from `GET /v1/currencies`; the request body is sent to `POST /v1/addresses` with a key that has the `create_address` permission:

```json
{
  "coin_id": "6f1c2a3e-8d4b-4c5a-9e7f-0a1b2c3d4e5f",
  "customer_id": "user-8812",
  "label": "Top-up wallet"
}
```

Static addresses are the base of [crypto top-ups and deposits](https://cryptolike.net/use-cases/deposits): one address per user, credited on every transfer.