Payment providers

Zevio orchestrates multiple operators in one organization: Tpay, Przelewy24, PayU, AutoPay, Stripe Connect Express. Credentials and onboarding live under Organization settings → Payment integrations. After connecting an account, select the Payment operator separately for card and BLIK - only then are methods routed through that PSP.

Launch order

  • Complete organization company data (NIP and fields used in PSP onboarding).
  • Connect at least one operator (credentials / Express / activation link) - full steps on Tpay, P24, PayU, Autopay, Stripe pages.
  • Configure notifications/URLs where the instruction requires it (Tpay and AutoPay manually; P24/PayU/Stripe usually automatic).
  • In Payment operator, select the active BLIK and/or card operator.
  • Run a Sandbox test payment (in-panel sandbox notebook).
  • Before Production, disable test mode using the status modal (Tpay / PayU / Stripe).

Method matrix (summary)

  • BLIK - PLN only; operator: Tpay / P24 / PayU / AutoPay / Stripe (when selected).
  • Recurring BLIK in the offer UI: model O.
  • Cards - depends on operator (Stripe Elements, PayU Secure Form, Tpay/P24/AutoPay redirect).
  • Apple Pay / Google Pay - per operator; wallet subscriptions only via Stripe.
  • EUR - typically PayU EUR POS (cards/wallets); not BLIK.

Enums

  • Provider: STRIPE | TPAY | AUTOPAY | P24 | PAYU
  • Methods: BLIK, BLIK_RECURRING, BLIK_MANUAL_RECURRING, CARD, CARD_MOTO, wallets

Instruction pages

  • Tpay
  • Przelewy24
  • PayU
  • Autopay
  • Stripe Connect
Each child page contains the full steps from the in-app Instruction modals under Payment integrations - the same copy as the product.