Paysafe Redirect¶
Paysafe Redirect Payment Methods¶
Paysafe Redirect enables seamless access to a wide range of alternative payment methods through a single integration. It allows merchants to offer localized and preferred payment options tailored to specific markets, all while ensuring a secure and streamlined checkout experience.
Customers are redirected to a secure environment to complete their payment using their selected method. There are two ways to initiate this redirect:
🧾 Hosted Payment Page (HPP)¶
In this flow, the Payments Platform presents the available payment methods (e.g., ePay, PaySafeCard, Trustly, etc.) for the customer to choose from. Once a method is selected, the customer is redirected to Paysafe to complete the transaction securely.
🧬 Flow Diagram¶
sequenceDiagram
participant Customer
participant Merchant Frontend
participant Payments Platform
participant Paysafe
Customer->>Merchant Frontend: Start checkout
Merchant Frontend->>Payments Platform: Create HPP session
Payments Platform-->>Merchant Frontend: Session link
Merchant Frontend->>Customer: Redirect to HPP
Customer->>Payments Platform: View HPP and select payment method
Payments Platform->>Paysafe: Initiate redirect for selected method
Customer->>Paysafe: Complete payment
Paysafe->>Payments Platform: Notify payment result
Payments Platform->>Merchant Frontend: Notify result
🔌 Direct API Integration¶
In the direct API flow, the payment method is already selected on your platform. The customer is immediately redirected to Paysafe to complete the payment without an intermediate selection screen.
This method provides more control over the user experience but requires you to manage available payment methods and their codes.
🧬 Flow Diagram¶
sequenceDiagram
participant Customer
participant Merchant Frontend
participant Payments Platform
participant Paysafe
Customer->>Merchant Frontend: Start checkout
Merchant Frontend->>Payments Platform: Create redirect payment with selected method
Payments Platform->>Paysafe: Initiate payment session
Paysafe-->>Payments Platform: Redirect URL
Payments Platform-->>Merchant Frontend: Redirect URL
Merchant Frontend->>Customer: Redirect to Paysafe
Customer->>Paysafe: Complete payment
Paysafe->>Payments Platform: Notify payment result
Payments Platform->>Merchant Frontend: Notify result
✅ Supported Payment Methods¶
Below is the list of supported payment methods available via Paysafe Redirect, along with their corresponding codes. These codes are required when using Direct API Integration.
Code | Payment Method |
---|---|
ALI | AliPay |
BLT | Boleto |
CHP | SafetyPay Cash Payment |
GIR | Giropay |
GLU | Trustly |
GFC | Gift Cards |
OBT | Rapid Transfer |
NPY | EPS |
NTL | NETELLER |
ONB | SafetyPay Bank Transfer |
PGF | PagoEfectivo |
PSC | PaySafeCard |
PCH | Paysafecash |
PWY | Przelewy24 |
GCH | Gcash |
GRP | GrabPay |
CNS | Coins.ph |
DNA | Dana |
LNJ | LinkAja EWallet |
MAH | Mach |
SPX | Pix |
KHP | Khipu |
SPI | SPEI |
SFT | Sofort (Klarna) |
EPD | ePay |
WLT | PaySafe Wallet |
ℹ️ Note: For Hosted Payment Page integration, these codes are managed internally. For Direct API Integration, you must provide the correct code when initiating the payment request.
🔁 Flow Comparison¶
Feature | Hosted Payment Page | Direct API Integration |
---|---|---|
Who shows payment methods? | Payments Platform | Merchant platform |
Payment method selection step? | Yes | No (selected beforehand) |
Redirect to Paysafe | After selection | Immediately after initiation |
Flexibility in UX | Moderate (managed selection screen) | High (fully controlled UX) |
Integration effort | Lower | Higher |