POST
Step-up passkey challenge (v2)
Adding a beneficiary needs a step-up confirmation. To confirm with a passkey, use the general step-up endpoint, POST /v2/auth/passkey/challenge. It’s the same endpoint for every sensitive action (adding a beneficiary, an ad-hoc international or batch payment, and so on).
It returns a passkeySession and fido2options. Convert the base64url fields in fido2options to bytes, pass them to navigator.credentials.get() (or the native equivalent), and let the user unlock the passkey. That device step is the same as a passkey login, but don’t send the result to a login endpoint. It goes in the confirmation object when you add the beneficiary:
assertion is a JSON string with the device’s result in base64url: credentialIdB64, userHandleB64, clientDataJSON_B64, authenticatorDataB64 and signatureB64.
The passkeySession is valid for 3 minutes and for one request: the first request whose confirmation is checked uses it up, whether the check passes or fails. Request a new challenge for every attempt. An expired or spent session is a 422 SCA_EXPIRED; see Step-up confirmation.

Authorizations

Authorization
string
header
required

The user's access token from authentication. The program and environment come from the token.

Headers

x-program-id
string
required

Identifies the program. Can also be sent as the programId query parameter.

Response

Step-up challenge

success
boolean
Example:

true

data
object