v1

latestOpenAPI 3.1.02026-07-26261466.6 KB
Connect

Verify the code

Checks the code the user entered and, on success, connects the user and returns the token pair to store. Completing the code is the authorization — there is no separate approval screen.

The returned access_token is the user's connection token: it acts on behalf of this user (send it as the bearer token to the MCP server to create cards, check balances, and shop as them). It is not the platform token — the endpoints in this reference keep using your platform access token and name the user with user_id.

A code can be verified once: a second verify of the same attempt returns invalid_connect_attempt.

In sandbox the code is always 111111.

post/api/v2/connect/verify

Request body

connect_idstring required

The id returned by /connect/start.

codestring required

The one-time code the user entered. Always 111111 in sandbox.

Response

The connection. Store the token pair and user.id — every KYC call names the user by it.

object'connection'
access_tokenstring

The user's connection token — store it to act on their behalf. Send it as the bearer token to the MCP server; never in the Authorization header of these endpoints.

refresh_tokenstring

Use it with /connect/refresh to get a new pair before the access token expires.

token_type'Bearer'
expires_ininteger

Seconds until the access token expires (3600 = one hour).