What you observe
There is nothing explicit to opt in to. The passthrough is automatic on any Meld-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 CreatedfromPOST /v0/ramp/sessions. Against an unverified user, the call returns403 Forbiddenwith error codeKYC_NOT_VERIFIED.
One user, one Meld identity
Each Sumvin user maps to a single Meld identity for the lifetime of their account. Re-entering a Meld 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 |
|---|---|---|
| Meld widget asks the user for KYC documents | The user has not completed Sumvin KYC. | Route the user through the KYC guide; retry the Meld 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. |
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 for the error code. |
Related
- KYC guide — how a user becomes KYC-verified
- KYC and attestation — the trust model
- Meld overview
- Reference