Online Channel Test Cases

Info
All test cases outlined are in our Merchant Integration environment

Case	Summary	Description	Acceptance Criteria
A	Merchant Configuration
A-1	Validate API credentials - Client ID	Merchant's API credentials (Client ID and Client Secret) are present and valid in the Flexiti Developer Portal	Merchant is able to successfully authenticate with Flexiti API using these credentials
A-2	Validate API credentials - Client Secret	Merchant's API credentials (Client ID and Client Secret) are present and valid in the Flexiti Developer Portal	Merchant is able to successfully authenticate with Flexiti API using these credentials
A-3	Validate API Base URL is referencing correct Flexiti environment	Merchant's environment should reference the correct Flexiti environments	Merchant Integration API requests are sent to https://posapi-mi.flexiti.fi/flexiti/pos-api/ Training API requests are sent to https://posapi-training.flexiti.fi/flexiti/pos-api/ Production API requests are sent to https://posapi.flexiti.fi/flexiti/pos-api/

B

Merchant Authentication and Login

B-1

Unsuccessfully Authenticate with Flexiti's POS API - invalid client

Test Case: Access the API with

Code Block
'client_id=xxxxxx'

POST /oauth/token - 400 - invalid_client

B-2

Unsuccessfully call an endpoint - Invalid token

Test Case: Call the /token endpoint to generate a token and then call a different endpoint after the "expires_in" value expires.

Any endpoint - 401 - unauthorized

B-3

Unsuccessfully call an endpoint - wrong scope

Test Case: Attempt to call the following endpoints with an token that has a “customer” scope:

GET


A-4	Validate Disclaimers and Links	Verify that all disclaimers, pdfs, and links are working correctly	Verified by Marketing Team
A-5	Validate Field Lengths	Compare accepted field lengths with parameter lengths	Verified by Implementation Team
A-6	Verify that any merchant-scope API calls are made from the Merchant Server-side (i.e. POST oauth/token, /capture, GET /authorizations, /captures, /lookup, /search)	Ensure that all API Endpoints that require a merchant scope are made from the server-side	Verify that any merchant scope API calls are made from the merchant server-side
A-7	Verify that the APIs are called with the correct scope	Verify that the following API endpoints are called with the “customer” scope: POST /client-id/{client_id}/

customers/search

i18n
GET /client-id/{client_id}/

customers/lookup

terms-and-conditions
POST /client-id/{

clientId

client_id}/

authorization/{authorizationId}/release

customers/driverslicense
POST /client-id/{

clientId

client_id}

/authorization

widget/init
POST /client-id/{

authorizationId

client_id}/

capture

apply
POST /client-id/{

clientId

client_id}/

authorization

accounts/{

authorizationId

account_number}/

capture/{captureId}/return

close
POST /client-id/{client_id}/accounts/{account_number}/

refund

calculate-interest

GET

POST /client-id/{

clientId

client_id}/

authorizations

GET /client-id/{clientId}/authorization/{authorizationId}

GET

account/{account_number}/verify
POST /client-id/{

clientId}/captures

GET /client-id/{client_id}/customers/search - 403 - forbidden

GET /client-id/{client_id}/customers/lookup - 403 - forbidden

POST /client-id/{clientId}/authorization/{authorizationId}/release - 403 - forbidden

client_id}/authorization

Verified by Implementation Team

B

Merchant Authentication and Login

B-1

Unsuccessfully Authenticate with Flexiti's POS API - invalid client

Test Case: Access the API with

Code Block
'client_id=xxxxxx'

POST /oauth/token - 400 - invalid_client

B-2

Unsuccessfully call an endpoint - Invalid token

Test Case: Call the /token endpoint to generate a token and then call a different endpoint after the "expires_in" value expires.

Any endpoint - 401 - unauthorized

B-3

Unsuccessfully call an endpoint - wrong scope

Test Case: Attempt to call the following endpoints with an token that has a “customer” scope:

GET /client-id/{client_id}/customers/search
GET /client-id/{client_id}/customers/lookup
POST /client-id/{clientId}/authorization/{authorizationId}/release
POST /client-id/{clientId}/authorization/{authorizationId}/capture

- 403 - forbidden

POST /client-id/{clientId}/authorization/{authorizationId}/capture/{captureId}/return

- 403 - forbidden

POST /client-id/{client_id}/accounts/{account_number}/refund

- 403 - forbidden

GET /client-id/{clientId}/authorizations

- 403 - forbidden

GET /client-id/{clientId}/authorization/{authorizationId}

- 403 - forbidden

GET /client-id/{clientId}/captures

- 403 - forbidden

B-4

Any API call - Session time out

Test Case:

Code Block{{pos_url}}/flexiti/pos-api/v2.5/

GET /client-id/{client_id}/customers/search - 403 - forbidden
GET /client-id/{

{

client_id}

}

/customers/lookup

?account_number=0001GET {{pos_url}}/flexiti/pos-api/v2.5

- 403 - forbidden
POST /client-id/{clientId}/authorization/{authorizationId}/release - 403 - forbidden
POST /client-id/{clientId}/authorization/{authorizationId}/capture - 403 - forbidden
POST /client-id/{clientId}/authorization/{authorizationId}/capture/{captureId}/return - 403 - forbidden
POST /client-id/{

{

client_id}

}

/

customers

accounts/

lookup?

{account_number

=0001 - 504 - GATEWAY_TIMEOUT

B-5

Successfully Authenticate with Flexiti's POS API

Test Case: Use the correct “client_secret” and “client_id” from the Developer Portal to access the Flexiti API.

POST /oauth/token - 200

C

Customer Apply & Apply/Buy Flows

C-1 - /init Endpoint (Widget)

C-1.1

Customer already has an account that needs to be to activated

Test Case:

Code Block

{
    "customer_identification": {
        "personal_information": {
            "first_name": "Alice",
            "middle_name": "",
            "last_name": "Tester",
            "dob": "1950-05-12",
            "postal_code": "L1N7L1"
        }
    },
    "flow": "apply",
    "email": "test@example.com",
    "phone_number": 5550097339,
    "address_1": "225 HICKORY STREET NORTH #306",
    "city": "Whitby",
    "province": "ON",
    "tos_agreement": true
}

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "activation" type: "flx-success" verified: false

C-1.2

Customer submits a new application and Flexiti identifies the customer has an existing account.

Test Case:

Code Block

{
    "customer_identification": {
        "personal_information": {
            "first_name": "CERTIFICATION",
            "middle_name": "",
            "last_name": "EXISTING",
            "dob": "1980-01-01",
            "postal_code": "M6S2R5"
        }
    },
    "flow": "apply",
    "email": "test@example.com",
    "phone_number": 5551231231,
    "address_1": "123 Any Street",
    "city": "Montreal",
    "province": "QC",
    "tos_agreement": true
}

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "purchase" type: "flx-success" verified: false

C-1.3

Customer submits a new application (widget)

Test Case: Use a new application payload but pass the key below as the middle name:

Code Block
"middle_name": "A-RR_L"

POST

}/refund - 403 - forbidden
GET /client-id/{clientId}/authorizations - 403 - forbidden
GET /client-id/{clientId}/authorization/{authorizationId} - 403 - forbidden
GET /client-id/{clientId}/captures - 403 - forbidden

B-4

Any API call - Session time out

Test Case:

Code Block
{{pos_url}}/flexiti/pos-api/v2.5/client-id/{{client_id}}/customers/lookup?account_number=0001

GET {{pos_url}}/flexiti/pos-api/v2.5/client-id/{{client_id}}

/widget/init - 200

Code Block
action: "apply" type: "flx-success" verified: true/false

Send the application payload through the POST /client-id/{client_id}/apply

/customers/lookup?account_number=0001 - 504 - GATEWAY_TIMEOUT
B-5	Successfully Authenticate with Flexiti's POS API	Test Case: Use the correct “client_secret” and “client_id” from the Developer Portal to access the Flexiti API.	POST /oauth/token - 200
C	Customer Apply & Apply/Buy Flows
C-1	Apply & Apply/Buy - Widget - /init endpoint
C-1.

4

1

Customer

submits a new application that will be declined due to a derogatory status’s on an existing account.

already has an account that needs to be to activated

Test Case:

Code Block
{ "customer_identification": { "personal_information": { "first_name": "Prodip", "middle_name":

{

 "",
            "last_name": "Das",

first_name

dob": "

CERTIFICATION

1967-06-01",
            "

middle

postal_

name

code": "

",

M1J2A7"
        }
    },
    "

last_name

flow": "

04TEST

apply",
    "email": "test@example.com",
    "phone_number": 5550097339,
    "

dob

address_1": "

1930-01-01

225 HICKORY STREET NORTH #306",

"city": "Whitby",
    "

postal_code

province": "

M6S2R5

ON",
    "tos_agreement":

} }, "flow": "apply", "email": "test@example.com", "phone_number": 5551231231, "address_1": "123 Any Street", "city": "Toronto", "province": "ON", "tos_agreement": true }

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "apply" type: "flx-success" verified: false

Send the application payload through the POST /client-id/{client_id}/apply endpoint

C-1.5

Customer attempts an application but there is an IT related error.

To be performed with Flexiti Assistance.

Test Case: Use a new application payload but pass the key below as the middle name:

Code Block
"middle_name": "D-ENST_TEXTMAGIC",

POST /client-id/{{client_id}}/widget/init - 409 -application_create_error

Code Block
action: "retry" type: "flx-success" verified: false

C-1.5

Customer initiates and then fails verification

Test Case: Create Application with new information and enter 1111 as the pin 4 times.

true
}

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "activation" type: "flx-success" verified: false

C-1.2

Customer submits a new application and Flexiti identifies the customer has an existing account.

Test Case:

Code Block

{
    "customer_identification": {
        "personal_information": {
            "first_name": "CERTIFICATION",
            "middle_name": "",
            "last_name": "EXISTING",
            "dob": "1980-01-01",
            "postal_code": "M6S2R5"
        }
    },
    "flow": "apply",
    "email": "test@example.com",
    "phone_number": 5551231231,
    "address_1": "123 Any Street",
    "city": "Montreal",
    "province": "QC",
    "tos_agreement": true
}

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "

apply

purchase"
type: "flx

-success" verified: falseSend the application payload through the POST /client-id/{client_id}/apply endpoint

-success"
verified: false

C-1.

6

Test Case:

Code Block{ "customer_identification": { "personal_information": { "first_name": "Jeremy", "

3

Customer submits a new application (widget)

Test Case: Use a new application payload but pass the key below as the middle name:

Code Block
"middle_name": "

", "last_name": "Smith", "dob": "1930-01-01", "postal_code": "M6S2R5" } }, "flow": "apply", "email": "test@example.com", "phone_number": 5551231231, "address_1": "123 Any Street", "city": "Toronto", "province": "ON", "tos_agreement": true }

C-1.7

Application submission fails - Terms and Conditions required

A-RR_L"

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "apply" type: "flx-success" verified: true/false

Send the application payload through the POST /client-id/{client_id}/apply endpoint

C-1.4

New Flexiti user initiates and completes application flow - pending

Test Case: Use a new application payload but pass the key below as the middle name:

Code Block
"middle_name": "P-CREDIT"

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "apply" type: "flx-success" verified: true/false

Send the application payload through the POST /client-id/{client_id}/apply endpoint

C-1.5

New Flexiti user initiates and completes application flow - decline

Test Case: Use a new application payload but pass the key below as the middle name:

Code Block
"middle_name": "D-CREDIT"

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "apply" type: "flx-success" verified: true/false

Send the application payload through the POST /client-id/{client_id}/apply endpoint

C-1.6

Customer submits a new application that will be declined due to a derogatory status’s on an existing account.

Test Case:

Code Block
{ "customer_identification": { "personal_information": { "first_name": "

Howard

CERTIFICATION",
            "middle_name": "",
            "last_name": "

Billings

04TEST",
            "dob": "1930-01-01",
            "postal_code": "M6S2R5"
        }
    },
    "flow": "apply",
    "email": "test@example.com",
    "phone_number": 5551231231,
    "address_1": "123 Any Street",
    "city": "Toronto",
    "province": "ON",
    "tos_agreement":

"city": "Toronto", "province": "ON", "tos_agreement": false }

C-2 - /Apply Endpoint

C-2.1

Application submission fails - invalid inputs

Test Case:

Code Block

{
  "amount_requested": 5000,
  "phone_number": "5551231231",
  "language": "en-CA",
  "salutation": "mr",
  "first_name": "Garry",
  "middle_name": "",
  "last_name": "Blue",
  "dob": "1980-01-01",
  "address_1": "123 Any Street",
  "address_2": "Apt C",
  "city": "Montreal",
  "province": "QC",
  "postal_code": "A1A0H1",
  "monthly_housing_expenses": 1000,
  "input_type": "manual",
  "personal_income": "abc",
  "household_income": 223123,
  "housing_type": "Rent",
  "email": "email@address.com",
  "occupation_id": "FE",
  "occupation_title": "Baker",
  "employer_name": "Tasty Bakery",
  "employer_phone": "1231231231",
  "sin": "",
  "security_qid": "8",
  "security_answer": "Horse",
   "piw": "Cloud",
  "tos_agreement": true
}

POST /client-id/{client_id}/apply - 409 - "wrong_inputs"

Code Block

{
    "url": "/flexiti/pos-api/v2.5/client-id/{client-id}/apply",
    "message": "Some inputs are wrong!",
    "error": "wrong_inputs",
    "field_errors": [
        {
            "param": "personal_income",
            "msg": "invalid",
            "value": "abc"
        }
    ]
}

C-2.2

Application submission fails - Terms and Conditions required

Test Case: Any application where "tos_agreement": false

true
}

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "apply" type: "flx-success" verified: false

Send the application payload through the POST /client-id/{client_id}/apply endpoint

C-1.7

Customer attempts an application but there is an IT related error.

To be performed with Flexiti Assistance.

Test Case: Use a new application payload but pass the key below as the middle name:

Code Block
"middle_name": "D-EMAIL_DBL_TIMEOUT",

POST /client-id/{{client_id}}/widget/init - 409 -application_create_error

Code Block
action: "retry" type: "flx-success" verified: false

C-1.8

Customer initiates and then fails verification

Test Case: Create Application with new information and enter 1111 as the pin 4 times.

POST /client-id/{{client_id}}/widget/init - 200

Code Block
action: "apply" type: "flx-success" verified: false

Send the application payload through the POST /client-id/{client_id}/apply endpoint

C-2

Apply & Apply/Buy - Application - /apply endpoint

C-2.1

Application submission fails - invalid inputs

Test Case:

Code Block

{
  "amount_requested": 5000,
  "phone_number": "5551231231",
  "language": "en-CA",
  "salutation": "mr",
  "first_name": "Garry",
  "middle_name": "",
  "last_name": "Blue",
  "dob": "1980-01-01",
  "address_1": "123 Any Street",
  "address_2": "Apt C",
  "city": "Montreal",
  "province": "QC",
  "postal_code": "A1A0H1",
  "monthly_housing_expenses": 1000,
  "input_type": "manual",
  "personal_income": "abc",
  "household_income": 223123,
  "housing_type": "Rent",
  "email": "email@address.com",
  "occupation_id": "FE",
  "occupation_title": "Baker",
  "employer_name": "Tasty Bakery",
  "employer_phone": "1231231231",
  "sin": "",
  "security_qid": "8",
  "security_answer": "Horse",
   "piw": "Cloud",
  "tos_agreement": true
}

POST /client-id/{client_id}/apply - 409 -

"

tos

wrong_

agreement_required

inputs"

Code Block
{ "url": "/flexiti/pos-api/v2.5/client-id/{client-id}/apply", "message":

"It has been following errors:

"Some inputs are wrong!",
    "error": "wrong_inputs",

"error

"field_errors": [
        {
            "param": "

tos_agreement_required"

personal_income",
            "msg": "invalid",
            "value": "abc"
        }
    ]
}

D

C-

9New Flexiti user initiates and completes application flow - approval

2.2

Application submission fails - Terms and Conditions required

Test Case: Any application

with

where "

middle

tos_

name

agreement":

"A-RR_L",

false

POST /client-id/{client_id}/apply -

200 - Approved response

D-10

New Flexiti user initiates and completes application flow - pending

Test Case: Any application with "middle_name

409 - "tos_agreement_required"

Code Block
{ "url": "

P-CREDIT",POST

/flexiti/pos-api/v2.5/client-id/{client

_

-id}/apply

- 200 - Pending response

D-11

New Flexiti user initiates and completes application flow - decline

Test Case: Any application with"middle_name": "D-MISSING_INFO",

POST /client-id/{client_id}/apply - 200 - Declined response

D-7

New user initiates and fails application flow - SIN number format

",
    "message": "It has been following errors:",
    "error": "tos_agreement_required"
}

C-2.3

New Flexiti user initiates and completes application flow - approval

Test Case: Any application

where "sin": 12312

POST /client-id/{client_id}/apply - 409 - "wrong_inputs"

Code Block{ "url": "/flexiti/pos-api/v2.5/

with "middle_name": "A-RR_L",

POST /client-id/{client

-

_id}/apply

", "message": "Some inputs are wrong!", "error": "wrong_inputs", "field_errors": [ { "param": "sin", "msg": "invalid", "value": 12312 } ] }

D-8

New user initiates and fails application flow - Third Party time out

- 200 - `Approved response`
C-2.4	New Flexiti user initiates and completes application flow - pending	Test Case: Any application with `"middle_name": "P-CREDIT",`	POST /client-id/{client_id}/apply - 200 - `Pending response`
C-2.5	New Flexiti user initiates and completes application flow - decline	Test Case: Any application with`"middle_name": "D-`

EMAIL_DBL_TIMEOUT

CREDIT",

POST /client-id/{client_id}/apply

- 409 - application_create_error

D-9

New Flexiti user initiates and completes application flow - approval

Test Case: Any application with "middle_name": "A-RR_L",

- 200 - `Declined response`
C-3	Apply/Buy - Plan Section - /calculate-interest endpoint
See D-2
C-4	Apply/Buy - Purchase - /authorization endpoint
See D-3
D	Customer Buy Flow
D-1	Buy - Widget - /init endpoint
D-1.1	Customer initiates and then fails verification - account not found	Test Case: Account #: `1234` flow: purchase	POST /client-id/{{client_id}}/widget/

apply

init -

200 - Approved response

D-10

New Flexiti user initiates and completes application flow - pending

Test Case: Any application with "middle_name": "P-CREDIT",

POST

404 - not_found

Code Block
{ "url": "/flexiti/pos-api/v2.5/client-id/{client_id}/

apply - 200 - Pending response

D-11

New Flexiti user initiates and completes application flow - decline

Test Case: Any application with"middle_name": "D-MISSING_INFO",POST /

account/123/verify",
    "message": "It has been following errors:",
    "error": "not_found"
}

D-2

Buy - Plan Section - /calculate-interest endpoint

D-2.1

Customer's Plans and Terms not displayed - account not found

Test Case:

Account #: 1234

POST /pos-api/client-id/{client_id}

/apply - 200 - Declined response

C-3 - /Authorization Endpoint

E

Customer Buy Flow

E-1

Customer initiates and then fails verification - account not foundPOST

/accounts/{account_number}/calculate-interest - 404 - "not_found"

D-2.2

Customer's Plans and Terms displayed (QC Customer Account)

Test Case:

Account #:

1234 / FlexitiCard #: 9999999999999999

flow: purchase

116991631

POST /pos-api/client-id/{

{

client_id}/accounts/{account_number}/

widget/init - 404 - not_found Code Block{ "url": "/flexiti/pos-api/v2.5

calculate-interest - 200

D-2.3

Customer's Plans and Terms displayed (ROC Customer Account)

Test Case: Merchant generated from test data in sandbox account

Account #: 116991632

POST /pos-api/client-id/{client_id}

/account/123/verify", "message": "It has been following errors:", "error": "not_found" }G-

/accounts/{account_number}/calculate-interest - 200
D-3	Buy - Purchase - /authorization endpoint
D-3.1	Customer initiates and then

cancels Flexiti Authorization

To be handled by Merchant’s implementation design, the customer should be able to cancel the transaction process at any time up to the authorization call.

Customer successfully cancels the transaction flow prior to the

fails Flexiti authorization - not verified

Test Case:

Incorrectly input dynamic pin or security question and answer in the widget /init 3 times
Then attempt an authorization using that account

POST /client-id/{client-id}/authorization

requestG-

- 409 - not_verified
D-3.2	Customer initiates and then fails

verification

Flexiti authorization -

account

Account Number not found

Test Case:

Account #: 1234 / FlexitiCard #: 9999999999999999
flow: purchase

POST /client-id/{{client_id}}/widget/init - 404 - not_found

Code Block{ "url": "/flexiti/pos-api/v2.5/

Merchant generated from test data in sandbox account

Account #: 1234

POST /client-id/{client

_

-id}/

account/123/verify", "message": "It has been following errors:", "error": "

authorization - 404 - not_found

" }

G

D-3.3

Customer initiates and then fails Flexiti authorization -

missing verification code

user not able to purchase

Test Case: Merchant generated from test data in sandbox account

verification_code: 9999

FlexitiCard #: 2374980012865132
Account #: 116991633

POST /client-id/{client-id}/authorization - 409 -

verification_code_requiredG-

user_not_able_to_purchase
D-3.4	Customer initiates and then fails Flexiti authorization -

Account Number

not

found

enough credit

Test Case: Merchant generated from test data in sandbox account

Account #: 1234

Request an authorization amount larger than the test accounts open to buy

POST /client-id/{client-id}/authorization -

404

409 -

not

credit_

foundG-

exceeded
D-3.5	Customer initiates and then fails Flexiti authorization -

user not able to purchase

invalid plan ID

Test Case: Merchant generated from test data in sandbox account

Account #: 116991633 / FlexitiCard #: 2374980012865132

POST /client-id/{client-id}/authorization - 409 -

user

plan_term_not_

able_to_purchaseG-6

set
D-3.5	Customer initiates and then fails Flexiti authorization -

not enough credit

invalid term

Test Case: Merchant generated from test data in sandbox account

Account #: provided on request

POST /client-id/{client-id}/authorization - 409 -

credit_exceededG-

plan_term_not_set
D-3.7	Customer initiates and then fails Flexiti authorization -

invalid

plan

ID

not available to customer

Test Case: Merchant generated from test data in sandbox account

Account #: provided on request

POST /client-id/{client-id}/authorization - 409 - plan_term_not_

set

available

G

D-3.8

Customer

initiates and then fails Flexiti authorization - invalid term

successfully performs a regular purchase authorization (QC Account)

Test Case: Merchant generated from test data in sandbox account

Account #: provided on request

POST /client-id/{client-id}/authorization -

409 - plan_term_not_set

G-9

Customer initiates and then fails Flexiti authorization - plan not available to customer

200

D-3.9

Customer successfully performs a promotional purchase authorization (QC Account)

Test Case: Merchant generated from test data in sandbox account

Account #: provided on request

POST /client-id/{client-id}/authorization -

409 - plan_term_not_availableG-

200
D-3.10	Customer successfully performs a regular purchase authorization (

QC Account

ROC account)

Test Case: Merchant generated from test data in sandbox account

Account #: provided on request

POST /client-id/{client-id}/authorization - 200

G

D-3.11

Customer successfully performs a promotional purchase authorization (

QC

ROC Account)

Test Case: Merchant generated from test data in sandbox account

Account #: provided on request

POST /client-id/{client-id}/authorization - 200

G

D-3.12

Customer successfully performs a regular purchase authorization (ROC account)

Response in "account_avs" with customer address matching values

Test Case: Merchant generated from test data in sandbox

accountAccount #: provided on request

account	POST /client-id/{client-id}/authorization - 200
D-3.13	Billing and Shipping Information should be separately passed in and matching the expected values	Test Case: Run an authorization where the billing and shipping information are not matching each other	POST /client-id/{client-id}/authorization - 200

G-13

Customer successfully performs a promotional purchase authorization (ROC Account)

Test Case: Merchant generated from test data in sandbox account

Account #: provided on request

Verify with the Flexiti implementation team that the request received has the different corresponding billing & shipping info.

D3.14

In-store pick-ups: If in-store pick-ups is desired for online, the shipping address passed in is the store address.

Test Case: Process a transaction for instore pickup (There’s no difference from the Flexiti API’s perspective)

POST /client-id/{client-id}/authorization - 200

G-14

Response in "account_avs" with customer address matching values

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{client-id}/authorization - 200

H

Verify with the Flexiti implementation team & the merchant dev team that the shipping info received by Flexiti is that of the pick-up store info.
E	Merchant Order Management

H

E-1

Unsuccessfully release an authorization - wrong transaction ID

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/release - not_found

H

E-2

Unsuccessfully release an authorization - total requested more than authorization

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/release - auth_amount_exceeded

H

E-3

Unsuccessfully release an authorization - authorization ended

Test Case: Merchant generated from test data in sandbox account with Flexiti assistance.

POST /client-id/{clientId}/authorization/{authorizationId}/release - authorization_ended

H

E-4

Unsuccessfully release an authorization - employee does not have permission

Test Case: Merchant generated from test data in sandbox account with Flexiti assistance

POST /client-id/{clientId}/authorization/{authorizationId}/release - not_permitted

H

E-5

Perform a full release of an Authorization

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/release - 200

H

E-6

Perform a partial release of an Authorization

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/release - 200

H

E-7

Unsuccessfully capture an authorization - customer not able to purchase

Test Case: Merchant generated from test data in sandbox account with Flexiti assistance.

POST /client-id/{clientId}/authorization/{authorizationId}/capture - 409 - not_permitted

H

E-8

Unsuccessfully capture an authorization - authorization not capturable

Test Case: Merchant generated from test data in sandbox account with Flexiti assistance.

POST /client-id/{clientId}/authorization/{authorizationId}/capture - 409 - not_permitted

H

E-9

Unsuccessfully capture an authorization - wrong authorization ID

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/capture - 404 - not_found

H

E-10

Unsuccessfully capture an authorization - amount greater than authorization

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/capture - 409 - auth_amount_exceeded

H

E-11

Fully Capture an authorization

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/capture - 200

H

E-12

Partially Capture an authorization

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/capture - 200

H

E-13

Unsuccessfully refund a captured regular purchase - customer account not found

Test Case:

Account #: 1234

POST /client-id/{client_id}/accounts/{account_number}/refund - 404 - not_found

H

E-14

Unsuccessfully refund a captured regular purchase - refund exceeds limit

Test Case: Merchant generated from test data in sandbox account with Flexiti assistance.

POST /client-id/{client_id}/accounts/{account_number}/refund - 409 - refunds_limit_exceeded_amount

H

E-15

Perform a full refund of a captured regular purchase

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{client_id}/accounts/{account_number}/refund - 200

H

E-16

Perform a Partial Refund of a captured regular purchase

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{client_id}/accounts/{account_number}/refund - 200

H

E-17

Unsuccessfully return a captured promotional purchase - wrong authorization ID

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/capture/{captureId}/return

H

E-18

Unsuccessfully return a captured promotional purchase - return exceeds limit

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/capture/{captureId}/return

H

E-19

Perform a full Return on a captured promotional purchase

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/capture/{captureId}/return - 200

H

E-20

Perform a Partial return of a captured promotional purchase

Test Case: Merchant generated from test data in sandbox account

POST /client-id/{clientId}/authorization/{authorizationId}/capture/{captureId}/return - 200

H

E-21

Unsuccessfully view list of Authorizations available for capture - wrong dates

Test Case: Merchant generated from test data in sandbox account

GET /client-id/{clientId}/authorizations - 409 - date_from_bigger_than_date_to

H

E-22

View a list of Authorizations available for capture

Test Case: Merchant generated from test data in sandbox account

GET /client-id/{clientId}/authorizations - 200

H

E-23

Unsuccessfully view an authorization - authorization not found

Test Case: Merchant generated from test data in sandbox account

GET /client-id/{clientId}/authorization/{authorizationId} - 409 - not_found

H

E-24

View an authorization

Test Case: Merchant generated from test data in sandbox account

GET /client-id/{clientId}/authorization/{authorizationId} - 200

H

E-25

Unsuccessfully View a list of captures - wrong dates

Test Case: Merchant generated from test data in sandbox account

GET /client-id/{clientId}/captures - 409 - date_from_bigger_than_date_to

I

E-26

View a list of captures

Test Case: Merchant generated from test data in sandbox account

GET /client-id/{clientId}/captures - 200

Ac

Versions Compared

Old Version 10

New Version Current

Key

Online Channel Test Cases

Case

A

Merchant Configuration

B

Merchant Authentication and Login

C

Customer Apply & Apply/Buy Flows

C-1

Apply & Apply/Buy - Widget - /init endpoint

C-2

Apply & Apply/Buy - Application - /apply endpoint

C-3

Apply/Buy - Plan Section - /calculate-interest endpoint

C-4

Apply/Buy - Purchase - /authorization endpoint

D

Customer Buy Flow

D-1

Buy - Widget - /init endpoint

D-2

Buy - Plan Section - /calculate-interest endpoint

D-3

Buy - Purchase - /authorization endpoint

E

Merchant Order Management

Page Comparison

Versions Compared

Old Version 10

New Version Current

Key

Case

A

Merchant Configuration

B

Merchant Authentication and Login

C

Customer Apply & Apply/Buy Flows

C-1

Apply & Apply/Buy - Widget - /init endpoint

C-2

Apply & Apply/Buy - Application - /apply endpoint

C-3

Apply/Buy - Plan Section - /calculate-interest endpoint

C-4

Apply/Buy - Purchase - /authorization endpoint

D

Customer Buy Flow

D-1

Buy - Widget - /init endpoint

D-2

Buy - Plan Section - /calculate-interest endpoint

D-3

Buy - Purchase - /authorization endpoint

E

Merchant Order Management