API-Led Onboarding
Your platform builds the participant experience and calls Fiserv for everything behind it. This model provides the most control and requires the most implementation effort.
Your platform controls when evaluation starts and when to check back. Nothing is pushed to your platform.
Create and Update Participant Profiles
Your platform creates a participant record first, then updates it as your screens collect more information. The same endpoint handles create, update, verification submission, and provisioning through different operation types. Submission is explicit, and nothing is evaluated until your platform requests it.
Once a section is submitted, it is frozen. Corrections after that point go through the document path rather than by editing fields.
Verification and Asynchronous Status Handling
Most verification is asynchronous: submission moves the step to pending and the decision arrives later, although a straightforward individual participant can clear or decline immediately. Each step reports its own status and, where something is required from the participant, a pending action naming what to do next. Drive your interface from those actions rather than from a fixed screen order.
Document and Remediation Flow
Where documents are required, each requirement can list several acceptable options, and one document can satisfy more than one requirement. Uploads are tagged by side, so a two-sided ID is uploaded as separate parts, and liveness capture is its own type. Re-uploading replaces the previous file. Once everything is in place, your platform submits the set for evaluation, and the cycle repeats if more is required.
Status Monitoring
In API-led onboarding, your platform runs the status loop. Every save returns current step state and outstanding actions, and an inquiry call reads status on demand. Plan for polling rather than push. Push delivery of onboarding status is the stated direction, so confirm availability before designing around it.
Because there is no Fiserv SDK in your client to collect them, send device and session signals with the application, at minimum a device session identifier. Platforms can opt out and carry the associated risk, but fraud screening is weaker without these signals.
Related Topics
- Hosted Onboarding – Use a Fiserv-hosted participant onboarding experience
- Embedded Onboarding – Embed onboarding within your existing platform experience