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 Bizum payment through Redsys:- Set up a Redsys integration in your workspace. Follow the Redsys integration setup guide if you don’t have one yet.
- Ask your acquiring bank to activate Bizum on the Redsys terminal you use with Payrails.
- In the Payrails Portal, go to Settings → Integrations, open your Redsys integration, select Bizum under Payment methods, and save.
- Add Bizum as a payment option in your workflow.
Request fields for Redsys
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 Bizum payment
Call authorize a payment withbizum as the paymentMethodCode.
Authorize request
How Redsys handles Bizum
- Payrails sends Redsys a Bizum request to pay, addressed to the customer’s phone number with its dialing code.
- Payrails checks that both the phone number and the dialing code are present before it calls Redsys.
- A Bizum payment needs no redirect and no 3D Secure. Payrails keeps the payment pending until Redsys sends the final result as a notification.
- With instant capture, Redsys charges the customer as soon as they approve the payment. With manual capture, the customer approves the payment first, and Redsys charges it when you capture the payment.
- Refunds go back to the customer’s bank account through Redsys.
- Each Bizum payment is a new customer-initiated payment.