Settings
Open Add-ons > Manage add-ons > PayU for CS-Cart and Multi-Vendor > Settings.
General
Section titled “General”| Setting | Default | Description |
|---|---|---|
| Enable | On | When off, no new work is started. Jobs and webhooks of work that is already under way are still processed. |
| Marketplace owner mode | On | On: every order is processed with the marketplace owner’s account, vendors have no connection page and only the owner’s administrators can refund. Off: each vendor connects their own account, PayU is offered only for carts with one vendor whose account is connected, and the vendor refunds their own orders. |
| Debug log | Off | Also stores every HTTP call with masked request and response. Secrets are never stored. |
| Log retention (days) | 90 | Older log entries are removed by the cron run. |
| Order status when the payment is paid / failed / canceled | P / F / I | The order status set from the payment result. An order is never moved backwards. |
| Order status while the payment is still pending at PayU | O (Open) | Set when the customer comes back from PayU and the payment is not final yet (pay-by-link, BLIK confirmation). The order is then placed and waiting, the customer sees a waiting page that updates by itself, and the store does not offer to pay the order again. |
| Refund in full when the order status becomes | empty | A paid order that reaches this status is refunded once. Empty = refund by hand. |
Connection
Section titled “Connection”Credentials are not ordinary settings: they are entered on the Connection page and stored encrypted (AES-256-GCM, key derived from your store’s own secret). They are never shown again; leave a secret field empty to keep the saved value.
| Field | Description |
|---|---|
| Mode | Test uses the test credentials and the provider’s sandbox; Live uses the live credentials. |
| OAuth client ID (POS ID) | The POS ID of your PayU point of sale (digits). In PayU the OAuth client ID equals the POS ID. |
| OAuth client secret | The client secret of the POS (PayU panel > POS configuration). Used to obtain the OAuth access token. |
| Second key (MD5) | The second key of the POS. Every PayU notification is signed with it (OpenPayu-Signature); a notification that does not verify is rejected. |
| POS ID (only if different) | Optional. Only fill it when your merchantPosId differs from the OAuth client ID. Empty = the client ID. |
Payment method
Section titled “Payment method”In Administration > Payment methods choose the processor PayU. The field Payment description is the text before the order number in the PayU order (shown on the PayU page and the bank statement line of some banks).
Currencies: PLN, EUR, CZK, GBP, USD, HUF, RON, CHF, DKK, NOK, SEK. The order is charged in its own currency when it is one of these and otherwise converted to your store’s PLN currency. The POS you connect must settle the currency of the order, otherwise PayU refuses the order and the customer sees an error and can choose another method.
The queue runs from cron. Use either the command line or the secret web address shown in the Cron section of the settings:
php /path/to/store/admin.php --dispatch=kv_payu.cronhttps://your-store.example/index.php?dispatch=kv_payu.cron&key=<secret>
Log and jobs
Section titled “Log and jobs”- Log lists every call, job and webhook with filters (level, action, text, dates) and a CSV export.
- Jobs lists the queue. A job that fails is retried after 5 minutes, 15 minutes, 1 hour, 3 hours and 12 hours, then marked “Gave up”; use Retry to queue it again.
Multi-Vendor
Section titled “Multi-Vendor”In the vendor panel a vendor sees only their own records. With the marketplace owner mode on, vendors cannot refund and cannot run the queue; the payments sit on the owner’s account. With the mode off the vendor gets the Connection tab for their own account and refunds their own orders.
Rules in vendor mode (owner mode off): PayU is shown at checkout only when all products of the cart belong to one vendor and that vendor has saved working credentials. A mixed cart never reaches PayU, so no vendor’s money is charged to another account.
Requirement: auto-receive
Section titled “Requirement: auto-receive”Keep auto-receive switched on for the POS in the PayU panel. If PayU reports WAITING_FOR_CONFIRMATION the add-on logs a warning, shows it on the order’s PayU tab and leaves the order open; accept the payment in the PayU panel.