Skip to main content
Use this checklist as a quick guide before applying for final flow validation Web Checkout.
The guide aims at implementation with Flex, including front, nonce, payment response and final validation of result.

​
Overview

Preparation

Business requirements, credentials, sandbox environment and domains ready to start.

Technical integration

Nonce operation, loaded bookstores and parameters sent with the right format.

Functional Validation

Approved purchase, rejected and post-payment conduct reviewed from end to end.

Output to production

Revised production configuration and minimum evidence ready for final validation.

​
Suggested route

1

Prepare the environment

Confirms defined business requirements, active credentials for sandbox and return URLs or callbacks.
2

Connecting front and backend

Check that authentication to generate nonce and that Flex Loan with no mistakes on your checkout.
3

Test the purchase flow

It runs an approved and rejected purchase, validating messages, visual response and user continuity.
4

Confirms final result

Check front and confirm final status from backend to avoid closing the order with a preliminary result.
5

Requests final review

When the flow is stable in sandbox, prepare evidence and coordinate validation with the integration equipment.

​
Checklist base

1. Preparation

  • Revised business and technical requirements.
  • Credentials and testing environment available.
  • Domination, return pages and defined callbacks.
  • Checkout Flow confirmed for merchant.
  • Operating Authentication to Generate token or nonce.
  • Libraries or fronstore components loaded correctly.
  • Mandatory parameters sent with proper format.
  • Styles and visual experience reviewed within the checkout.
  • Approved transaction completed correctly.
  • Rejected transaction validated with bug management.
  • autoisation response processed at front.
  • Asynchronous methods tested if activated.
  • Final status confirmed from backend or through consultation.
  • Duples and reattempts handled securely.
  • Order or pay properly updated to your system.
  • Minimum logs available for support and diagnosis.
  • Sandbox complete with minimum evidence of evidence.
  • The production configuration revised by environment.
  • Critical flows tested with integration equipment.
  • Integration ready for live leave.

​
Minimum approval criterion

Approved purchase

At least an approved end to end validated flow.

Rejected purchase

Full Validation of Rejection and message management for the user.

Consisstore result

Confirmation between front and backend and final status of payment before production.

Introduction Flex

Check the main flow of Web Checkout with Flex.

API Nonce

Generates nonce from backend to start the form.

Test data

Use sandbox cards and scenarios to validate your integration.

API Consultation

confirms from backend the final status of the operation.