Handle callback functions

When you call paymentForm.init(...), Flex It allows you to capture three callback functions. The most important result for front responseCallback(response).

Here. responseCallback(response) as the main entrance of the result at front. The JSON That you get there reuses the same structure of API of Authorisation - ecommerce for the method of payment chosen within Flex.

Callbacks available

responseCallback

It runs when the process gets to a business result and gives you the JSON response.

trackingCallback

It runs for every flow event, as a method change, clicks or user advance within the form.

Failed

It runs after a technical error occurs during the load or performance of the component.

Example of implementation

function responseCallback(response) {
    console.log("-------Respuesta-------");
    console.log({response});
}

function trackingCallback(trackdata) {
    console.log("-------Tracking de Eventos-------");
    console.log({trackdata});
}

function onErrorCallback(error) {
    console.log("-------Error en el proceso-------");
    console.log({error});
}

paymentForm.init(
    document.querySelector("#demo"),
    responseCallback,
    trackingCallback,
    onErrorCallback
);

How to interpret responseCallback

The field response.payment_method indicates what reference to PayIn you have to use to interpret the JSON response returned by Flex.

Do not use response.meta.status.code as an approved or refused payer. That code indicates only the result of the service processing or if the response was generated correctly. To validate the payment result, check response.transaction.state and confirms from backend with Consultation or Notificationswith the method of payment.

The object response following the contract of API from Authorisation with Card.If your flow uses Redirect or 3DS authentication outside the same screen, complete this reading with Considerations for Redirect methods.

The object response following the contract of API from Authorisation with Yape.Even if the result goes by responseCallback, also valid operative consistency from backend before confirming order.

The object response following the contract of API with Bank Transfer.That method may require later confirmation. Do not take the front as the only source of truth: get up at Consultation or Notifications.

The object response following the contract of API from Authorisation with QR.To generate QR or showing an initial response does not amount to a confirmed final payment. Use Consultation or Notifications To close up his business logic.

The object response following the contract of API from Authorisation with Cuotéalo.The final status with a redirection or monitoring flow confirms Consultation or Notifications.

The object response following the contract of API from Authorisation with PagoEfectivo.The generation of CIP or from the payment link doesn’t mean that the money’s been received. confirms the result with Consultation or Notifications.

trackingCallback and onErrorCallback for technical faults. No one replaces the business logic you have to build up about responseCallback and backend confirmation.

API of Authorisation - ecommerce

Main reference of the response contract that Flex Reuse responseCallback.

API Consultation

Valids from backend the final status of the operation before closing the order.

Notifications S2S

Use this channel if your integration also confirms backend results using notifications.

Getting started

Integration

Payments

Callbacks available

responseCallback

trackingCallback

Failed

Example of implementation

How to interpret responseCallback

API of Authorisation - ecommerce

API Consultation

Notifications S2S

​Callbacks available

responseCallback

trackingCallback

Failed

​Example of implementation

​How to interpret responseCallback

​Related references

API of Authorisation - ecommerce

API Consultation

Notifications S2S

Callbacks available

Example of implementation

How to interpret responseCallback

Related references