Skip to main content
POST

Overview

If you already verified this person — in a partner verification application, with another provider, or through your own process — send us that verification instead of putting them through a second one. Two kinds of evidence are accepted:
What you send is evidence, not a verdict. Your decision is recorded as provenance and shown on the cardholder; the cardholder’s status is decided by our own screening of the document and images, exactly as for any other submission. An import saves a collection round-trip; it does not approve a cardholder on your say-so.

Request Body

Success Response (201)

The cardholder, with the status our screening reached — or PENDING while it is still running, in which case the decision arrives on your KYC webhook — plus what we recorded about the import:
The data object also carries every other cardholder field, as in Get Cardholder.

Error Codes

In the sandbox

The sandbox redeems shared sessions without a partner: the shareToken chooses the outcome.

Authorizations

Authorization
string
header
required

API key from the FYATU CaaS portal. Pass as Authorization: Bearer <key>.

Path Parameters

id
string
required

Cardholder ID

Body

application/json
reference
string
required

Your own identifier for this verification. Required

source
enum<string>

Inferred when omitted: a request with shareToken is SHARED_SESSION, one with document is EXTERNAL_PROVIDER

Available options:
SHARED_SESSION,
EXTERNAL_PROVIDER
provider
string

Who performed the verification, in your words. Recorded as given

decision
string

What the source concluded (e.g. APPROVED, DECLINED). Recorded as provenance, never used as our verdict

verifiedAt
string<date-time>

When the source verified the person, RFC 3339

shareToken
string

SHARED_SESSION only. Redeemable once

document
object

EXTERNAL_PROVIDER only. Required for that source

Response

Verification imported

success
boolean
status
integer
message
string
data
object