POST /api/v1/cashier/verification accepts an authenticated multipart request with a CSRF token for cookie authentication. Let the HTTP client set the multipart boundary; do not set a JSON content type.
| Field | Accepted value |
|---|---|
type | identity, address, or selfie |
documentType | ID for identity, PROOF_OF_ADDRESS for address, or SELFIE for selfie |
document | One JPEG, PNG, WebP or PDF file, at most 10 MiB |
Submit one file per document type. Combine front/back images or multiple pages into a single PDF before uploading. This matches the pending-document replacement model: submitting the same type again replaces its pending file. Unsupported categories, mismatched types, multiple files and excessive file sizes return a validation response without creating a document.
The web client maps passport, driver’s license and national ID selections to ID, address documents to PROOF_OF_ADDRESS, and selfie to SELFIE. Document bytes use the KYC service’s authenticated encrypted storage; a successful upload creates a pending review rather than approving verification.
GET /api/v1/cashier/verification reports the most recently uploaded identity/address document’s review status as pending, verified, or rejected. Where there is no document, the existing account verification flags provide the compatibility fallback. The legacy payment response key represents email confirmation and is labeled Email Confirmation in the web client; it does not certify payment documents.