Skip to main content
PUT
Update Related Person
Updates a related person on a business account’s application. Provided fields are merged into the existing record.
taxId can be patched onto an existing person — useful for representatives added before the field existed, whose USD issuance is blocked until one is supplied. See Add Related Person for the per-country formats.

Mandatory and optional fields

Every field is optional in this request — provided fields are merged, omitted fields keep their stored values. The same fields are mandatory before submission as on Add Related Person: firstName, lastName, email, phone, dateOfBirth, sourceOfWealthExplanation, a government identifier, and all five currentAddress fields. ownershipPercentage and roles stay optional throughout.
currentAddress is all-or-nothing. Send it and all five fields must be present — there is no patching a single line of an address.

Example Request

Example Response

data is the whole merged record, not just the fields you sent.

Errors

Authorizations

X-API-Key
string
header
required

Your Rolla API key

Path Parameters

accountId
string<uuid>
required

Identifier of a business account owned by the same user as your API key's business

personId
string<uuid>
required

Identifier of a beneficial owner or director on this account

Body

application/json
firstName
string
Minimum string length: 1
Example:

"Jane"

lastName
string
Minimum string length: 1
Example:

"Doe"

roles
enum<string>[]

The person's capacities on the business. Defaults to ["Beneficial Owner"] when omitted or empty, so the stored record always has at least one role.

Available options:
Beneficial Owner,
Director
Example:
email
string<email>

Where this person’s KYC link is sent

Example:

"jane@betalogistics.com"

phone
string

International format

Minimum string length: 1
Example:

"+13025550124"

dateOfBirth
string

YYYY-MM-DD. The person must be 18 or older

Example:

"1985-09-21"

ownershipPercentage
number

Ownership stake as a percentage, not a fraction: send 60 for 60%. A value between 0 and 1 is rejected.

Required range: 0 <= x <= 100
Example:

60

currentAddress
object

Residential address. All-or-nothing: whenever the object is sent, every one of the five fields must be present.

sourceOfWealthExplanation
string

Free-text explanation of where the person’s wealth comes from. Accepted empty here; required before the application can be submitted.

Example:

"Salary and dividends from Beta Logistics LLC"

taxId
string | null

The person's government identifier, in the format their country of residence issues — Mainland China: 18-character resident ID; Hong Kong: HKID; United States: SSN or ITIN; elsewhere: the national ID or tax number as issued. Nigerian residents send nin instead. Required before the application can be submitted, and can be patched onto an existing person. The format is validated by the USD provider when the account is issued.

Example:

"123456789"

bvn
string | null

Bank Verification Number. Nigerian residents only; must be 11 digits when the person's currentAddress.country is NG.

Example:

"22345678901"

nin
string | null

National Identification Number, accepted in place of taxId for Nigerian residents; must be 11 digits when the person's currentAddress.country is NG.

Example:

"12345678901"

Response

Related person updated successfully

status
integer
required
Example:

200

message
string
required
Example:

"Related person updated successfully"

success
boolean
required
Example:

true

data
object
required

A beneficial owner or director on a business account’s application.