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 Bancontact payment through Worldpay:- Set up a Worldpay integration in your workspace. Follow the Worldpay integration setup guide if you don’t have one yet.
- Ask Worldpay to enable Bancontact on your Worldpay entity.
- In the Payrails Portal, go to Settings → Integrations, open your Worldpay integration, select Bancontact under Payment methods, and save.
- Add Bancontact as a payment option in your workflow.
Request fields for Worldpay
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 Bancontact payment
Call authorize a payment withbancontact as the paymentMethodCode. The response includes the redirect to Bancontact.
Authorize request
success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.
How Worldpay handles Bancontact
- Payrails reads the customer’s email from
meta.order.billingAddress.email, not frommeta.customer.email. - When Worldpay reports the payment as pending after the redirect, Payrails waits for the Worldpay webhook to set the final status.
- Bancontact through Worldpay supports customer-initiated transactions (CIT): the customer confirms every payment.