SaaS and digital services
Renew access to applications, content and packages without sending the customer through checkout again.
Recurring payments · BLIK + cards
One consent. Payments that keep your service running.
Accept recurring charges for memberships, subscriptions and regular services through BLIK or a saved card. Your system chooses the time and amount, and dpay processes the payment.
- BLIK and cards
- Fixed or variable amounts
- Payment results sent to your system
Your system
Monthly plan · PLN 59.99
Customer consent confirmed
readySaved payment method
BLIK · active consent
Schedule in your system
every month15 Jul
Paid
15 Aug
Next
15 Sep
Scheduled
Next charge submitted by your system
without another BLIK code
How it works
From customer consent to the next paid service period.
One straightforward process connects your subscription, the payment and its result.
Step 01
The customer chooses recurring payments
Show the amount, frequency and service terms in your store or application.
Step 02
They give consent once
They confirm with a BLIK code or approve the card in their banking app.
Step 03
Your system submits the charge
At the chosen time, your system sends dpay the amount of the next payment.
Step 04
You receive the result
The payment result returns to your system automatically.
Two popular methods
The customer chooses BLIK or a card. Your system keeps one operating model.
The confirmation journey differs by payment method. Your system still submits each subsequent charge and receives the result automatically.
BLIK
BLIK recurring payments
The customer gives consent for subsequent payments and confirms it with a BLIK code in their banking app. When payment is due, your system submits the next charge to dpay.
- Consent without taking the first payment
- Fixed or variable amount
- Limits for a single charge and the full service
- Consent status available to your system
The way subsequent charges are approved depends on the BLIK service option selected for your customer journey.
BLIK recurring payment documentationYour system stays in control
Your system runs the cycle. dpay processes the payment.
dpay does not set the schedule or subscription rules. When a payment is due, your system sends dpay the amount and the saved payment method reference.
Charge timing
Defined by the logic of your service.
Amount
Fixed or variable within the agreed limit.
Consent scope
Single and total limits, plus an expiry date.
Payment result
The result of every payment returns to your system.
POST /api/v1_0/payments/register
{
"transactionType": "blik_recurring",
"service": "SHOP_ID",
"value": "59.99",
"blik_alias": "SUB-84721-PAYID",
"url_ipn": "https://your-company.example/api/ipn",
"checksum": "e3b0c44298fc..."
}
200 OK
// the final result is delivered through IPNWhere it fits
When customers return regularly, payments should keep up.
Passes and memberships
Collect fees for clubs, classes, communities and paid membership programmes.
Regular deliveries
Collect payment for subscription boxes, catering, cosmetics or other regularly ordered products.
Plans and services
Charge for hosting, support, service packages and amounts that can be fixed or variable.
More advanced customer journeys
Not every service starts with the first charge.
You can save a card without taking a payment, request consent when the customer chooses a paid service, and submit the first charge later.
Save a card without a charge
Add a card to the customer account without taking funds.
Consent at purchase
Ask for consent when the customer chooses a paid service.
Temporary hold
Check that funds are available and capture the correct amount later.
Variable charges
Match each charge to actual usage within the consent limits.
Before you start
Choose the methods and rules for subsequent payments.
Recurring payments require a connection to your system and activation of the selected method on your dpay account.
01
Payment model
BLIK, cards or both, together with the amount and frequency rules.
02
System connection
Securely link the saved method to the customer account and submit subsequent charges.
03
Payment results
Handle successful and failed payments, and request consent again when the previous consent expires.
Frequently asked questions
Recurring payments, explained clearly.
The payment mechanism stays separate from the system that manages your subscriptions.
Does dpay collect payments according to a schedule?
No. Your system determines the time and amount, then submits the payment request to dpay. dpay processes the payment and returns the result, so your subscription rules remain in your system.
Does the customer confirm every subsequent payment?
For cards, the customer usually does not need to approve each subsequent charge again. For BLIK, it depends on the selected service option: a payment can run without customer action or require confirmation in the banking app.
Does my system store card details?
No. Instead of full card details, your system stores a secure reference to the card and links it with the customer account or a specific service.
Can the amount change between payments?
Yes, if the consent configuration and enabled payment model allow it. You can set a fixed or maximum amount, a total limit and an expiry date.
How do I stop recurring charges?
Your system stops submitting further payment requests. A saved payment method does not trigger a charge by itself. Consent can also expire or be withdrawn.
How do I enable recurring payments with dpay?
In the form, choose BLIK, cards or both and describe the amounts and frequency. You will receive the customer-consent rules, integration steps and the information required to activate the service on your account.
Recurring payment enquiries
Let’s talk about regular payments.
Tell us about your subscription, service or billing model. Our reply will list the available methods, customer-consent rules and the first integration steps.
- Recurring BLIK and card payments
- Fixed or changing amounts
- Connected to your system with payment confirmations