Overview

The Flexiti widget is used in for the Online channel only, and is for high orchestration scenarios, such as customer verification , using and multiple account selection. It is a UI component as that’s an entry point to the Flexiti credit application and purchase flows.

Widget Sequence Diagram

Important: We strongly recommend using POS API requests at server side.

Example Purchase Flow

...

Image Added

Implementation Steps

Follow these steps in order to implement the Flexiti widget on your website:

1. Create an account in the Flexiti Developer Portal if you haven’t already.

   1. Training Environment: https://developer.flexiti.fi/

   2. Merchant Integration Environment: https://developer-mi.flexiti.fi/

2. Set the Trust URL in the Developer Portal for the environment you are implementing in.

   1. This ensures we will recognize where the website traffic is coming from

   2. Make sure there is no trailing slash (/) at the end of the URL. For example, use https://example.com instead of http://example.com/

3. Implement the Flexiti Widget as follows:

   1. Request Access Token (see Oauth 2 Authorization Method and Refresh Token)Login As Merchant (see POST /client-id/{client_id}/merchants/login)

      1. client_credential

      2. refresh_token

   2. Implement the SDK Object (see SDK Object)

   3. Implement the Flexiti SDK Init Method (see POST /client-id/{clientId}/widget/init)

   4. For additional information on event communication and general rules for the widget see Widget Communication Events.

4. Implement the TRAINING / Test version of the code on your Staging website (using your Training or Merchant Integration credentials) and test thoroughly.

   1. Once you are ready to launch we will perform UAT testing in your staging environment and issue your Flexiti production credentials.

5. Implement the PRODUCTION / Live version of the code on your Production website using your Flexiti production credentials and review

Widget Sequence Diagram

Example Application Flow

Important: We strongly recommend using POS API requests at server side.

...

Image Removed

Example Purchase Flow

...

Widget Sections

...