Skip to main content
← Checkout Web overviewSTEP 05 / 05
Complete the full payment flow in sandbox before requesting production validation. Confirm that the browser, backend and order status agree. Implement these recommendations as you integrate Web Checkout with Alignet One Flex.

​
Flow responsibilities

Backend

Generates tokens, issues the nonce, validates final statuses, and updates orders.

Frontend

Initializes Flex, displays checkout, and handles callbacks to improve the user experience.
Do not complete an order based only on the response shown in the browser. Confirm the final status from the backend, especially for asynchronous methods.

​
Security

Nonce and tokens

  • Generate the Access Token and nonce from the backend.
  • Do not expose credentials or tokens in JavaScript, HTML, logs, or analytics.
  • Renew temporary credentials when they expire.
  • Use responseCallback for user experience.
  • Use trackingCallback for flow traceability.
  • Use onErrorCallback for controlled messages and support.
  • For QR, Cuotéalo, or PagoEfectivo, confirm the result through a query or notification.
  • Handle pending, expired, and declined statuses.
  • Avoid duplicating orders when customers retry.
  • Show clear messages for approved, declined, pending, or canceled payments.
  • Keep the operation number available for support.
  • Validate Flex on desktop and mobile devices.
  • Test the language, close button, and visible payment methods before production.
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.

​
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.