Variations of the Apply Flow

Apply can be a standalone flow or it can be a sub-flow within the Checkout flow.

• Standalone flow: The standalone Apply flow can be performed via the SDK only or via a hybrid integration (APIs and SDK).
• Sub-flow: Likewise, Apply as a sub-flow of Checkout (in the Apply and Buy Later model) can be performed via the SDK only or via a hybrid integration (APIs and SDK).
  In the Apply and Buy Later model, the Apply sub-flow is completed and later after approval, the session is resumed and the Checkout flow is completed.

These variations of the Apply flow are detailed below.

📘

The application step may include a prequalification offer before the full offer.

Prequalification: The prequalification request is based on consumer-submitted data that does not affect the consumer credit history. The lender executes a credit check based solely on the information provided to the lender. The lender may conditionally accept or decline the request. If the lender conditionally accepts the request, it provides an estimation of the funding that will be provided to the consumer. Prequalification is a tool to encourage the consumer to continue the flow.

Full Offer: The full offer request aims to get a final financing approval. The consumer is requested to provide detailed information and sign the terms and conditions. Once the offer is accepted, the consumer can buy the merchandise with the financing.

Standalone Apply - SDK Only

1. When the consumer clicks the Apply button, the SDK is opened and the flowType is Apply.
2. A sequence of screens is completed via the SDK.

Standalone Apply - APIs and SDK

In a hybrid integration, a typical Apply flow proceeds as follows:

1. Personal information of the consumer is gathered and the GET /v2/checkout/accounts endpoint is called to retrieve the account of the consumer.
2. For existing consumers, the response returns a message that authentication is required. If the consumer is new, skip to step 7.
3. The GET /v2/checkout/applications/{applicationId}/token endpoint is called to retrieve an interactive sessionToken that can be used later to resume the session.
4. The sessionToken is returned.
5. The SDK is called to present the OTP authentication flow.
6. The authentication completion status code is returned.
7. The GET /v2/checkout/applications/{applicationId}/accounts endpoint is called to get offers.
8. Offers are returned and presented to the consumer.

Apply as a Sub-flow of Checkout in Apply and Buy Later

In the Apply and Buy Later model, the Apply sub-flow is similar to the standalone Apply flow (either SDK only or a hybrid integration of APIs and SDK). Both are detailed above. The remaining Checkout portion of Apply and Buy Later is detailed in the Checkout Overview.