---
title: "Create a new customer"
method: POST
path: "/payments/br/customers/"
tags: ["Customers (Brazil)"]
---

# Create a new customer

`POST /payments/br/customers/`

Create a new customer to send or request funds.

## Headers

- `X-Belvo-API-Resource-Version` 'Payments-BR.V2'

## Request body

- union
  - CreateCustomerV2
    - `identifier` string, required — The CPF (11 digits) or CNPJ (14 digits) of the customer.
    - `name` string, required — The full name or business name of the customer.
    - `external_id` string, uuid — An additional unique identifier for the resource for internal purposes. {% admonition type="success" name="Highly Recommended" %} We recommend using this field to store your own unique identifier for each resource (customer, bank account, payment intent, or enrollment). This can be useful for tracking the resource in your system and for debugging purposes. {% /admonition %}
  - CreateCustomerOfpi — Create a customer for Payment Initiation
    - `identifier` string, required — The customer's CPF or CNPJ number.
    - `name` string — The full name of the customer you want to create.
    - `external_id` string, uuid — An additional unique identifier for the resource for internal purposes. {% admonition type="success" name="Highly Recommended" %} We recommend using this field to store your own unique identifier for each resource (customer, bank account, payment intent, or enrollment). This can be useful for tracking the resource in your system and for debugging purposes. {% /admonition %}
    - `email` string — The customer's email address.
    - `phone` string, nullable — The customer's phone number.
    - `address` string, nullable — The customer's physical address.

## Response `201`

OK (Created)

- union
  - CustomerV2
    - `id` string, uuid, required — Belvo's unique identifier for the current item.
    - `created_at` string, date-time, required — The ISO-8601 timestamp of when the data point was created in Belvo's database.
    - `updated_at` string, date-time, required — The ISO-8601 timestamp of when the data point was updated in Belvo's database.
    - `name` string, required — The full name or business name of the customer.
    - `identifier` string, required — The CPF (11 digits) or CNPJ (14 digits) of the customer.
    - `external_id` string, uuid — An additional unique identifier for the resource for internal purposes. {% admonition type="success" name="Highly Recommended" %} We recommend using this field to store your own unique identifier for each resource (customer, bank account, payment intent, or enrollment). This can be useful for tracking the resource in your system and for debugging purposes. {% /admonition %}
  - CustomerOfpi
    - `id` string, uuid, required — Belvo's unique identifier for the current item.
    - `created_at` string, date-time, required — The ISO-8601 timestamp of when the data point was created in Belvo's database.
    - `created_by` string, uuid, required — The unique ID for the user that created this item.
    - `customer_type` 'INDIVIDUAL' | 'BUSINESS', required — The type of customer. Can be either: - `INDIVIDUAL` - `BUSINESS` (Brazil OFPI only)
    - `name` string, nullable, required — The full name of the customer.
    - `external_id` string, uuid — An additional unique identifier for the resource for internal purposes. {% admonition type="success" name="Highly Recommended" %} We recommend using this field to store your own unique identifier for each resource (customer, bank account, payment intent, or enrollment). This can be useful for tracking the resource in your system and for debugging purposes. {% /admonition %}
    - `country` 'BRA' | 'null', nullable, required — The customer's country of residence. - BRA (🇧🇷 Brazil)
    - `email` string, nullable, required — The customer's email address.
    - `identifier` string, required — The document number of the customer's ID (depending on the `identifier_type`).
    - `identifier_type` 'CPF' | 'CNPJ', required — The customer's ID document type. For Brazil, this can be either: - `CPF` (when `customer_type` is `INDIVIDUAL`) - `CNPJ` (when `customer_type` is `BUSINESS`)
    - `address` string, nullable — The customers physical address.
    - `phone` string, nullable — The customer's phone number.

## Other responses

- `400` — Validation Error
- `401` — Unauthorized
- `403` — Access to Belvo API denied
- `404` — Not Found Error
- `408` — Request Timeout
- `500` — Unexpected Error

---

[API](https://skmtc.net/belvo/apis/belvo-api-docs.md) · [All operations](https://skmtc.net/belvo/apis/belvo-api-docs/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/belvo/belvo-api-docs/versions/3423c786ece5/schema)