Confirm untrusting a beneficiary
Finalize untrusting a beneficiary (identified by the externalAccountId in
the path) by submitting the SCA proof (code for SMS_OTP / TOTP, or
passkeyAssertion + origin for PASSKEY), echoing the challengeId when
one was issued. Returns trusted: false.
This endpoint is only meaningful for customers in a region where SCA is required (e.g. EU). For customers outside SCA-regulated regions, this returns 409.
In sandbox, the SMS/TOTP code is always 123456.
Authorizations
API token authentication using format <api token id>:<api client secret>
Path Parameters
The unique identifier of the external account (beneficiary) being untrusted.
Body
- Option 1
- Option 2
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.
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.
"123456"
The challenge handle from the trust start's scaChallenge, when one was issued. Omit when the start returned no challenge.
Opaque WebAuthn assertion produced by the device from the challenge's assertion options. Required when satisfying a PASSKEY challenge.
The WebAuthn origin the passkeyAssertion was produced against. Required alongside passkeyAssertion; omit it for the code path.
"https://app.example.com"
Response
Beneficiary untrusted.
The result of a confirm-trust / confirm-untrust call. trusted is true after a successful trust and false after a successful untrust.
Whether the beneficiary is now trusted. true after a successful trust, false after a successful untrust.