---
updatedAt: 2025-06-12T23:56:41.000Z
agentTools:
  projectIndex: https://docs.fiatrepublic.com/llms.txt
---

# Enabling USD Services

As part of enabling **USD** for our Members, some integration changes will be necessary.

### Additional required fields for End Users to create USD account

#### Individual End Users:

* User's phone number
* User’s nationality
* Type of identity document (e.g., Work Permit, Passport)
* Document number

Create [Individual End User](https://docs.fiatrepublic.com/reference/create-individual-end-user) & [Object](https://docs.fiatrepublic.com/reference/individual-end-user-object) explained

#### Business End Users:

* UBO's phone number
* UBO's nationality
* UBO's type of identity document (e.g., Work Permit, Passport)
* UBO's document number

Create [Business End User](https://docs.fiatrepublic.com/reference/create-business-end-user) & [Object](https://docs.fiatrepublic.com/reference/the-business-end-user-object) explained

## Identity Verification Document Requirement

To comply with regulatory requirements and enable United States Dollar (USD) services for your entities, an **Identity Verification document** must be provided. This requirement applies to the following:

* Your **Member Entity**. That means that in first step, you'll first need to upload an `IDENTITY_VERIFICATION` document for your company's Ultimate Beneficial Owner (UBO). To do this, you use [Create Document endpoint](https://docs.fiatrepublic.com/reference/create-document), and pass `businessId` which you can retrieve your businessId by calling the `GET /member-details endpoint` [GET Member Details](https://docs.fiatrepublic.com/reference/get-member-details) , or alternatively, manage this process via the Payment Dashboard.
* **End Users:** When creating a new End User for whom USD services are intended, or when enabling USD services for an existing End User.
* **Businesses:** When creating a new Business (either a Linked Business or a Business End User) for which USD services are intended, or when enabling USD services for an existing Business we will require you to provide Identity Verification document for the UBO

**What is required?**

You must upload a document that serves as proof of identity verification for the entity in question. When uploading this document:

* It is expected that the `type` parameter in the [Create Document](https://docs.fiatrepublic.com/reference/create-document) request is set to `IDENTITY_VERIFICATION`.
* Ensure the `relatedEntityIds` parameter correctly links the document to the specific End User or Business ID.

> **⚠️ Important: Identity Report**
>
> The `IDENTITY_VERIFICATION` document contains the output from an identity verification check. Please be aware that this report can be generated by various providers.
>
> While **Sumsub** is a common source, the report could also originate from other services such as **Persona**, **Onfido**, or another provider chosen by the Member.

**How to provide the document:**

You can provide the required Identity Verification document by using the **[Create Document endpoint](https://docs.fiatrepublic.com/reference/create-document)**. Please refer to its detailed documentation for instructions on how to make the API request, including supported file formats (JSON, JPEG, PDF, PNG) and other necessary parameters.

**Summary of Process for USD Enablement:**

1. **Identify the Entity:** Determine if you are enabling USD for your own Member Entity, an End User or a Business (Linked Business/Business End User).
2. **Prepare Document:** Obtain the necessary Identity Verification document for that entity.
3. **Upload Document:**
   * Use the [Create Documents endpoint](https://docs.fiatrepublic.com/reference/create-document).
   * Set the document `type` appropriately (e.g., `IDENTITY_VERIFICATION`).
   * Link the document using `relatedEntityIds` to the correct End User or Business ID.
4. **Proceed with USD Service Enablement:** Once the required documentation is successfully uploaded and processed, you can proceed with enabling USD services for the entity through the relevant API endpoints or platform functionalities.