e2e

Demopay (Own SSO)

Learn about our alternative end-to-end customer journey from onboarding a customer to settling their order. If you want to use guest checkout, you can enable a combination of your own SSO and our SSO capabilities.

1

Bring your own SSO

Customer uses your SSO to log-in ahead of starting their credit journey. This step can be skipped if guest checkout is selected.

2

createApplication

The applicant enters their personal information into a blank application form and the request is sent, creating the application.

3

verifyEmailAddress

Check whether the applicant’s email address exists. If this is false, it is still possible to continue with the acquisition journey. This step requires a third-party integration.
Please note that steps 2, 3, and 4 happen all together

4

verifyPhoneNumber

Check whether the applicant’s phone number exists. If this is false, it is still possible to continue with the acquisition journey. This step requires a third-party integration.
Please note that steps 2, 3, and 4 happen all together

5

checkEligibility

Once the applicant has created an application, complete a soft check on their eligibility. The response returned will define the next step in the customer journey. For this journey, the state is defined below. Information is passed at this point to your credit decision engine.
Please note that steps 2, 3, and 4 happen all together

6

SSO Widget - Create credentials

Create log-in credentials to save and return your application journey, repeat spend and set up your e-servicing account.

7

ApplicationPennyDropInitiate

Match the applicant's details to the applicant’s bank account using a third-party integration. If it matches, 1p will be sent to the customer with a code as the reference.

8

ApplicationPennyDropValidate

Verify the code provided by the applicant to the code sent to the bank account.

9

renderDocument

Retrieve and display an applicant’s Important Customer Information, Pre-contract Credit Information, and the Credit Agreement in HTML or PDF. This endpoint is called once per document that is retrieved.

10

signature

An applicant will tick their e-signature and submitting this will confirm they have accepted the terms of their agreement. The response returned will define the next step in the customer journey, for this journey, the state is defined below.

11

requestDecision

Perform a hard check on the applicant’s credit history and use the returned information in your credit decision engine. For this journey, the state is defined below.

12

createCustomer

Onboard the applicant as a customer and complete the credit acquisition process. For this journey, the state is defined below.

13

retrieveSpendOptionsForCustomerRef

Retrieve and display the spend options available based on the customer and basket.

14

authorise

Authorise a transaction once a spend option has been chosen.

15

settle

Settle the authorisation once the order has been received.

Request Example

Request

Text

1There are no NewDay-side requests or responses for this step.