---
title: "Start passkey approval ceremony for a pending transaction"
method: POST
path: "/wallets/passkey/approval/start"
tags: ["SCA Transactions"]
---

# Start passkey approval ceremony for a pending transaction

`POST /wallets/passkey/approval/start`

## Request

- Base URL: `https://www.sandbox.striga.com/api/v1`
- URL: `https://www.sandbox.striga.com/api/v1/wallets/passkey/approval/start`
- Auth: API key in header `api-key` and API key in header `Authorization`

Issues a WebAuthn assertion challenge bound to an existing transaction `challengeId` (returned by an initiate endpoint). Required only when the partner picked `verificationMethod: passkey` on the initiate call — run this before submitting the signed credential to `/wallets/transaction/confirm`.

## Request body

- object
  - `userId` string, required
  - `challengeId` string, required: Transaction challenge id returned by an initiate endpoint.

## Response `200`

WebAuthn assertion options bound to the transaction challenge.

- object
  - `challengeId` string, required
  - `dateExpires` string
  - `verificationMethod` 'passkey', required
  - `options` object, required: Standard WebAuthn `PublicKeyCredentialRequestOptions`. Base64url-encoded binary fields are passed through to the browser without modification.
    - `challenge` string
    - `timeout` integer
    - `rpId` string
    - `allowCredentials` object[]
      - `type` string
      - `id` string
    - `userVerification` string
  - `allowedOrigins` string[], required
  - `relyingPartyId` string, required

## Other responses

- `400`: Request was rejected. The `errorCode` field disambiguates.
- `401`: Invalid API key or HMAC signature.

---

[API](https://skmtc.dev/striga/apis/striga-strong-customer-authentication.md) - [All operations](https://skmtc.dev/striga/apis/striga-strong-customer-authentication/llms.txt) - [OpenAPI document](https://skmtc.dev/striga/apis/striga-strong-customer-authentication/revisions/6a0cf1c67072?raw)