SANDBOX cases simulation

In order to validate your Fintecture's integration, it is important to ensure all cases are covered.
Depending on the payment method you will find below some scenarios to help you reproduce the different statuses one can encounter.

Immediate transfer

💡 Note
Please note that we rely on banks' sandboxes to reach those statuses. While we do our best to keep the documentation up to date, do not hesitate to contact us in case of a problem

Console status	API status	Country	Connect scenario
Waiting	`provider_required`	All	No action needed in Connect (default status)
Waiting	`sca_required`	FR	Follow this scenario: Select Crédit Mutuel Click on "Continue on Crédit Mutuel"
Completed	`payment_created`	FR	Follow this scenario: Select Credit Mutuel Click on "Continue on Crédit Mutuel" Click on "Se connecter" Click on "Confirmer"
Unsuccessful	`payment_unsuccessful`	FR	Follow this scenario: Select Credit Mutuel Click on "Continue on Crédit Mutuel" Click on "Se connecter" Click on "Abandonner"
Pending	`payment_pending`	FR	Follow this scenario: Select CIC Privée Click on "Continue on CIC Privée" Click on "Se connecter" Click on "Abandonner"
Cancelled	`payment_cancelled`	All	No action needed in Connect (action is to be done directly in the Console or by API using the PATCH `/pis/v2/payments/session_id`)
Expired	`payment_expired`	All	No action needed in Connect (set 1 second expiry on session's creation)

Smart Transfer

💡 Note
Some Smart Transfer cases will require our event simulator to simulate customer's transactions

Console status	API status	Country	Connect scenario
Waiting	`provider_required`	All	No action needed in Connect (default status)
Waiting	`sca_required`	All	Follow this scenario: Select Bank Transfer (if payment method selector screen)
Pending	`payment_pending`	All	Follow this scenario: Select Bank Transfer (if payment method selector screen) Click on "Display the beneficiary's IBAN" Click on "Complete the bank transfer" then "I confirm"
Partial	`payment_partial`	All	Follow this scenario: Select Bank Transfer (if payment method selector screen) Click on "Display the beneficiary's IBAN" Simulate a transaction with an amount that is inferior to the requested one Click on "Complete the bank transfer" then "I confirm"
Completed	`payment_created`	All	Follow this scenario: Select Bank Transfer (if payment method selector screen) Click on "Display the beneficiary's IBAN" Simulate a transaction with the requested amount Click on "Complete the bank transfer" then "I confirm"
Overpaid	`payment_created`	All	Follow this scenario: Select Bank Transfer (if payment method selector screen) Click on "Display the beneficiary's IBAN" Simulate a transaction with an amount that is superior to the requested one Click on "Complete the bank transfer" then "I confirm"
Cancelled	`payment_cancelled`	All	No action needed in Connect (action is to be done directly in the Console or by API using the PATCH `/pis/v2/payments/session_id`)
Expired	`payment_expired`	All	No action needed in Connect (set 1 second expiry on session's creation)

Buy Now Pay Later

💡 Note
To facilitate testing the bnpl scenarios, the interactions with the insurance api are mocked for the SIRENs below, each providing a possible outcome. Those SIRENs have to be either used on creation (Console / API) or directly in Connect (CMS)

Console status	API status	Country	SIREN	Scenario	Insurer Quotation	Cover	Settlement
Waiting	`provider_required`	All	All	No action needed in Connect (default status)	-	-	-
Waiting	`provider_required`	All	`000000001`	Generate a Connect session (using Console, CMS or the API) for indicated SIREN Simulate the customer flow using the Connect session (quotation will be refused)	KO	-	-
Waiting	`sca_required`	All	`000000002`	Generate a Connect session (using Console, CMS or the API) for indicated SIREN Simulate the whole customer flow using the Connect session (cover activation will be refused)	OK	KO	-
Pending	`order_created`	All	`000000003`	Generate a Connect session (using Console, CMS or the API) for indicated SIREN Simulate the whole customer flow using the Connect session Settlement will be scheduled and refused	OK	OK	-
Unsuccessful	`payment_unsuccessful`	All	`N/A`	Not reproductible	-	-	-
Completed	`payment_created`	All	`000000000`	Generate a Connect session (using Console, CMS or the API) for indicated SIREN Simulate the whole customer flow using the Connect session Settlement will be scheduled to proceed successfully 10 mins later	OK	OK	OK
Completed	`payment_created`	All	`000000004`	Generate a Connect session (using Console, CMS or the API) for indicated SIREN Simulate the whole customer flow using the Connect session and sign the e-mandate Settlement will be scheduled to proceed successfully 10 mins later	OK	OK	OK
Cancelled	`payment_cancelled`	All	All	No action needed in Connect (action is to be done directly in the Console or by API using the PATCH `/pis/v2/payments/session_id`)	-	-	-
Expired	`payment_expired`	All	All	No action needed in Connect (set 1 second expiry on session's creation)	-	-	-