Pay-by-linkCustomers select a local bank, confirm the transfer and return to your service.
Payment infrastructure for institutions
Local payments. Inside your product.
Connect your product to dpay and add local payment methods without building a separate solution for every country. You keep your interface, product and customer relationship.
- One integration
- Local payment methods
- Payment result in your system
Markets and methodsExplore the local payment mix.
5 markets
4 method familiesSelected market
Poland
Customers pay with BLIK or an instant transfer from a local bank through a journey they already know.
Pay-by-link
Customers enter a code and approve the payment in their banking app.
Example banks available through pay-by-link
- Your product
- dpay
- Local bank or wallet
- Payment result
One connection to dpay takes the customer to the right method and returns the payment result to your product.
For regulated payment businesses
Your service stays in front. Local infrastructure runs underneath.
Keep your own product, brand and customer relationship while dpay connects your service to local payment methods.
Payment and electronic money institutions
Extend your service with local payment flows without building a separate connection for every market.
For product, technology and operations teams
Small payment institutions
Add local payments to a service operated in Poland and grow it within your registration scope.
Technology matched to your operating scope
Cross-border institutions
Add payment methods used in local markets to a product offered to customers across multiple countries.
One layer for multiple local markets
Local payment methods
One integration. Many local ways to pay.
dpay connects your product to the methods customers know in their market. Pay-by-link, BLIK, MB WAY and Bizum can use the same connection.
01PL · CZ · SK
Pay-by-link
Customers choose a bank, approve the transfer and return to your product. Local journeys for Poland, Czechia and Slovakia.
02PL
BLIK
Customers enter a six-digit code and approve the payment in their banking app.
03PT · EUR
MB WAY
Customers enter their phone number and approve the payment in the app. A popular way to pay in Portugal.
04ES · EUR
Bizum
Customers pay using their phone number and approve the transaction in their banking app. A popular method in Spain.
Start with one market, then add more methods without rebuilding the entire payment journey.
White-label in practice
ZEN.COM: white-label PBL for PL, CZ and SK.
We provide ZEN.COM with pay-by-link in a white-label model. Based on locale and currency, ZEN.COM selects the market, uses the matching bank list supplied by dpay and displays it inside its own interface, for PL/PLN, CZ/CZK or SK/EUR.
- 01ZEN.COM identifies the payment marketLocale and currency select the right variant: PL/PLN, CZ/CZK or SK/EUR.
- 02ZEN.COM displays the bank list from dpayThe bank set for the selected market appears under the ZEN.COM brand, without a separate dpay interface.
- 03The customer selects a bank and approves the transferAfter selecting a bank, the customer moves to the relevant online banking service while dpay handles the technical PBL flow.
- 04The status returns to ZEN.COMZEN.COM receives the payment result and continues the journey inside its own product.
Bank lists supplied by dpayWhite-label PBL
PLPLN
Bank list supplied to ZEN.COM for the PL market: Alior Bank, ING Bank Śląski, Bank Pocztowy, BNP Paribas, mBank, Nest Bank, Bank BPS, SKOK, PKO Bank Polski, Bank Pekao, Erste Bank, Bank Millennium, Credit Agricole, VeloBank, Bank Ochrony Środowiska, Santander, SGB Bank, Inteligo, Plus Bank, Revolut, UniCredit, Bank Spółdzielczy w Brodnicy, Bank Spółdzielczy Rzemiosła, Krakowski Bank Spółdzielczy.
CZCZK
Bank list supplied to ZEN.COM for the CZ market: Česká spořitelna, Komerční banka, Fio banka, Raiffeisenbank, mBank, ČSOB, MONETA Money Bank, UniCredit.
SKEUR
Bank list supplied to ZEN.COM for the SK market: Slovenská sporiteľňa, Tatra banka, VÚB banka, Poštová banka.
One technical layer
One connection supports the whole payment journey.
dpay takes the payment from the choice of a local method to the result in your system, refunds and reporting.
Payment registration
Your system sends the amount, currency and selected method, and dpay creates the payment.
Connection to a local method
dpay sends the customer to the right bank, app or wallet for the selected market and currency.
Payment result
Payment information returns to your system so it can continue serving the customer.
Refunds
Support full or partial refunds for methods and operating models where this operation is available.
Operational data and reports
Reports group transactions by market, currency and the services enabled in your product.
Testing and launch
Verify scenarios in a test environment, then move into production with the dpay team.
From idea to launch
Start with one market. Add more without rebuilding.
We begin with the most important market and one complete payment journey, then use the same foundation to expand the service.
- 01
Choose the first market
We define the method, currency and customer experience your product will start with.
- 02
Shape the payment journey
We design the data, handoffs and statuses around your product.
- 03
Integrate and test
Your technical team connects the API and verifies complete payment and error scenarios.
- 04
Launch payments
Go live in the first market, then add more methods through the same technical layer.
A clear division of responsibilities
Every part has a clear role.
You own the product and customer relationship. dpay provides integration and routing. A licensed provider handles regulated processing where the method or market requires it.
Your institution
Builds the product and customer relationship, designs the user experience and operates within its own permissions.
dpay
Connects your system to the payment method, sends customers into the right journey and returns the status.
Licensed provider
Handles regulated payment operations and settlement where the method or market requires it.
Payments Lab sp. z o.o. is a small payment institution registered with the Polish Financial Supervision Authority under MIP85/2020. Where a payment requires permissions outside dpay's scope, regulated processing and settlement are handled by a licensed provider working with dpay.
Frequently asked questions
The operating model, made clear.
One technical layer simplifies implementation while every role in the payment process stays clear.
Does dpay infrastructure support pay-by-link only?
No. The layer is method-agnostic: it brings pay-by-link, BLIK, MB WAY, Bizum and additional local payment methods into one integration model.
Can we start with one market?
Yes. Launch one market and one method first, then add more through the same integration layer.
Does one integration mean one agreement?
Not always. One technical integration can support several methods, but the agreement structure depends on the country, bank and payment-method provider.
Who processes and settles the payment?
dpay does so within its licence scope. Where the method or market requires different permissions, regulated processing and settlement are handled by a licensed provider working with dpay.
Is this product also available to small payment institutions?
Yes. dpay provides the technical layer for processes within the institution's registration scope and connects the journey to a licensed provider where needed.
Can we keep our own interface and brand?
Yes. Your service remains the customer's starting point. A bank, app or payment-provider screen appears only where the specific payment journey requires it.
Payment infrastructure enquiries
Add local payments to your product.
Tell us where you operate and how payments work in your service today. We will use your scenario to show how dpay can connect it to local payment methods.
- One integration
- Local methods for each market
- Support from testing to launch