Start identity verification
Creates a Stripe Identity session: a government ID document plus a matching selfie, on Stripe’s hosted pages. The documents are held by Stripe — Farthing never receives, stores or proxies ID images, only the verdict.
The verdict arrives asynchronously; verificationStatus on GET /v1/billing moves from pending to verified. A failed attempt goes back to pending and can be retried — a typo’d document is not fraud.
Authorizations
A dashboard session — the short-lived JWT a signed-in human holds at the dashboard, sent on the same Authorization: Bearer header. Dispatched by shape: a session token is a JWT, an API key starts with ck_. Sessions cannot be created through this API, and operations that list only this scheme refuse API keys with 401.
Response
The Stripe Identity URL.
A Stripe-hosted page to send the browser to. Farthing never sees the card or the ID document — the flow happens on Stripe's pages.