eKYC

What is the Penny Drop process?

1. 1
   Customer enters bank details: The Initiate Penny Drop endpoint within the eKYC API is called and verifies:
   
   - The bank account supplied is a valid UK bank account.
   
   - The bank account matches to the customer.
2. 2
   1p is sent to the bank account: If the bank account passes the checks above, then 1p is sent to the bank account with a code via a Faster Payments service.
3. 3
   Customer retrieves the code: The customer logs into their bank account and retrieves the code.
4. 4
   Customer inputs the code: The customer enters the code, and the Validate Penny Drop endpoint within the eKYC API is called to verify it against the code sent to the bank account.
5. 5
   Outcome: If the code matches, the customer passes the Penny Drop process. If it does not match, the customer fails the Penny Drop attempt. They may be able to re-try code input depending on business logic and outcome of any previous attempts.

What is the OTP process?

1. 1
   Customer journey requires OTP - code is triggered: The Initiate OTP endpoint within the eKYC API is called and triggers an OTP to the chosen phone type (mobile or landline) or email address or the respective phone number or email address held on the customer’s application or account (unless a phone number is provided in the request).
2. 2
   Customer receives the code: The customer receives the code to the chosen phone number or email address – via SMS to mobile, an automated call to landline, or an email to email address.
3. 3
   Customer inputs the code: The customer enters the code, and the Validate OTP endpoint within the eKYC API is called to verify the code sent to the phone number or email address.
4. 4
   Outcome: If the code matches, the customer passes the OTP process. If it does not match, the customer fails the OTP attempt. They may be able to re-try code input or trigger a new OTP depending on business logic and outcome of any previous attempts.

How do the eKYC API's work?

Penny Drop and OTP are initiated and validated in the same way but have different methods to send out the respective code. Below is what a successful eKYC initiation and validation flow looks like.

1. 1
   You initiate your chosen eKYC method to send the required code to the customer.
2. 2
   A successful initiation will:
   
   - Update the status to initiated.
   
   - Return an authId, remainingPasscodes and journeyId.
   
   - Send the required code to the customer.
3. 3
   The customer retrieves and enters the code, which is passed through the relevant validation endpoint with the authId and id.
4. 4
   If the validation succeeds the customer's status will be updated to authenticated.

Customise eKYC

eKYC restrictions are configured based on your requirements. The customisable restrictions and descriptions are listed below.

eKYC Statuses

The customer will have one of the following eKYC statuses depending on the eKYC method used and whether the eKYC method is being initiated or validated.