Introduction
BLIK Recurring Payments require activation of the additional payment channel. To enable it, please contact customer support.
BLIK Recurring Payments in Model O use the standard Payment API extended with additional parameters required by the BLIK payment process. The customer confirms activation in their banking application.
Transaction status notifications are sent in accordance with the Payment API documentation. Additionally, if a transaction is declined, an extra notification containing the reason for the rejection is sent. For payments made using an alias, additional notifications regarding the alias itself and its status are also sent.
BLIK Model O enables flexible, automatic recurring payments. Customers set up recurring payments by entering a BLIK code. Once activated, subsequent payments initiated by the merchant are authorized automatically by the bank without requiring customers to confirm each payment in their banking app.
Flexible amounts and payment dates
BLIK Model O supports recurring payments with variable amounts and variable frequency. The customer authorizes a recurring payment arrangement, while the merchant initiates subsequent charges with the amount applicable to each transaction.
Payments are automatically authorized by the bank without requiring the customer to enter another BLIK code or confirm each charge in their banking app.
Important: Information displayed to the customer
Before the customer activates recurring payments, the merchant must clearly display:
- Product and recurring payment name - identify the service and payment arrangement.
- Amount - specify the fixed amount or explain that charges vary according to the agreement, price list or a stated range.
- Frequency - specify the billing interval or explain that payments occur at variable intervals such as after each service use.
- Initial charge - state the exact amount payable during activation. For a verification charge, explain its refund.
Display the next payment date when specified.
The recurring amount and frequency are not displayed in the banking app in Model O, so the merchant must provide this information before activation.
Examples of use
| Use case | Example charges | How it works |
|---|---|---|
| Monthly subscription | 49 PLN on October 10 and 49 PLN on November 10 | The same amount is charged every month |
| Weekly subscription | 49 PLN on October 3 and 49 PLN on October 10 | The same amount is charged every week |
| Subscription upgrade | 150 PLN on October 10 and 250 PLN on November 10 | The amount changes after the customer upgrades |
| Usage-based billing | 120 PLN on October 5 and 185 PLN on November 5 | Each bill reflects actual usage |
| Scooter rental | 12 PLN on October 3 and 19 PLN on October 8 | Charges follow individual rides |
Amounts and billing frequency must be clearly communicated to the customer including when they are variable.