Skip to main content
POST
Submit Representative KYC Reliance
Submits identity documents you have already verified yourself for one representative — a beneficial owner or director — of a business account, instead of sending them through Rolla’s hosted liveness check. This is the per-representative parallel of Submit KYC Reliance, which covers individual accounts. Use it when the people behind a business have already completed identity verification on your side and re-verifying them would be redundant.
KYC reliance is enabled per partner. If it is not enabled for your business the endpoint returns 403. Contact your Rolla representative to have it turned on — enabling it means agreeing on the verification standard your own KYC meets.
One call per representative. Each beneficial owner and director is verified separately and must be submitted on their own personId. Verifying one does not verify the others, and Submit Application still requires every one of them to pass.

Request

Send as multipart/form-data. Both files are required. personId is the id returned by Add Related Person — the same id used for the related-person KYC link and for that person’s document uploads.

Example Request

Example Response

verification is that representative’s own status — the same value Get Requirements reports for them under relatedPersons. readyToSubmit reflects the whole application — fields, documents and every representative’s KYC — so it stays false while any of them is outstanding.

Key Behaviours

The review is not instant. verification commonly comes back as pending on the call that submits it. Poll Get Requirements until that person reads verified.
Verification still blocks submission. Submit Application returns 409 KYC_INCOMPLETE until every representative’s review completes successfully — reliance replaces the hosted liveness step, not the requirement itself.
Reliance and the hosted link can be mixed on the same account: verify some representatives yourself and send a KYC link to the rest. Both resolve to the same per-person verification.
A passport uploaded here is reused when a USD account is issued, so a bank-account request will not ask for it again. See Issue Bank Account.

Errors

When the identity provider rejects an upload, the reason is passed through rather than hidden behind a generic failure:

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 the related person, as returned by Add Related Person

Body

multipart/form-data
passport
file
required

The account holder's passport image or PDF

selfie
file
required

Selfie or liveness capture from your own verification. Image or video

country
string
required

2-letter ISO code of the country that issued the passport

Required string length: 2
Example:

"CN"

documentNumber
string
Maximum string length: 64
Example:

"E12345678"

issueDate
string<date>
Example:

"2020-03-14"

expirationDate
string<date>
Example:

"2030-03-13"

Response

KYC reliance submitted for the representative

success
boolean
Example:

true

message
string
Example:

"KYC reliance submitted successfully"

data
object