App Drop-in

Integration Options

Fourthline's App Drop-in lets you smoothly integrate workflows into your mobile app. It takes care of all interaction with the client, collects the relevant data (e.g. ID document, selfie, geolocation), and uploads it to Fourthline for case processing. You never handle sensitive personal data .

The SDK takes care of the user journey and orchestrates modules with a streamlined API flow. You can also easily level up from single products to multi-product solutions with no additional API requests.

All required images and data are captured in our best-practice UI and automatically uploaded to Fourthline for processing. You never handle sensitive personal data.

How it works

The App Drop-in supports the following:


Flow

The flow is as follows:

App Drop-in flow

App Drop-in flow


User interface

Fourthline provides the mobile-responsive UI , which is built in line with industry-standard best practices for user experience (UX):

  • The UI includes guidance and animations to help clients understand the journey.
  • Clients may not know how to take photos with appropriate lighting, background, and framing, which can lead to processing delays or unnecessary rejections. The UI provides clients clear instructions and real-time feedback to optimize image quality and maximize conversion.
  • The UI validates data entered by clients in real time to reduce input errors.
  • You can localize the UI text in a range of languages, and customize fonts and colors to match the look-and-feel of your brand.
  • Fourthline collects analytics data and continually updates the UI to improve conversion, meet evolving regulatory requirements, and keep pace with market trends in UIs and UX.
Note
Fourthline ensures photos are taken during the workflow, in compliance with art. 41b of the European Banking Authority – Guidelines on the use of Remote Customer Onboarding Solutions under Article 13(1) of Directive (EU) 2015/849.

How to integrate

See below for integration and configuration guidance.

Configuration

For configuration and setup instructions, see the relevant manual:

Integration manuals

For step-by-step integration manuals per solution, see the relevant integration guide:

UI customization

For how to customize the UI , see App UI Customization.

Duplicate submissions prevention

To prevent duplicate submissions, after a client completes the App drop-in flow, always verify the workflow status before allowing a new workflow to be launched. This prevents duplicate submissions and inconsistent workflow states.

Note
Store the workflowId returned when the workflow is first created and reuse it to check the status.

How it works

  1. Make a GET case status request.
  2. Read the verificationStatus value from the response.
  3. Do not allow a new workflow launch if the status is one of the following:
StatusDescription
completedWorkflow finished successfully
pendingWorkflow is still being processed
rejectedWorkflow was rejected

Only allow a new workflow to be launched when the status is new or another non-terminal state.

UI guidance

From a UI perspective:

  • Disable the launch button when the workflow status is completed, pending, or rejected.

  • Clearly explain why the client cannot continue (for example, Your verification is still being processed).

  • Re-enable the launch option only when the workflow is eligible to be restarted.

Support
For any questions, contact your Fourthline delivery manager.

Accordion in HTML5