Create and configure service providers

This topic describes how to create and configure service providers.

About service providers

To integrate iProov’s services into your application or website, start by creating a Service Provider in iPortal.

If you do not have the necessary access, please contact your organization's primary iPortal admin or your Customer Success representative for assistance.

The Service Provider plays a vital role in generating detailed and comprehensive reports.

To ensure clarity and effective management, iProov strongly recommends selecting meaningful names that accurately represent the intended use. (edited)

Recommended naming conventions

• Direct customers: <direct customer name>.<product or use case>.<country or region>.<environment>

For example: WaterlooBank.banking.uk.prod

• Partners: <partner name>.<end customer name>.<product or use case>.<country or region>.<environment>

• For example: Microsoft.WaterlooBank.banking.uk.prod

Create service providers

1. Log into : https://portal.iproov.com/.

2. Click Service providers.

3. Click Create a service provider.

4. Enter a value for Service provider name.

5. Enter a Description, for example: Waterloo Bank production SP for opening current account use case

6. Select a Service Location. The platform is available in multiple geographical regions.

Select the most appropriate to ensure minimum latency and the best user experience.

7. Select an appropriate Environment type:

• Production: live service provider.

• Development: develop and test a service provider before it goes live.

• Testing: test an implementationn in a service provider.

Type	Description	Restriction	Intended Use
Development	Some biometric and security tests are disabled by default. This allows for development and tools to be used.	A fair use transaction usage & TPS/TPM policy applies. SP will be suspended if no traffic for 12 months.	Development Quality assurance (e.g. Functional testing, Integration testing)
Test	All biometric and security tests will be enabled. This type of SP can be used for demo purposes. If testing for threat methods is required, a Test SP should be used (please consult our testing rules of engagement and speak to your iProov representative). The Secured by iProov logo will appear on the SDK when using Test SPs.	Development tools may cause transactions to be rejected. A fair use transaction usage & TPS/TPM policy applies. SP will be suspended if no traffic for 12 months.	User Acceptance Testing & Pre-Production Testing for threat methods Demo
Production	All biometric and security tests will be enabled. Development tools may cause transactions to be rejected. Should only be used for production traffic.	TPS/TPM policies will be based on contractual agreements. All transactions will be billable according to contractual agreement.	Production Only