KYC Flow, Step by Step
Pollar runs identity verification as ordered steps: every step is required, and Pollar talks to the providers so your app does not. This page plays a verification end to end. Pick who asks for the steps, which steps they are, the user's document and the outcome: the diagram rebuilds the flow for that combination.
Your app's own KYC takes Didit and form steps, configured under Identity checks > Verification steps. A ramp route or a card provider can also require a SEGIP check of a Bolivian ID card, set per corridor under Cash in and out > Providers. Prices come from your app's price list, see Credits.
A ramp route or a card provider can require its own steps: Form, Didit and SEGIP, in that order. Every step is required. Pollar runs them with the providers enabled for your app, and every event is charged to your app's credits.
getKycStatus() returns one of these for the signed-in user. With several steps, the status is approved only once every step is complete.
| Status | What it means | What the user sees | What your app does |
|---|---|---|---|
| none | The user has not started. | Your "Verify identity" entry point. | Opens the flow. |
| pending | A step is still open, or the case is in manual review (decisionStatus manual_review). | The modal resumes the open step, or says the verification is in review. | Waits. No new session is needed. |
| approved | Every step is complete. Carries expiresAt: the approval window, or earlier if the document expires first. | Can go on. | Unlocks what needs a verified identity. |
| rejected | Didit declined the attempt, or SEGIP found a field the user can fix. | The reason and a way to try again. | Lets the user retry. Each new attempt is charged. |
| expired | The session was abandoned or the approval expired. | Has to verify again. | Opens the flow again. |
Each event is charged to your app's credits at the price in your price list. If the balance does not cover it, Pollar does not open the Didit session, check SEGIP or store the form, and nothing is charged.
| Event | When | When it repeats |
|---|---|---|
| KYC session started | When the Didit session opens, before the user takes a photo. | Each retry opens a new session. |
| KYC verification completed | When Didit approves or declines. | Once per session. |
| SEGIP check | On every check of the ID card. | Each corrected field is a new check. |
| Form submitted | When the form is submitted. | Each submission, a correction included. |
Names, document and date of birth are stored with AES-256-GCM under a data key of their own, wrapped by AWS KMS. The document number is never stored in clear.
Document, portrait and liveness images are stored encrypted with that identity's key. Form answers and the data sent to SEGIP are encrypted too.
Pollar keeps Didit's normalized result, never its full response. Provider credentials are encrypted.
When a document is already verified on another account of your app and the faces match, the accounts link on their own. Any other duplicate waits for a human review.