Skip to main content
Alignet One Flex allows to integrate a payment form into web applications using a single interface for multiple payment methods. The recommended flow combines authentication, generation of nonceconstruction payloadand capture of result from responseCallback.

Latest improvements

Check recent viewing, multidioma, checkout closure, Yape UX and operation number.

Initial flow

1. Authentication

First generates Access Token from API Security. Without that token you cannot apply for nonce.

2. API Nonce

with Access Token currently applying nonce That will be used to initialise Flex.

3. Bookshop Flex

After you get the nonceincludes CSS and JS of the environment and continues with the initiation of the form.
In FlexThat’s right. AutenticaciónAPI Nonce → library inclusion and then the initialization of the component.

Recovery implementation

Construction of payload

Guma el payload Reusing the structure of API and sending payment_method: {} at the root object.

Initiate component

It creates an instance of FlexPaymentForms, defines visible methods and puts the form into your DOM.

Capture callbacks

Process responseCallback, trackingCallback and onErrorCallback by the payment method selected.
In Flex, the result visible to the front enters by responseCallback(response)and that response reuses the contract of API of PayIn with respect to the payment method used.

Why? Alignet One Flex?

A single integration

The same capture interface for all available payment methods.

Easy to use

It removes the complexity of managing independent payment flows.

Sure.

Integrated 3DS Authentication and secure data transmission.

Available payment methods

3DS card

Visa, Mastercard, Amex and Dyers with Secure 3D authentication.

Yape

Digital wallet with client phone number.

QR

I pay by scanning a code QR from any bank app.

Banking Transfer

Direct payment from online banking.

Cuotéalo

I pay in quotas without credit card.

Coming

PagoEfectivo and Powerpay’s on his way.