---
title: "Create Customer Wallets"
method: POST
path: "/v2/customers/{customer_id}/wallets"
tags: ["Customers"]
---

# Create Customer Wallets

`POST /v2/customers/{customer_id}/wallets`

Provisions one or more crypto wallets for a customer across supported chains and tokens.

## Path parameters

- `customer_id` string, required

## Request body

- object
  - `wallets` object[], required — Wallets to provision, one entry per rail.
    - `rail` string, required — Blockchain network to provision the wallet(s) on.
    - `currency` string[], required — Token(s) to provision a wallet for on this rail.

## Response `200`

Wallet creation request accepted for processing. Note the nested `data`: the outer envelope wraps a `message` plus the inner `data` array of wallets being provisioned.

- object
  - `data` object
    - `message` string
    - `data` CustomerWallet[]
      - `id` string, uuid — Unique wallet identifier.
      - `status` 'PENDING' | 'ACTIVE' | 'INACTIVE' — Wallet provisioning status. Wallets start PENDING and move to ACTIVE (or INACTIVE) asynchronously once the wallet address has been issued; creation is not synchronous.
      - `currency` string — Token held in this wallet.
      - `rail` string — Blockchain network for this wallet.
      - `address` string, nullable — On-chain wallet address. Null until the wallet is provisioned.
      - `balance` number — Current wallet balance.

## Other responses

- `401` — Authentication failed due to invalid credentials
- `409` — One or more of the requested wallets already exist for this customer.
- `422` — Failed due to a formatting error.

---

[API](https://skmtc.net/fin/apis/fin-com-api.md) · [All operations](https://skmtc.net/fin/apis/fin-com-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fin/fin-com-api/versions/6e69503ee7b8/schema)
