Tpay

Tpay handles BLIK (including recurring) and cards. Configure under Organization settings → Payment integrations → Tpay. Steps below match the in-app instruction.

Tpay payment configuration

1. Notifications (webhook and email)

In the Merchant Panel go to Settings → Notifications.

  • Notification URL: In the "Notification URL" section paste the address below and save. Tpay will send Zevio information about payment registration to this address.
  • Token notification URL: In the "Token notification URL" section paste the same address. It is required for card tokenization (trial, subscription resume, card update) and for token status updates.
  • Email notifications: In the "Email notifications" section set the notification type to "None". Zevio handles customer notifications; you can enable or disable them in organization settings.
Zevio generates the organization webhook URL (copyable in the instruction modal). Paste the same URL into both Tpay notification fields.

2. Credentials

When registering through Zevio, the client ID is saved automatically. If Tpay sends new credentials or you change them in the Merchant Panel, update the client secret (and optionally the Cards API RSA key) in Zevio under Payment integrations → Tpay → Credentials. An incorrect secret will break BLIK and card payments.

  • Fields: tpayClientId, tpayClientSecret
  • Optional Cards API RSA public key (Tpay panel Integrations → API → Cards API) - collect cards on Zevio checkout without full redirect
  • If the secret changes in Tpay, update it in Zevio or BLIK/card break

3. Payment operator selection

After activating the Tpay account and configuring notifications, select Tpay as the card and/or BLIK payment operator in organization settings (Payment operator section). Only then will payments be routed through Tpay.

Account activation (new registration)

Merchant account has been created in Tpay. A registration link has been sent to your email address. Click the button below to proceed with account activation.

Methods: BLIK and card via Tpay.

Sandbox testing (summary)

Organization settings → Payment providers → Activate Tpay account. After registration, select Tpay for BLIK and/or cards.

  • BLIK: BLIK code starting with 777 (or another 777xxx).
  • Recurring BLIK registration: use amounts ending in .08-.15 (e.g. 10.08, 19.14).
  • Cards: success.
  • Subscription offer: use card or BLIK. Apple Pay and Google Pay on subscriptions work only with Stripe.
Full code/scenario list: in-panel sandbox notebook and Tpay sandbox documentation.

Where in the dashboard

  • /dashboard/settings/organization → Payment integrations → Tpay
  • Payment operator section - select Tpay for card and/or BLIK

Tpay account activation

Review the content first, then confirm.

1. Registration and first login

To enable payments, activate your account in the Tpay Merchant Panel - use the activation link in the button above or the one sent to your email - and complete the required merchant data in your Tpay account. The data must match the company details used when registering in Zevio. Completing account verification is required to accept payments and to add a payout bank account.

2. Merchant verification

After logging into the MP click "Verify account" and complete the form. The form has several steps - complete them in order; to proceed to the next step, fill in all fields marked as required in the current step.

2.1. Basic information (company data)

Complete the company data. You can add your website URL and correspondence address. For entities registered in Poland data is loaded automatically from the REGON database; other entities enter data manually.

2.2. Personal data - representatives and beneficiary

Representative: provide details of persons authorised to represent the entity you are registering: for a sole proprietorship - the entrepreneur's data; for a civil partnership - all partners; in other cases - persons authorised to represent according to your entity's rules of representation (e.g. as in the company register). Remember to add scans or photos of ID documents for the indicated representatives (field below the data). For companies - attach the real beneficiary declaration.

In parallel the AML department checks the content and operation of your sales site (including terms, privacy policy, product descriptions).

2.3. Required documents (shown conditionally)

This step is not required for everyone. In some cases the system may require attachment of a Real Beneficiaries Declaration or a Declaration on Holding Politically Exposed Positions - use the "Download" button in this step for the template. You can only proceed after attaching the required file. If no declaration is required you go straight to step 2.4. For foreign entities the system may require registry documents in translation (at least into English, sworn or officially certified).

2.4. Pay activation fee

After completing all required data, pay the activation fee - this submits your data for verification. The fee is non-refundable. In this step you also accept the GTCPS (current text on Tpay's website). Click "Pay activation fee" - you will be redirected to the Payment Panel to make the transfer. Until the transfer is credited in the MP the "Verify account" button will still be visible (clicking it shows a message that the transfer is pending); after it is credited the button disappears.

Statement confirmation

Confirm the statement to proceed to the final step.

I declare that I am authorised to conclude the agreement with Tpay and accept the General Terms of Payment Services (GTCPS).

The AML department processes cases in order of receipt; there is no way to expedite via sales or Customer Service. After successful verification the account status is "Active"; test mode remains on - to accept real payments, turn it off in MP - Settings - Test mode. You will receive an email about successful verification. The moment your account is successfully verified is the moment the Payment Services Agreement is concluded.

In Zevio, before disabling Tpay test mode you must confirm you reviewed this activation guide (checkboxes in the modal).

Detailed sandbox scenarios

Organization settings → Payment providers → Activate Tpay account. After registration, select Tpay for BLIK and/or cards.

BLIK

  • BLIK code starting with 777 (or another 777xxx).
  • BLIK test code range.
  • Recurring BLIK registration: use amounts ending in .08-.15 (e.g. 10.08, 19.14).
  • Payment may succeed even if BLIK is not saved for recurring charges (per-code test limits).
  • 999*** codes: every 15 min the oldest saved entries are removed, the 20 most recent are kept.
  • 777*** codes with an amount ending in .08 (e.g. 15.08) stay active for at least a week.
  • Zevio sandbox, all BLIK providers: simulates a bank without recurring BLIK support. When "Start manual BLIK recurrence when the bank is unsupported" is on (refuseNoPayId: false), payment succeeds as one-time BLIK with manual recurrence; otherwise Zevio will offer a fallback offer or manual code entry.
  • 495.00 PLN + any 777*** code: simulates a bank without recurring BLIK.

Cards

  • Test card numbers only. Any cardholder name, future expiry date, 3-digit CVV.
  • success.
  • 3D Secure outcome depends on amount cents: .01 no extra step, .03 and .05 different scenarios, .06 decline, other amounts - extra confirmation.
  • Forced errors at amounts: 500.00, 501.00, 503.00 (card and wallet); 504.00 for saved-card payment.

Apple Pay / Google Pay

  • Redirect to Tpay. Apple Pay in Safari, Google Pay in Chrome / on Android. The card in the wallet is not charged.
  • Apple Pay: Safari on iPhone/iPad/Mac with a card in Wallet → confirm on Tpay → success.
  • Google Pay: Chrome or Android, join the googlepay-support-tpay test group, add a test card → confirm on Tpay → success.
  • Amounts 500.00, 501.00, 503.00 PLN - forced error (same as cards).
  • Subscription offer: use card or BLIK. Apple Pay and Google Pay on subscriptions work only with Stripe.
Tpay sandbox documentation: https://support.tpay.com/sprzedawca/srodowisko-testowe-sandbox