Skip to main content
Payflex is a buy now, pay later (BNPL) payment method in South Africa. Customers pay in full or split the amount into installments, and Payflex collects them from the customer’s card. Payrails processes Payflex through two payment service providers (PSPs): directly through Payflex, or through dLocal. The flow is the same with each one, but the required request fields differ. Pick a PSP below for its setup steps and request examples.

​
How a Payflex payment works

Payflex is a redirect payment method:
  1. The customer selects Payflex at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to the Payflex checkout page.
  3. The customer signs in or checks out as a guest, chooses to pay in full or in installments, and confirms the payment.
  4. The PSP sends the customer back to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures Payflex payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

Payflex supports ZAR (South African rand) as its only presentment currency.

​
Integrate Payflex

Choose the PSP that processes Payflex for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

dLocal

Payflex via dLocal

Payflex

Direct Payflex integration

​
Compare PSPs

Neither PSP supports saving a Payflex instrument or merchant-initiated transactions (MIT). Each Payflex payment is a new customer-initiated payment.

​
Ways to integrate Payflex

  • Payrails SDK: the Web SDK shows Payflex when your workflow returns it as a payment option, and redirects the customer to the Payflex checkout page. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with payflex as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026