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 before requesting final validation of your Web Checkout flow.
This guide covers Flex implementations, including the frontend, nonce, payment response and final result validation.

​
Checklist base

1. Preparation

  • Business and technical requirements reviewed.
  • Credentials and testing environment available.
  • Domain, return pages and callbacks defined.
  • Checkout flow confirmed for the merchant.
  • Authentication working to generate a token or nonce.
  • Libraries or frontend components loaded correctly.
  • Mandatory parameters sent with proper format.
  • Styles and visual experience reviewed within the checkout.
  • Approved transaction completed correctly.
  • Declined transaction validated with error handling.
  • Authorization response processed by the frontend.
  • Asynchronous methods tested if activated.
  • Final status confirmed from backend or through consultation.
  • Duplicates and retries handled safely.
  • Order or payment updated correctly in your system.
  • Minimum logs available for support and diagnosis.
  • Sandbox completed with the required test evidence.
  • Production configuration reviewed for the target environment.
  • Critical flows tested with integration team.
  • Integration ready for go-live.

​
Minimum approval criterion

Approved purchase

At least one approved flow validated end to end.

Rejected purchase

Decline handling and customer messages fully validated.

Consistent result

Frontend, backend and final payment state aligned before production.