Go-Live Requirements
Getting started guide
This page describes the process for starting a new integration with Fourthline, or adding a new implementation as an existing Business Partner.
Overview
The high-level process:
Process overview
Here’s how it works, step by step:
1. SDPA agreement
Define your Solution Description and Platform Architecture (SDPA) with Fourthline. This document formalizes the scope and setup of your integration.
The SDPA includes:
- Your solution(s) and modules
- Integration option(s)
- Specific configuration
- Deployment and operating models
- Identifiers, credentials, and IP address restrictions
- Any feature requests
- Communication channels and meetings
- Implementation timeline
- Dependencies
For product-specific configuration requirements:
- Identity Verification
- Qualified Electronic Signature
- AML Screening
- Client Authentication
- Document Authentication
Tip
Define your requirements as specifically as possible. Clear requirements reduce iteration and help ensure an accurate implementation.
2. Environments
Use separate environments for testing and live operations.
- Sandbox (testing):
https://api.ext-sandbox.fourthline.com- Production (live):
https://api.fourthline.com3. Authentication & API credentials
To start testing, you must have valid API credentials.
- Learn how credentials work on the dedicated API credentials page.
- Generate credentials in the self-service Hub.
4. Testing
Test your integration in the Sandbox environment.
Fourthline verifies real clients and authentic identity documents. We do not provide dummy data, sample documents, or test files.
To test your integration:
- Use official specimen documents, such as PRADO.
- Alternatively, use real identity documents and personal data from colleagues. To safeguard the privacy of your colleagues and their data, when you have finished testing, contact your Fourthline delivery manager to delete all testing data from the Sandbox environment.
- Always run tests in the Sandbox environment
Use the available test endpoints:
| Solution | Endpoint | Description |
|---|---|---|
| Identity Verification | Set test outcome | Set an outcome to apply when a case reaches a specific status. |
| Qualified Electronic Signature | Test signature flow | Start a test signature flow and specify the outcome. |
| Qualified Electronic Signature | Get test passcode | Get a one-time passcode to confirm a test signature, without requiring a valid mobile phone number. |
More information
For more information about how Fourthline protects your data, see Security & Compliance.
5. Go-live checklist
Complete the following before going live:
- Backend testing of all API endpoints used
- Functional testing to ensure the integration meets requirements, including business logic for different statuses
- UI and user experience review
- Business testing of the end-to-end flow on your side
- Case processing training for partners who process their own cases
- Alignment with Customer Success team
- Alignment with Fourthline Operations team
- Jira service desk for monitoring phase setup and testing
Tip
In addition to testing with Fourthline, perform any additional validation required in your environment, such as security or penetration testing.
Success
After approval, your integration is live. Ongoing support is provided to ensure stable operations.
Updated about 1 month ago