---
title: "Start an SCA login"
method: POST
path: "/sca/login/start"
tags: ["Strong Customer Authentication"]
---

# Start an SCA login

`POST /sca/login/start`

Begin an SCA login for the customer with the chosen factor, opening the
end-user SCA session (an exemption gating read / account access beyond the
per-transaction window). Returns factor-specific material: `SMS_OTP`
dispatches a code and returns a `challengeId` + `expiresAt`; `TOTP` returns
only the factor (the customer reads the code from their app); `PASSKEY`
returns WebAuthn `passkeyOptions`. Complete with
`POST /sca/login/complete`.

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`.

## Request body

- ScaLoginStartRequest — Selects which enrolled factor to start an SCA login with. The factor must already be enrolled (or, for `SMS_OTP`, the phone verified).
  - `factor` 'SMS_OTP' | 'TOTP' | 'PASSKEY', required — A Strong Customer Authentication factor. | Factor | Description | |--------|-------------| | `SMS_OTP` | One-time code sent by SMS to the customer's verified phone. Requires no prior enrollment. | | `TOTP` | Time-based one-time code from an authenticator app. Requires enrollment. Not valid for per-transaction challenges (cannot carry dynamic linking). | | `PASSKEY` | WebAuthn passkey assertion. Requires enrollment. |

## Response `200`

SCA login started; factor-specific material is returned.

- ScaLoginStart — The factor-specific material a customer needs to complete an SCA login. Each factor surfaces only the fields it issues: `SMS_OTP` carries `challengeId` and `expiresAt`; `TOTP` carries neither (the customer reads the code from their authenticator app); `PASSKEY` carries the opaque WebAuthn `passkeyOptions` with `allowedOrigins` and `relyingPartyId`.
  - `factor` 'SMS_OTP' | 'TOTP' | 'PASSKEY', required — A Strong Customer Authentication factor. | Factor | Description | |--------|-------------| | `SMS_OTP` | One-time code sent by SMS to the customer's verified phone. Requires no prior enrollment. | | `TOTP` | Time-based one-time code from an authenticator app. Requires enrollment. Not valid for per-transaction challenges (cannot carry dynamic linking). | | `PASSKEY` | WebAuthn passkey assertion. Requires enrollment. |
  - `challengeId` string, nullable — The challenge handle for an `SMS_OTP` login, threaded back on the complete call. Present only for `SMS_OTP`.
  - `expiresAt` string, date-time, nullable — Absolute UTC timestamp after which the `SMS_OTP` code expires. Present only for `SMS_OTP`.
  - `passkeyOptions` object, nullable — Opaque WebAuthn assertion request options. Present only for `PASSKEY`; pass to the device's WebAuthn API to produce the assertion submitted on the complete call.
  - `allowedOrigins` string[], nullable — The origins the WebAuthn ceremony may run against. Present only for `PASSKEY`.
  - `relyingPartyId` string, nullable — The WebAuthn relying-party id. Present only for `PASSKEY`.

## Other responses

- `400` — Invalid or unknown factor
- `401` — Unauthorized
- `404` — Customer not found
- `409` — SCA is not required for this customer.
- `500` — Internal service error

---

[API](https://skmtc.net/stainless-api/apis/grid-api.md) · [All operations](https://skmtc.net/stainless-api/apis/grid-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/stainless-api/grid-api/revisions/151f2d9bad9c/schema)