Skip to main content
POST
Confirm trusting a beneficiary

Authorizations

Authorization
string
header
required

API token authentication using format <api token id>:<api client secret>

Path Parameters

externalAccountId
string
required

The unique identifier of the external account (beneficiary) being trusted.

Body

application/json

Confirms trusting or untrusting a beneficiary by submitting the SCA proof. Carries the same proof fields as an ScaAuthorization (code for SMS_OTP / TOTP, or passkeyAssertion + origin for PASSKEY) and, when the start issued one, the challengeId. The beneficiary is identified by the externalAccountId in the path — no separate handle is needed.

code
string | null
required

The one-time code the customer received by SMS, or read from their authenticator app. Provide for SMS_OTP / TOTP. In sandbox, the code is always 123456.

Example:

"123456"

challengeId
string | null

The challenge handle from the trust start's scaChallenge, when one was issued. Omit when the start returned no challenge.

passkeyAssertion
object | null

Opaque WebAuthn assertion produced by the device from the challenge's assertion options. Required when satisfying a PASSKEY challenge.

origin
string | null

The WebAuthn origin the passkeyAssertion was produced against. Required alongside passkeyAssertion; omit it for the code path.

Example:

"https://app.example.com"

Response

Beneficiary trusted.

The result of a confirm-trust / confirm-untrust call. trusted is true after a successful trust and false after a successful untrust.

trusted
boolean
required

Whether the beneficiary is now trusted. true after a successful trust, false after a successful untrust.