Skip to main content

Introduction

PSE uses a redirect-based payment flow. When a customer selects PSE at checkout, they are redirected to their bank’s authentication interface to confirm the transfer, then redirected back to your website or app upon completion. PSE is a single-use payment method where customers must authenticate each payment. This guide explains the process of integrating PSE into your app or website using Payrails.

Pre-requisites

Before you start accepting PSE payments with Payrails, there are a few requirements you must meet:

Ways to integrate PSE

Payrails SDK

Server-to-server integration

Parse PSE from lookup response

Pass PSE payment method in request to authorize payment with Payrails

Note on amountsCOP uses 0 decimal places. Amounts should be provided as whole numbers—for example, 160000 for COP 160,000.
PSE is a redirect-based, single-use payment method. After calling the authorize endpoint, the customer will be redirected to their bank’s authentication interface. Once the transfer is confirmed, the customer will be redirected back to the returnInfo.success URL. Make sure to provide valid returnInfo URLs in your authorization request.

Handle the redirect response

Supported currencies

PSE via dLocal supports the following presentment currency:
  • COP — Colombian Peso

Supported regions / countries

Supported workflows and services

Last modified on September 28, 2026