---
title: "Submit the session for activation"
method: POST
path: "/api/fma/v1/kyc/submit"
tags: ["Managed Custody KYC"]
---

# Submit the session for activation

`POST /api/fma/v1/kyc/submit`

Hands the session off to UR's background activation scheduler after Form A is signed. Returns state Submitting with queued false as the success signal on these KYC paths; UR then activates the bank account asynchronously and delivers the fma.account.result webhook when the URID reaches Live status.

## Headers

- `X-Ur-Id` string
- `X-External-User-Id` string
- `X-Api-Signature` string, required
- `X-Api-Deadline` string, required
- `X-Api-PublicKey` string, required

## Request body

- KycSubmitRequest
  - `sessionId` string, required — The onboarding session UUID returned by create-account.

## Response `200`

Business result envelope. code 0 means success; business rejections return HTTP 200 with a non-zero code.

- KycSubmitResponse
  - `code` integer — Business result code. 0 means success; business rejections return HTTP 200 with a non-zero code.
  - `message` string — Human-readable diagnostic for non-zero codes.
  - `data` object
    - `state` string — Submitting on success; UR's background scheduler now owns the session.
    - `queued` boolean — False is the success signal for these KYC paths; UR can proceed with bank activation immediately without further user action.
    - `awaitingPenny` boolean — False on the documented KYC paths.

---

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