Redirecting customer

This guide explains how to redirect the customer after the payment request is sent, if necessary. This redirect applies to all 3 types of integrations. The full integration guides are available here:

Customer redirect

After sending the request, your ecommerce platform receives a response. It depends on the type of integration:

  • For Hosted integrations, the response is a URL to redirect the customer. 
  • For Host2Host integrations, it can be a redirect request or the result of the transaction. 
  • For JavaScript integrations, it can be a redirect request or the result of the transaction. 

Note: The redirect URLs received from AP are valid for max 30 minutes. Your ecommerce platform must redirect the customer’s browser to that URL.

The redirect can be full screen or in an iframe, although there are some drawbacks to the latter:

  • Some solutions aren’t compatible with an iframe, including Bizum.
  • You can’t set an iframe height that prevents there being vertical scroll bars on the cashier because the size depends on the payment solution, whether the customer is registered, etc.

When the cashier completes payment on the URL they were redirected to:

  • AP sends a notification to the URL on your ecommerce platform provided in the “statusURL” parameter of the request with the transaction result.
  • AP redirects the customer to the URL on your ecommerce platform for the transaction result, from the options sent in the parameters “successURL”, “errorURL” and “cancelURL”.

Redirect process

The process and reasons for redirecting the customer depend on the type of integration. 

Redirect on Hosted

After receiving a request by POST from your ecommerce platform, AP generates and returns a redirect URL in response:

				
					https://checkout.stg-eu-west3.epgint.com/EPGCheckout/rest/online/detokenize?token=1cfe2f52-a72c-4a48-bf40-7d045397ef7c&apiVersion=5

When the customer’s browser goes to the URL, AP recoups the request parameters and generates the cashier for the payment gateway according to the merchant’s settings, request parameters and customization parameters:

  1. Full-screen redirect with customized logo, title and subtitles, order details and payment solution selector.
  2. Loads in an iframe with the “form only” settings.

Host2Host redirect

For Host2Host integrations, customers may be redirected to a URL. This can be for several reasons:

  • Cardholder authentication for card payments.
  • The customer must log in on the payment solution platform.
  • If the payment solution isn’t compatible with direct operations, the response will show redirect is required. The URL is in the element <redirectionResponse>

Here are two examples:

Request for SCA redirect to issuer for authentication:

				
					<operation sorted-order="x">
   .
   .
   <redirectionResponse>redirect:https://checkout.stg-eu-west3.epgint.com/EPGCheckout/rest/online/3dsv2/redirect?action=gatherdevice&params=eyJ0aHJlZU…………I6IjA1In0=</redirectionResponse>
   <service>3DSv2</service>
   <status>REDIRECTED</status>
   <transactionId>986566</transactionId>
   <respCode>
      <code>8100</code>
      <message>Frictionless requires</message>
      <uuid>83730158_047c_4d19_a06c_d5d03547af2d</uuid>
   </respCode>
   .
   .
</operation>

Request for redirect to payment solution platform so customer can log in and authorize payment:

				
					<operation sorted-order="1">
.
.
 <message>Redirecting to bizum</message>
.
.
  <paymentSolution>bizum</paymentSolution>
  <redirectionResponse>redirect:/rest/online/bizum/redirect?transactionId=7600819</redirectionResponse>
  <status>PENDING</status>
 <respCode>
   <code>0000</code>
.
.
 </respCode>
</operation>

JavaScript redirect

For JavaScript integrations, customers may be redirected to a URL. This can be for several reasons:

  • Cardholder authentication for card payments.
  • The customer must log in on the payment solution platform.
  • If the payment solution isn’t compatible with direct operations, the response will show redirect is required. The URL is in the element <redirectionResponse>

Here are two examples:

Request for SCA redirect to issuer for authentication:

				
					<operation sorted-order="x">
   .
   .
   <redirectionResponse>redirect:https://checkout.stg-eu-west3.epgint.com/EPGCheckout/rest/online/3dsv2/redirect?action=gatherdevice&params=eyJ0aHJlZU…………I6IjA1In0=</redirectionResponse>
   <service>3DSv2</service>
   <status>REDIRECTED</status>
   <transactionId>986566</transactionId>
   <respCode>
      <code>8100</code>
      <message>Frictionless requires</message>
      <uuid>83730158_047c_4d19_a06c_d5d03547af2d</uuid>
   </respCode>
   .
   .
</operation>

Request for redirect to payment solution platform so customer can log in and authorize payment:

				
					<operation sorted-order="1">
.
.
 <message>Redirecting to bizum</message>
.
.
  <paymentSolution>bizum</paymentSolution>
  <redirectionResponse>redirect:/rest/online/bizum/redirect?transactionId=7600819</redirectionResponse>
  <status>PENDING</status>
 <respCode>
   <code>0000</code>
.
.
 </respCode>
</operation>
Comparte este documento
Tabla de Contenidos

Consulta la documentación de las distintas secciones de integraciones:

Comienza a integrar

undraw_add_to_cart_re_wrdo 1 (1) (1)

Plugins para CMS

Complementa la integración

SDKs

Métodos de pago

Herramientas

Addon Payments

Consulta la documentación de Addon Payments. Aquí tienes las distintas secciones:

Integraciones

Consultas frecuentes

Portal Backoffice

Cyberpac

We are currently working on the English version of the Cyberpac documentation. You can view the Spanish version using the buttons below:

Canales BackOffice Portal

Plugins integration

Custom integrations

POS integrated Payments

Create a solution that will help you automate processes. You can even add payment processes on physical terminals.

Payment Integrated with Android POS

Payment Integrated with Smartphone POS

POS Data sheets

Addon Payments

Comercia Global Payments has several integration options so you can choose the most efficient one for you.

Integrations

Frequently Asked Questions

BackOffice Portal

Consult the documentation of the different integrations sections:​

Start integration

undraw_add_to_cart_re_wrdo 1 (1) (1)

CMS Plugins

Complement your integration

SDKs

Payment Methods

Tools