Connect PayU, Tpay, Paynow or PayPal
Connect PayU, Tpay, Paynow or PayPal with the credentials from the gateway panel, set up BLIK on the checkout page for PayU and recurring BLIK for Tpay, and manage gateway defaults.
PayU, Tpay, Paynow and PayPal connect the same way: you paste the credentials from your own account at the gateway into a short form. When you finish, the gateway card shows Connected and the gateway is enabled on your prices. You need an active merchant account at the gateway; Zanfia does not create one for you.
Open the Payments tab
In the sidebar open Integrations and choose Payments (/integrations/payments). PayPal is
in Global payments; PayU, Tpay and Paynow are in Local payments (click the section header
if it is folded). Click Connect on the card.
Fill in the credentials
The window is titled Connect plus the gateway name. Every field has a Where do I find this? guide with short steps and a link that opens the gateway's panel in a new tab. The fields per gateway are listed in the table below. Numeric ID fields accept digits only, which catches a key pasted into the wrong field.
Enable the gateway on your prices and save
For PayU, Tpay and Paynow leave Automatically enable this payment gateway on all existing prices (recommended) ticked; PayPal does not have this box, so enable it on prices afterwards (see Defaults for prices below). Click Save. A message such as "Integration with PayU was successful" confirms it and the card moves to Connected.
Good to know
If the gateway refuses the credentials, the error stays inside the window next to the fields, so you can compare it with what you typed. Saved secrets are never shown again: to change credentials later you enter all of them from scratch.
Credentials per gateway
| Gateway | Fields in the form | Where the guides point |
|---|---|---|
| PayU | POS ID (pos_id), OAuth protocol - client_id, OAuth protocol - client_secret, Second key (MD5) | The PayU management panel: your POS (point of sale) settings and its OAuth settings. The second key is the one used to sign notifications. |
| Tpay | ID Number (e.g. 401780), OAuth Protocol - Client ID, OAuth Protocol - Secret, Security code | The Tpay merchant panel: Settings → API for the ID and the OAuth keys, Settings → Security / Notifications for the security code. |
| Paynow | API Key (Api-Key), Signature Key (Signature-Key) | The Paynow merchant panel: Settings → Shops, your shop. Both keys are on the same page. |
| PayPal | Client ID, Client Secret | The PayPal Developer Dashboard: Apps & Credentials, your live app. |
If the connection is refused
| Gateway | Message | What to check |
|---|---|---|
| PayU | "Client Id or Secret is not valid!" | The client_id and client_secret of the same POS. |
| Tpay | "The provided client ID or secret is invalid. Ensure that the provided data is correct." | The OAuth Client ID and Secret. |
| Paynow | "API key or Signature key is not valid!" | Both keys of the same shop. |
| Paynow | "The notification URL domain … does not match the domain configured in your Paynow merchant panel." | Update the shop domain settings in Paynow to match the domain of your site. |
| PayPal | "Client ID or Client Secret is not valid!" | That you copied the credentials of the live app. |
PayU: BLIK code on the checkout page
By default a buyer who picks PayU is redirected to PayU and chooses BLIK there. The Manage window of PayU has a section BLIK code on the checkout page: "Buyers type their BLIK code right on the checkout page, with no redirect to PayU." PayU enables this service ("Transparent payment with a BLIK authorization code") usually on a separate point of sale, so the section asks for that point of sale's credentials from the PayU panel. If PayU enabled the service on your main point of sale, enter the same credentials and click Save BLIK point of sale.
Once saved you can also tick Show BLIK as the first payment method: buyers see the BLIK code field right away on every checkout with PayU, unless you set the method order by hand on a checkout (Form & UX). Remove deletes the BLIK point of sale; buyers then pay with BLIK on the PayU page again.
Tpay: recurring BLIK
The Manage window of Tpay has a section Recurring BLIK (recurring payments) with the switch Recurring BLIK enabled on my Tpay account. Turn it on only after signing the recurring BLIK payments annex with Tpay; the link How to enable recurring BLIK payments in Tpay opens Tpay's own guide. Once enabled, a subscription price can accept BLIK after you also turn on Accept recurring BLIK (Tpay) in the form of that price; it is set on each subscription price separately.
Before you turn the switch on, copy the address shown under it and save it in the Tpay Merchant Panel under Settings → Notifications as the address for BLIK alias notifications. It lets Zanfia receive consent confirmations, revocations and expirations.
Defaults for prices
Every connected gateway has a Workspace settings section in its Manage window:
| Setting | What it does |
|---|---|
| Default gateway for new prices | "New prices are created with this gateway enabled." At least one default payment gateway must stay enabled. |
| Existing prices | Enable on all or Disable on all switches the gateway on every existing price at once. Buyers see the change immediately. |
Remove a gateway
In Manage, click the trash icon next to the connection and confirm "Remove this connection? Anything that uses it will stop working." The gateway stops being offered on your checkouts until you connect it again.
Which payment methods and currencies each gateway covers is in Payment methods by gateway.
Was this article helpful?