This flow only appears when identity verification is enabled on your account. When it is not, or when the user was verified recently enough to still be approved, the widget skips the step and goes straight to the operation. Ask your Ripio contact whether it is enabled for you — see Partner settings.
What the user sees
1
Fill in their details
In Argentina the widget collects the data itself across four steps — name, personal information, address, and financial information. In every other country the user goes straight to the provider.
2
Complete verification at the provider
The widget hands the user to Ripio’s identity provider to submit documents and a liveness check. This happens on the provider’s own pages, outside the widget.
3
Come back and wait for the decision
The provider returns the user to Ripio, which re-enters the widget on a status screen. The widget polls for the outcome every 10 seconds for up to 5 minutes.
4
Continue, or find out it failed
On approval the user carries on into the operation they came for. On rejection they see a failure screen with the option to contact support.
Verification can outlast the 5-minute window — plenty of submissions land in manual review. When that happens the widget stops waiting and tells the user they will hear by email; the approval email arrives when the decision is made, and their next visit finds them already verified.
What your backend observes
Verification results reach you as KYC Webhook Events, the same events an API-driven KYC produces. Two details matter for widget users:
Events arrive at the
kyc_webhook_url configured on your account, which is separate from your main webhook URL.