Acquisition Handover Journey
Learn how to begin or resume an acquisition journey, and smoothly transition it to our platform.
As a NewDay partner, you can choose to host the first step of the customer acquisition process directly on your own website. This means collecting customer details in a quote form and checking customer eligibility.
In addition, you can allow your applicant to drop off during their acquisition journey and subsequently return to it by logging back into the account they have with you.
Before handing over
Before handing over,
you’ll need to collect the applicants data on a ‘check eligibility’ form
and then use that data to perform an eligibility check by calling the Eligibility endpoint. The API documentation provides details on mandatory fields and required validations.
After reaching this stage, the application can be handed over to us.
The Handover Journey can take place two scenarios using the same process:
- After receiving a check eligibility response from the Acquisition API.
- If the customer drops off and wants to resume the journey at a later point.
To hand over control of the journey to us you’ll have to generate a JWT token in your code and pass it to our endpoint.
Create a token
The JSON Web Token (JWT) you pass to us will need the below details. This will allow us to retrieve customers’ information from our database and display the appropriate UI based on their application status.
The token Algorithm is HS256 and the token Header must contain the following:
The payload information is as follows.
| Parameter | Location | Description | Format |
|---|---|---|---|
id |
Payload | A 36-digit identifier that identifies the customer application in our databases. | guid |
customerRef |
Payload | Optional. A 36-digit identifier that identifies the customer; this value can either be provided by the partner or generated by NewDay when creating the application. | guid |
merchantId |
Payload | Optional. An identifier assigned to the merchant. | string |
exp |
Payload | The token expiration date is formatted as a number of seconds elapsed since epoch. Tokens should be valid for 5 minutes. | integer |
orderRef |
Payload | Optional. If available in a checkout journey, it will be sent when authorising the payment. | string |
offerIds |
Payload | Optional. Allows NewDay to retrieve specific offers. | string[] |
basketAmountTotal |
Payload | Mandatory for inside checkout. The total amount of the customer basket. | number (format: double) |
basketAmountIndividual |
Payload | Optional. The amount of each item in the customer basket. | number (format: double)[] |
basketDescription |
Payload | Optional. High-level basket description. | string |
loyaltyProgram |
Payload | Optional. The customer is purchasing a loyalty membership. | bool |
channel |
Payload | MerchantCheckout if your customer is applying for credit as part of a checkout journey. MerchantBrowsing should be used for a non checkout journey |
string |
upfrontPaymentAmount |
Payload | Optional. Upfront payment amount required as part of the purchase. | number(double) |
futureSaleValue |
Payload | Optional. Future sale amount defined as part of a customer purchase. | number(double) |
riskFlag |
Payload | Optional. Flag to determine if the item in the basket is considered high risk (possible values “High” / “Blank”). | string |
fulfillmentType |
Payload | Optional. Variable to determine where the basket items are to be delivered (possible values “clickAndCollect” / “homeDelivery”). | string |
deliveryAddress |
Payload | Optional. Delivery address for the purchased items. | Object (see below) |
Delivery Address Object
| Parameter | Description | Format |
|---|---|---|
postcode |
Delivery postcode | string |
Sign the token with the signature key provided by your Account Manager. This is a secret key that should be kept secure and not shared with anyone. After creating and signing the JWT token, the customer should be redirected to our handover URL. If you are embedding our application, the base URL will be specific to your organisation and will follow the format below.
NewDay will provide the brand-specific base URL and values for brand, channel, and product. The endpoint requires the following items passed as either parameters into the query string URL or as a POST request.
The code above is an example of how to implement the new POST request to access Acquisition Handover. The form is hidden and needs to be submitted automatically triggering the iframe to be populated with the response of the form action.
| Parameter | Description |
|---|---|
iframe |
Optional. Accepts values of true or false. If no value for the parameter then assumed to be false. Can be passed as part of the query string or inside the POST request. |
analyticsCookieConsent |
Optional. Accepts values of true or false. If no value for the parameter then assumed to be false. If true it allows us to activate analytics cookies. Can be passed as part of the query string or inside the POST request. |
token |
Mandatory. Can be passed as part of the query string or inside the POST request. |
Once the application matching the id in the token is fetched, NewDay will show the appropriate page based on the application status. The status post check eligibility is usually one of: quoteAccept, quoteDecline or complexRefer. If the customer is accepted they will be able to continue their journey on NewDay’s website.
You may also like:
Still have questions
Can’t find the answer to your question? Our friendly team are more than happy to help