Accept BLIK and MB WAY at checkout
Turn on BLIK and MB WAY to unlock new revenue in Poland and Portugal, with no configuration required. Available for one-time items.
What's new?
We've updated the Paddle platform to support BLIK and MB WAY as payment methods. This means that blik and mb_way are now allowed values for the payments[].method_details.type field against a transaction in the Paddle API.
Information about the payment method used for a payment attempt.
Type of payment method used for this payment attempt.
How it works
Europe is a region where mobile-first payment solutions are becoming deeply embedded in everyday financial life, with Poland and Portugal leading the charge. In both countries, it's common to pay using apps — BLIK in Poland and MB WAY in Portugal. Customers expect the speed and convenience of these apps when paying online.
You can now turn on BLIK and MB WAY as payment method for Paddle Checkout. Once enabled, Paddle automatically presents them as a payment option for one-time purchases for customers in Poland and Portugal respectively — no additional configuration required.
Deferred capture
Most payment methods supported by Paddle are instant capture type payment methods. This means that payment is authorized and captured in one step.
BLIK and MB WAY are deferred capture type payment methods, which means funds are captured after payment is authorized. For BLIK and MB WAY, this typically happens within ten minutes, but may take longer in some cases depending on the customer's bank or app.
Paddle Checkout includes a new screen to let customers know that funds are being captured. The checkout is completed at this point, so Paddle.js emits a checkout.completed event.
The transaction is completed when payment is fully captured, at which point a transaction.completed event occurs.
For this reason, we don't recommend using Paddle.js events for fulfillment. To be sure a payment was fully captured, use webhooks and wait for transaction.completed to occur.
Summary of changes
API and events
This is a summary of the changes to responses in the Paddle API and events:
| Entity | Field | Change | Notes | 
|---|---|---|---|
| Transaction | payments[].method_details.type | New allowed value | Returns blikandmb_way. | 
Next steps
This change is available now.
It's a non-breaking change, meaning it doesn't impact existing integrations. You should test your checkout success workflows to make sure they're compatible with deferred capture payment methods.
To keep the Paddle platform safe for everyone, BLIK and MB WAY require additional approval from Paddle. You can apply by filling out the form on the BLIK and MB WAY pages. Once approved, you can enable them in Paddle > Checkout > Checkout settings. You don't need to establish a local entity or sign up for any merchant accounts.
You can work with transactions using the API to see the new payments[].method_details.type value.