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 BLIK payment through Checkout.com:- Set up a Checkout.com integration in your workspace. Follow the Checkout.com integration setup guide if you don’t have one yet.
- Ask Checkout.com support to enable BLIK on your Checkout.com account.
- In the Payrails Portal, go to Settings → Integrations, open your Checkout.com integration, select BLIK under Payment methods, and save.
- Add BLIK as a payment option in your workflow.
Request fields for Checkout.com
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 BLIK payment
Call authorize a payment withblik as the paymentMethodCode.
Authorize request
How Checkout.com handles BLIK
- Payrails processes BLIK through the Checkout.com Payment Setup API, and sends the code to Checkout.com as the partner code.
- Checkout.com sends the final result as a webhook notification after the customer approves or declines in the banking app.
- Checkout.com accepts references of up to 35 characters for BLIK. Payrails shortens the merchant reference to 35 characters on the payment and on refunds.
- Each BLIK payment is a new customer-initiated payment.