Complete an SCA login
Finalize an SCA login by submitting the proof for the started factor
(code for SMS_OTP / TOTP, or passkeyAssertion + origin for
PASSKEY), echoing the challengeId for SMS_OTP. Returns the
reported session status.
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>
Query Parameters
The unique identifier of the customer completing an SCA login.
Body
- Option 1
- Option 2
Completes an SCA login by submitting the proof for the started factor. Carries the same proof fields as an ScaAuthorization (code for SMS_OTP / TOTP, or passkeyAssertion + origin for PASSKEY), plus the factor being completed and, for SMS_OTP, the challengeId returned by the login start.
The factor being completed; must match the started login.
SMS_OTP, TOTP, PASSKEY 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 returned by the login start, required for SMS_OTP and omitted for other factors.
Opaque WebAuthn assertion produced by the device from the login start's passkeyOptions. Required when completing a PASSKEY login.
The WebAuthn origin the passkeyAssertion was produced against (one of the login start's allowedOrigins). Required alongside passkeyAssertion; omit it for the code path.
"https://app.example.com"
Response
SCA login completed; the session status is returned.
The status of a completed SCA login session.
The status of the login session, passed through verbatim (Grid does not normalize it). A successful login reports SUCCESS; other values indicate the login did not complete and should be surfaced to the caller.
"SUCCESS"