Create a Profile

Creates a profile that represents a transaction participant, such as the client’s own entity or an external counterparty. A profile is transaction-direction agnostic. The same profile can support both send-to and receive-from transaction directions. Profiles are a prerequisite for all digital asset operations, including blockchain address whitelisting and payout execution.

Please ensure that the correct information is submitted.

flowchart LR

  S((Start)):::start --> A[👤 1. Create a Profile]:::highlight --> B[🛡️ 2. Whitelist Blockchain Address]:::step --> C[💸 3. Create Payout]:::step

  

  classDef step fill:#C7E5DE,stroke:#5FA8A0,color:#1F3C3A,stroke-width:2px,rx:14,ry:14;

  classDef highlight fill:#A8DCD1,stroke:#2F7F77,color:#0F2F2D,stroke-width:3px,rx:16,ry:16;

  classDef start fill:#FFFFFF,stroke:#2F7F77,color:#0F2F2D,stroke-width:2px;

  

  linkStyle 0 stroke:#2F7F77,stroke-width:3px;

  linkStyle 1 stroke:#2F7F77,stroke-width:3px;

  linkStyle 2 stroke:#2F7F77,stroke-width:3px;
📘

Create a recipient profile

Endpoint

https://www.bankingcircleconnect.com/api/v1/digital-assets/profiles

Purpose

Creates a profile representing a transaction counterparty.

Usage

Use this endpoint to define a counterparty before performing any transaction. Create one profile per counterparty and ensure all information provided is accurate and complete, as profiles are reused across different transaction flows.



Choose recipient type (kind)

When creating a profile, you must specify the type of entity the profile represents. This is done using the kind field, which determines how the profile is structured and used in subsequent transactions

KindDescription
selfRepresents your organisation (the API client).

Use when:
Sending funds from your own account
Future enhancement: Receiving funds from your own external wallet
Managing your own treasury
external_corporateRepresents an external business entity.

Use when:
Sending payouts to merchants or partners
Future enhancement: Receiving funds from merchants or partners
Managing institutional clients.
external_individualRepresents a natural person receiving or sending funds.

Use when:
Sending payouts to individuals
Future enhancement: Receiving funds from individuals
Managing retail recipients.

Request Body

To create a profile for your organisation:

FieldTypeRequiredDescription
kindstringYesType of profile selected: Self
labelstringYesGive a name to this profile
companyNumberstringYesThe company number of the API client (the client of BC), can be found in the client portal

To create a profile for an external business entity:

FieldTypeRequiredDescription
kindstringYesType of profile selected: external_corporate
addressobjectYesThe registered address of the entity
companyNumberstringYesThe company number of the API client (the client of BC), can be found in the client portal
countrystringYesThe country of nationality, in ISO 3166-1 alpha-2 country code
entityNamestringYesThe registered name of the entity
taxIdentificationNumberstringYesThe TIN of the entity

To create a profile for a natural person:

FieldTypeRequiredDescription
kindstringYesType of profile selected: external_individual
addressobjectYesThe residential address of the individual
companyNumberstringYesThe company number of the API client (the client of BC), can be found in the client portal
countrystringYesThe country of nationality, in ISO 3166-1 alpha-2 country code
dateOfBirthstringYesThe DOB of the individual
firstNamestringYesThe First Name of the individual
lastNamestringYesThe Last Name of the individual

Duplication check on profiles:

A duplication check is performed at the time of profile creation based on a combination of key attributes, depending on the profile type for a given client:

Self (own organisation):

label

External Corporate (business entity):
taxIdentificationNumber (TIN) + country + entityName + address

External Individual (third-party individual):
firstName + lastName + country + dateOfBirth + address


💡

Profile ID

A profileId is returned upon creation. Store this value securely, as it is required for subsequent operations.


Example

Create Profile

{
  "kind": "self",
  "label": "Primary treasury profile",
  "companyNumber": "123456789"
}

Response

{
  "kind": "self",
  "companyNumber": "123456789",
  "label": "Primary treasury profile",
  "id": "prof_01hx2zq3k4m5n6p7q8r9",
  "status": "Created",
  "createdAt": "2026-04-29T09:00:00+00:00",
  "updatedAt": "2026-04-29T09:00:00+00:00"
}

Retrieve Profiles

ℹ️

Fetch a single profile

Endpoint

https://www.bankingcircleconnect.com/api/v1/digital-assets/profiles/{id}

Purpose

Retrieves a specific profile by its unique identifier.

Usage

Used to validate profile details and status before downstream operations.

ℹ️

List profiles

Endpoint

https://www.bankingcircleconnect.com/api/v1/digital-assets/profiles

Purpose

Retrieves all profiles associated with the authenticated client.

Usage

Typically used after profile creation to obtain entities for downstream operations.

⚠️

Important

Uses cursor-based pagination.



Coming Soon

📌

Webhook

Webhooks provide real-time updates for:

  • Transactions
  • Profiles

Sandbox Testing

A dedicated sandbox environment will be available soon, giving you a safe space to explore the API, test your integration, and simulate payout flows without impacting real funds.




Did this page help you?