> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sumvin.com/llms.txt
> Use this file to discover all available pages before exploring further.

# KYC passthrough

> How a Sumvin user keeps their verified KYC state when they enter a ramp widget.

<Snippet file="product-term-disambiguation.mdx" />

When your KYC-verified Sumvin user opens a ramp widget for a ramp or bank-linking flow, they do not re-verify. Sumvin shares the user's existing KYC outcome with the ramp on their behalf, so the widget takes them straight to the destination flow — payment, institution select, or payout confirmation. This is part of **Atomic Money** — Sumvin's payments, ramps, cards, and settlement surface.

For the trust model behind why this reuse is acceptable, see [KYC and attestation](/concepts/kyc-and-attestation).

## What you observe

There is nothing explicit to opt in to. The passthrough is automatic on any ramp-touching flow for a KYC-verified user. As the partner, you see:

* The widget opens directly on the destination step — payment capture, institution picker, or payout confirmation — rather than on a document-upload screen.
* Ramp sessions against a KYC-verified user return `201 Created` from `POST /v0/ramp/sessions`. Against an unverified user, the call returns `403 Forbidden` with error code `KYC_NOT_VERIFIED`.

If the user has not completed Sumvin KYC, route them through the [KYC guide](/guides/kyc) before retrying. If you send an unverified user into a ramp widget through a flow that does not gate on KYC, the ramp partner will collect verification in-widget — which works, but means the user ends up verified with the provider separately from Sumvin, without the reuse benefit.

## One user, one ramp identity

Each Sumvin user maps to a single ramp identity for the lifetime of their account. Re-entering a ramp flow — another ramp session, a second bank-linking attempt, a different widget — always resolves to the same identity, and the verified state carries across all of them.

## Failure modes

| Symptom                                                                  | Cause                                                    | Resolution                                                                                                     |
| ------------------------------------------------------------------------ | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| Ramp widget asks the user for KYC documents                              | The user has not completed Sumvin KYC.                   | Route the user through the [KYC guide](/guides/kyc); retry the ramp flow once their KYC is approved.           |
| `POST /v0/ramp/sessions` returns `403 Forbidden` with `KYC_NOT_VERIFIED` | Same as above — no verified KYC on the Sumvin side.      | Check `GET /v0/kyc/status`, then route through [KYC](/guides/kyc).                                             |
| Ramp session creation returns `502 Bad Gateway`                          | Upstream provider rejected the request. Often transient. | Retry with a fresh quote; if it persists, check the [reference](/products/ramps/reference) for the error code. |

## Related

* [KYC guide](/guides/kyc) — how a user becomes KYC-verified
* [KYC and attestation](/concepts/kyc-and-attestation) — the trust model
* [Atomic Money ramps overview](/products/ramps/overview)
* [Reference](/products/ramps/reference)