Person creation and USD issuance are separate steps
Create the person first, then request an account with their person_id. A person record does not itself confirm approval for a USD account. Some information is optional during person creation but must be present before a personal USD account can be requested.
Personal USD prerequisites
| Field | Requirement |
|---|---|
name_first, name_last | First and last names matching the ID. |
name_other | Middle or other name when present; optional. |
phone, email, dob | Contact details and date of birth (YYYY-MM-DD). |
kyc_level | Basic KYC must be complete. |
id_level, id_type, id_number, id_country | Primary ID details. Use primary and an appropriate primary ID type such as passport, drivers_license, or national_id. Country codes use ISO 3166-1 alpha-2. |
bank_id_number | BVN for Nigerian IDs. This is not a universal requirement for every country; country-specific validation applies. |
address | Object containing line1, city, state, country, and postal_code. line2 is optional. |
background_information | Required for the personal USD account request, even if omitted when creating the person. Include employment_status, occupation, primary_purpose, source_of_funds, and expected_monthly_inflow. |
documents | An array containing identity-document and proof-of-address evidence. Each item includes type and a downloadable url. Date fields are issuance_date and expiry_date, where applicable. |
Use Create Person to create the holder and Create Document to attach additional evidence. Refer to Individual compliance requirements for the applicable proof-of-address policy, including a recent bank statement displaying the person's name.
Document array structure
Replace the placeholders below with the user's actual evidence. Use synthetic evidence only in the test environment. The URLs are illustrative and must be replaced with accessible document URLs; dates must match the actual documents.
{
"documents": [
{
"type": "passport",
"url": "https://documents.example.com/passport.pdf",
"issuance_date": "2025-01-01",
"expiry_date": "2035-01-01"
},
{
"type": "bank_statement",
"url": "https://documents.example.com/recent-bank-statement.pdf"
}
]
}
This is the document portion of the request, not a complete person-creation payload. Use the current Create Person endpoint for the full request format, and include the matching environment's bearer API key.
Request the account and handle RFIs
Once the person has the required identity, background information, and evidence, call Create Bank Account with person_id and currency: USD.
Issuance continues asynchronously. While the account is pending, Graph may request additional information or a hosted verification action through Requests for Information. Respond to each applicable RFI and track Issuance Events. A successful person-creation response or a completed RFI does not guarantee account activation.
Business accounts and beneficial owners
Business USD account requests follow the business onboarding route and require the business and its beneficial owners to meet the Business compliance requirements. Create each beneficial owner as a person with matching identity details, address, and supporting identity/proof-of-address evidence, then associate them with the business using the beneficial-owner endpoints.
The same person field conventions apply: name_other is optional, documents is an array, and bank identity requirements depend on country. Do not assume that the new personal USD RFI sequence or its sandbox scenarios apply to business accounts.

