Skip to main content
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.

Integration checklist

Check the Checklist dedicated to Web Checkout.