Supported workflows
| Workflow | Supported |
|---|---|
| Payrails SDK | ✔ |
| Payrails API | ✔ |
| Delayed / Manual Capture | ✖ |
| Instant Capture | ✔ |
| Cancel / Void | ✖ |
| Refund / Reverse | ✔ |
| Save Instruments | ✖ |
| Merchant Initiated Transaction (MIT) | ✖ |
Before you begin
Complete these steps before you send your first Payflex payment through dLocal:- Set up a dLocal integration in your workspace. Follow the dLocal integration setup guide if you don’t have one yet.
- Ask dLocal to enable Payflex on your dLocal account for South Africa.
- In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select Payflex under Payment methods, and save.
- Add Payflex as a payment option in your workflow.
Request fields for dLocal
Send these fields in the authorize request, in addition to the standard authorize fields. Required fields must be present for the payment to succeed. Payrails sends Optional fields to the PSP when you include them.Authorize a Payflex payment
Call authorize a payment withpayflex as the paymentMethodCode. The response includes the redirect to the Payflex checkout page.
Authorize request
success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.
How dLocal handles Payflex
- Payrails sends Payflex to dLocal for South Africa in ZAR, whatever the customer country code.
- A missing
meta.orderreturns an error. So does an address that lacks any ofstreet,doorNumber,city,postalCode,stateorcountry.code. - The payment stays pending until dLocal reports the result.