Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

  • All test cases outlined are in our Merchant Integration environment.

  • If testing in the Production environment ensure that the refunds will be done using the AppV3 after the purchases.

Case

Summary

Description

Acceptance Criteria

A

UI Experience

A-1

Check the UI where Flexiti is allocated

Check if the client allocated enough screen space to host the Online API (Browser and Mobile)

The merchant must be allocated enough screen space to host our Online API (this test could be done together with cases D (Apply/Buy Flow)

B

Language/Accessibility

B-1

Flexiti flow initiated with the correct language

The Flexiti flow is opened with the language matching the site language chosen by the customer

  • With the site language as "French", ensure that Flexiti flow is opened with the "French" flow, and that at the end of the process, the customer is redirected back to a French merchant page;

  • With the site language as "English", ensure that Flexiti flow is opened with the "English" flow, and that at the end of the process, the customer is redirected back to an English merchant page;

  • The branding of both UIs must be corrected, please check our Marketing guidelines below:

  • Financing pages will be checked by our Marketing team and could take 10 business days for validation.

B-2

End of Flexiti flow redirects to a page with correct language

After the Flexiti flow ends (both due to success and failure), the redirected page contains the correct language matching the original language setting by the customer.

  • With the site language as "French", ensure that the redirect URL is in “French”

  • With the site language as "English", ensure that the redirect URL is in “English”

C

Security

C-1

Check the Flexiti Client ID and Client secret, and oauth token are not exposed

Check the HTML code of the merchant’s web pages where Flexiti is installed (i.e. Standalone financing page, cart, product page)

  • oauth token must not be exposed in the HTML Code

  • Client ID and Client Secret must not be exposed in the HTML Code

C-2

Oauth token initialization

An oauth token should be generated for each customer that initiates a Flexiti checkout.

When the customer clicks on “Start Flexiti checkout” or equivalent button, ensure that a new Flexiti oauth token is generated and used throughout the checkout session.

C-3

Refresh oauth token (Optional)

For a single user checkout session - Ensure that if the customer is taking a long time in checkout (I.e., over 20 mins) the user session does not expire after 20 minutes by calling the refresh token.

The oauth token is refreshed after 20 min within a single user session.

D

Information Accuracy

D-1

Full Apply/Buy flow with a Promotional purchase (ROC)

Start the Apply/Buy flow on the checkout page and ensure that the application and the purchase can be successfully completed using AB or ON as province and using a Promotional plan.

Check if our Online API is receiving the correct set of information provided by the customer at the checkout cart on the merchant website.

  • Check the Flexiti Logo at the checkout

  • Check the Merchant logo in the Apply/buy flow

  • Ensure that the right Plans and Terms are displayed.

  • Billing and shipping information must be provided

  • system/init endpoint must be called with billing and shipping values provided during the checkout cart

    • if the customer provided different billing and shipping addresses, ensure that the corresponding values populated into our API request are being passed correctly. The billing address must be passed to our billing_address, and the shipping address must be passed to our shipping_adress

    • if the merchant has the option ship-to-store the store’s address must be passed to our shipping_address field.

  • check if the parameters/body fields as name, last name, etc. are passed accurately to us as our API documentation

    • first and last name (no spaces)

    • amount requested (must be passed as number)

    • e-mail must be passed on the call

    • phone number (can't start with '0' or '1', and 10 characters in length with no additional characters)

    • province follows our API references input requirement (2-character syntax, AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, YT.)

    • postal code (6 characters, no space)

  • Check if the page is redirecting to the Success URL page set on the Dev Portal, if the transaction is declined ensure that is redirecting to the Error URL page set on the Dev Portal

  • If the flow is canceled ensure that will return to the checkout page or to the page the merchant wants to be redirect

  • Check if after the successful flow is closed the language on the page is the same as used before the Flexiti flow started.

D-2

Full Apply/Buy flow with a Regular purchase (QC)

Start the Apply/Buy flow in the checkout page and ensure that the application and the purchase can be successfully completed using QC as province and a Regular purchase.

Check if our Online API is receiving the correct set o information provided by the customer at the checkout cart on merchant website.

  • Check the Flexiti Logo at the checkout

  • Check the Merchant logo in the Apply/buy flow

  • Ensure that the right Plans and Terms are displayed with no admin fee.

  • Billing and shipping information must be provided

  • system/init endpoint must be called with billing and shipping values provided during the checkout cart

    • if the customer provided different billing and shipping addresses, ensure that the corresponding values populated into our API request are being passed correctly. The billing address must be passed to our billing_address, and the shipping address must be passed to our shipping_adress

    • if the merchant has the option ship-to-store the store’s address must be passed to our shipping_address field.

  • check if the parameters/body fields as name, last name, etc. are passed accurately to us as our API documentation

    • first and last name (no spaces)

    • amount requested (must be passed as number)

    • e-mail must be passed on the call

    • phone number (can't start with '0' or '1', and 10 characters in length with no additional characters)

    • province follows our API references input requirement (2-character syntax, AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, YT.)

    • postal code (6 characters, no space)

  • Check if the page is redirecting to the Success URL page set on the Dev Portal, if the transaction is declined ensure that is redirecting to the Error URL page set on the Dev Portal

  • If the flow is canceled ensure that will return to the checkout page or to the page the merchant wants to be redirect

  • Check if after the successful flow is closed the language on the page is the same as used before the Flexiti flow started.

D-3

Mobile order Apply/Buy flow with a Promotional purchase (ROC)

Start the Apply/Buy flow in a mobile checkout page and ensure that the application and the purchase can be successfully completed using AB or ON as province and using a Promotional plan.

  • Repeat one of the cases from D-1 or D-2 and check the UI experience observed on A-1 for Mobile.

  • No labels