Vault sessions
Disconnect a user
End your app’s connection to a user. Your app can no longer read their cards or ask them to pay.
DELETE
Call it when the user asks your app to forget them. Every token your app holds for the user stops working, links you sent them stop opening, and the user’s cards stay in their Vault.
After the call, List a user’s vaulted cards answers
The tokens stop working before the user’s auto-approval for your app does. While the second half is still in flight, the call answers:
404 connection_not_found for the user, and a checkout authorization for them is refused. To work with the user again, send them a new vault session.
Call it as often as you like. A second call answers 200 with every count at 0.
Errors
A user your app never connected is refused, so the call tells you nothing about anyone else’s users:
Deleting one vault session with
DELETE /api/v2/vault_sessions/{id} ends only that link and the token it gave you. The user stays connected to your app.Authorizations
A platform access token. Get one on the Create an access token endpoint by exchanging your client_id + client_secret, then send it as Authorization: Bearer <token>. Tokens live one hour.
Path Parameters
The user's id, as your app stored it when they connected.
Maximum string length:
64Response
The user is disconnected from your app.
Available options:
vault_user_connection Available options:
false Tokens your app held for the user that stopped working on this call.
Wallet links your app sent the user that stopped working on this call.
Vault session links the user had not opened yet. A disconnected user who taps one gets nothing.