Versions Compared

Old Version 8

changes.mady.by.user Arthur Zhao

Saved on

compared with

New Version Current

changes.mady.by.user Arthur Zhao

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

To use it add the refresh token (provided in the original /oauth/token call) and change the grant_type to refresh_token.

 NOTE: The API request must be passed in the x-www-form-urlencoded format, or you will receive an error.

...

This endpoint will return the Flexiti Online Flow as a Redirect URL, which can be hosted in a Modal (Preferred presentation method).

*NOTE: If you are integrating the APPLY-ONLY flow, please remove ‘/v2’ from the API URI, this will ensure that the flow opened immediately starts the application flow.

Request Parameters:

Type

Parameter

Required

Details

HEADER

authorization

Yes

  • ASCII string (40)

  • This is the word “Bearer” with a space and then the access_token given in oauth/token API response

  • Default value: Bearer {insert_bearer_token_from_oauth_here/token_api}

HEADER

x-reference-id

Yes

  • ASCII string (32)

  • GUID

  • Unique identifier for the flow for traceability purposes

PATH

client_id

Yes

  • ASCII string (100)

  • This is the Client ID given in the Developer User Account section

BODY

merchant_orderid

Optional

  • ASCII String

  • Optional field provided by the merchant (Typically the order ID in the Merchant Shopping Cart). This value can be used to request information from Flexiti regarding the transaction in the GET /notifications/merchant-order-id/{merchant-order-id} endpoint.

BODY 

is_guest

Optional

  • Boolean

  • Identifies if the current shopping cart user is running a guest session. Is useful to identify the application risk

  • Default value: false

 BODY

customer_id

Optional - Required for Buy Flow if VCC is not provided

  • ASCII string (20)

  • Value helps in identifying customer if their customer-id is already known (i.e. Merchant can save a customer’s Flexiti customer-id to be associated with their merchant profile). This makes it easier for the Flexiti Online flow to identify the customer account, taking them directly to checkout.

 BODY

vcc

Optional - Required for Buy Flow if customer_id is not provided

  • ASCII string (16)

  • The FlexitiCard Number (VCC) of the Customer. If provided, takes the customer directly to the checkout flow.

 BODY

has_previous_purchase

Optional

  • Boolean

  • Help identify if the current shopping cart user has previously purchased using your online site. This field helps us to identify if the user’s information is trusted.

 BODY

lang

Yes

  • ASCII string (5)

  • Language to be displayed to the customer: French or English

  • Possible Values: “en-CA” or “fr-CA” ← Case Sensitive.

 BODY

flow

Yes

  • ASCII string (10)

  • Flow field indicates the action the customer is looking to perform, either a:

    • stand-alone application: Customer only wants to do an application, does not want to complete purchase immediately

    • buy: customer already a FlexitiCard holder, and is able to provide the VCC #

    • apply/buy (Customer is not yet a FlexitiCard holder, and wishes to apply in the cart and proceed to purchase directly after as a single action)

  • Possible Values: “apply”, “buy”, “apply/buy”

 BODY

amount_requested

Yes

  • number (18,2)

  • Credit amount requested by the customer, means different things depending on the flow value:

    • If flow is “buy” or “apply/Buy, “amount_requested” is the cart total the customer is trying to checkout with using Flexiti.

    • If flow is “apply”, “amount_requested” is the amount the customer is applying credit for. Uses a default value parameterized in your account if no value is provided.

 BODY

salutation

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (4)

  • Salutation

  • Available values: (mr = Mr./M.), (ms = Ms./Mme.), (mrs = Mrs.), (mss = Miss.)

 BODY

email

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (75)

  • Characters allowed: Email format and [a-z A-Z 0-9 .!#$%&'+/=?^_`{|}~-]+

  • Customer Email

  • This will be used for MFA

 BODY

phone_number

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (10)

  • Customer Mobile Phone Number

    • Phone number should not start with a 0/1

    • Phone number should only contain numeric values

    • Phone numbers using only single digit will not be allowed (ex. 5555555555)

    • Phone number should be 10 digits (i.e. not include country codes)

  • This will be used for MFA via SMS

 BODY

fname

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (35)

  • Characters allowed: Alphanumeric and _ . ‘ -

  • Customer First Name

 BODY

mname

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (114)

  • Characters allowed: Alphanumeric and _ . ‘ -

  • Customer Middle Name

 BODY

lname

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (50)

  • Characters allowed: Alphanumeric and _ . ‘ -

  • Customer Last Name

 BODY

dob

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (10)

  • Format: DD/MM-YYYY

  • Customer Date of Birth

BODY

address_1

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (150)

  • Characters allowed: Alphanumeric and # _ - .

  • Customer Address Line 1

 BODY

address_2

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (143)

  • Characters allowed: Alphanumeric and # _ - .

  • Customer Address Line 2

 BODY

city

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (50)

  • Characters allowed: Alphanumeric and _ . ‘ -

  • Customer City

 BODY

province

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (2)

  • Customer Province (2 character syntax, ex. ON for Ontario)

  • Available values: AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, YT.

 BODY

postal_code

Optional - Helps pre-populate application form during “Apply” and “Apply/Buy” flow if information is available

  • ASCII string (6)

  • Customer Postal Code

BODY

billing_information.first_name

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (80)

  • Information used to match/verify the Account details on file

  • Billing Address Customer’s First Name

BODY

billing_information.last_name

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (130)

  • Information used to match/verify the Account details on file

  • Billing Address Customer’s Last Name

BODY

billing_information.address_1

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (250)

  • Information used to match/verify the Account details on file

  • Billing Address Line 1

BODY

billing_information.address_2

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (100)

  • Information used to match/verify the Account details on file

  • Billing Address Line 2

BODY

billing_information.city

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (100)

  • Information used to match/verify the Account details on file

  • Billing address city

BODY

billing_information.province

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (2)

  • Information used to match/verify the Account details on file

  • Billing Address Province (2 character syntax, ex. ON for Ontario)

  • Available values: AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, YT.

BODY

billing_information.postal_code

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (10)

  • Information used to match/verify the Account details on file

  • Billing Address Postal Code

BODY

shipping_information.first_name

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (80)

  • Information used to match/verify the Account details on file

  • Shipping Address Customer’s First Name

BODY

shipping_information.last_name

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (130)

  • Information used to match/verify the Account details on file

  • Shipping Address Customer’s Last Name

BODY

shipping_information.address_1

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (250)

  • Information used to match/verify the Account details on file

  • Shipping Address Line 1

BODY

shipping_information.address_2

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (100)

  • Information used to match/verify the Account details on file

  • Shipping Address Line 1

BODY

shipping_information.city

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (100)

  • Information used to match/verify the Account details on file

  • Shipping Address City

BODY

shipping_information.province

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (2)

  • Information used to match/verify the Account details on file

  • Shipping Address Province (2 character syntax, ex. ON for Ontario)

  • Available values: AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, YT.

BODY

shipping_information.postal_code

Yes if Flow is “Buy” or “Apply/Buy”

  • ASCII string (10)

  • Information used to match/verify the Account details on file

  • Shipping Address Postal Code

...