One API, three groups of methods
tpay is a Polish online payment operator. The integration uses its current interface, the Merchant Open API, where the platform authenticates with a key pair under OAuth 2.0. Every supported method runs over that single connection:
- BLIK, including the BLIK One Click variant,
- payment cards, with the option to save a card for later purchases,
- bank transfers from the buyer’s own bank.
You set the checkout up in one of two ways: a redirect to the tpay payment page, or a payment form that stays inside your checkout.
BLIK: with a code and without one
In the on-site variant the buyer types the six-digit code from their banking app straight into the checkout. The code is valid for two minutes, so it makes sense to ask for it only at the final step.
BLIK One Click extends that variant by remembering the shop. After a successful payment the buyer gets a confirmation request in their banking app, and from then on approves each order with a push notification alone, with no code to retype. In B2B this pays off where the same person regularly tops up small items and pays upfront.
One operator-side detail worth knowing: a buyer can remember the shop in more than one banking app. tpay does not charge any of them automatically in that case, but returns the list of apps to choose from. The mechanism is described in the tpay BLIK documentation.
Cards and settlement currency
A saved card means a returning buyer does not enter the card details again. tpay handles Visa and Mastercard cards.
Two operator constraints matter in wholesale:
- Currencies other than PLN. According to the tpay documentation, card payments in a foreign currency are available through only one of the acquirers the operator works with. If you run an export channel in EUR, check this in your contract before launch.
- PCI DSS. A card form embedded in your own checkout does not exempt the merchant from the standard. tpay recommends starting with the self-assessment questionnaire.
What happens after the payment
tpay reports the outcome of a transaction with a notification sent to the shop’s address. Each notification carries a JWS signature, and the module verifies it before changing the order status. The notification address is public and tpay does not provide a list of IP addresses to filter on, so the signature is the only protection against a forged “paid”.
When the shop does not acknowledge receipt, tpay resends the notification many times, at growing intervals, for more than a day. A short outage on the shop side therefore does not mean a lost payment. The details are in the tpay notification documentation.
On the platform side:
- for the payment method you set which status an order gets while payment is pending, after it succeeds and after it fails,
- the buyer can retry a failed payment from the order itself, without placing it again,
- the administrator sees the history of payment attempts on the order and can also retry it,
- the platform emits payment settled, failed and refunded events, which can be forwarded by webhook to an ERP or an accounting system.
Refunds start from a return
You do not issue the refund in the tpay panel. It comes out of the returns module when you settle a case with money back, so the goods and the money share one record. The amount for a line defaults to what the buyer paid for the returned quantity and cannot exceed it.
Two practical caveats:
- tpay pays refunds out of the funds on the merchant account. The balance has to cover the refund amount plus the operator’s fee, otherwise the request will not go through.
- If the tpay module is switched off, settling a return with a refund is rejected and the case keeps its status until the module is switched back on. Replacement and repair work as usual.
Before go-live
- A registered and verified tpay merchant account.
- Open API keys generated in the Merchant Panel (Integration, then API). The secret is shown only once, when the key is created.
- Card payments enabled on the account, if you want to accept them.
- Tests in the tpay sandbox environment, which has its own certificates for signing notifications.
You enter the keys in the platform’s admin panel. Secret fields are encrypted at rest and cannot be read back through the API.
Who should see tpay at checkout
An online gateway is rarely the default way to pay in wholesale. Regular customers pay by transfer on terms or against a credit limit, and both are part of the open core. The tpay module, like the other online payment gateways, is a paid module.
Payment methods are assigned to sales channels and to specific organizations. tpay can therefore be visible in the retail channel and to new customers with no limit, and hidden from contract accounts.
You pay tpay’s rate and nothing on top: Endora adds no intermediary margin of its own. The choice between tpay and PayU usually comes down to who you already have a contract with. Stripe fits better when most payers are foreign customers. If you sell on invoice only, start with KSeF, and you will find the rest in the integrations catalog.