¶ Payments - methods and integrations in Hummerce
Payments in Hummerce bring together ready-made online integrations (PayU, Przelewy24, PayPal, InPost Pay, installments and leasing), internal payments (e.g. loyalty points, cash on delivery) and non-integrated payments (e.g. bank transfer) in one shared configuration mechanism - with assignment to store views, its own messages and statuses.
As of Hummerce 2.20 (payment assignment to views, top-up payments, repeating and changing payment), updated 2026-09-29.
¶ Benefits and use cases
- One payment, many views - a payment can be assigned to only selected store views (e.g. different payments for B2B, different for B2C or for foreign sales).
- Custom messages for each payment - the description, success, error and warning messages can be set separately for each method.
- Automatic top-up of the difference - when an order hasn't been paid in full (e.g. after an edit by staff), the customer gets the option to pay the difference without contacting support.
- Repeating or changing the payment without support's help - a customer whose payment failed can try again or choose a different method.
- Ready-made online payment integrations in the platform standard - PayU, Przelewy24 with BLIK (a popular Polish mobile payment method), PayPal, InPost Pay, and installments and leasing.
- Payments integrated with external modules (e.g. PayU, Przelewy24, PayPal, InPost Pay) - newer integrations have more capabilities and work with the provider's current API; older integrations (from before 2016) have limited functionality and are gradually being replaced by newer ones.
- Internal payments - tied to platform modules, e.g. payment with loyalty points or cash on delivery.
- Non-integrated payments - e.g. bank transfer, with no connection to an external system.
¶ Assignment to views and order on the list
- From version 2.20, every payment has a Views setting that determines which store views it's available in.
- The payment list can be two-level (a parent payment and sub-payments, e.g. individual banks within one integration) and can be sorted freely.
- The currently selected payment in the cart comes from: the last payment chosen and saved in the cart or in a cookie, or if there is none - from the default payment set in the configuration, and if that one is also missing or unavailable in the current view - from the first selectable one.
- When the customer has a remembered payment, the list is collapsed by default (it can be expanded with the change-payment-method button) - it can also be forced to always show fully expanded.
- The order of payments on the list, the default payment and its description text all affect cart conversion - it's worth setting them deliberately.
¶ Payment statuses and messages
- An order's payment status is independent of the order status and the delivery status - the full list of symbols is in Order, Payment and Delivery Statuses.
- After placing an order and on the order information page, the customer sees one of three messages: success (green), warning - orange (a non-integrated payment, or the online payment result isn't known yet), or error - red (the payment ended in an error or was canceled). The default text for each can be overridden separately for each payment.
- With integrated payments, after placing the order the customer is taken to a redirect page to the payment system, and after returning - to the order confirmation page with the payment status.
- In the order details, the Payments tab shows the history of successive payment attempts with their statuses.
When an order hasn't been paid in full - e.g. after an edit by staff, or with a partial payment - the store asks the customer to pay the missing amount on the order confirmation page and on the order information page. The mechanism relies on the Partially paid payment status, which in some cases has to be set manually.
¶ Repeating and changing payment (from 2.20)
- When a payment fails, the customer can repeat it or switch to a different method - without contacting support.
- For each payment, you set separately: whether it can be changed to another one, whether another one can be changed to it, and the list of payments excluded from switching (e.g. from bank transfer to cash on delivery).
- Default values for sub-payments are inherited from the parent payment, and for first-level payments - from the integration module's default settings, if that particular feature's module doesn't support it.
¶ Payment integrations in the standard
| Payment |
Version / API |
Use |
Documentation page |
| PayU |
REST API 2.1 (Classic API up to version 2.33) |
Payment card, fast bank transfers, PayPo |
PayU |
| Przelewy24 and BLIK |
REST API, from version 2.28 |
Fast bank transfers with an automatic bank list, BLIK with no redirect |
Przelewy24 and BLIK |
| PayPal |
Orders API v2, from version 2.34 (the older email-based integration is still available) |
PayPal account, international payments |
PayPal |
| InPost Pay |
Widget 2.0, from version 2.34 |
Fast purchase through the InPost app |
InPost Pay |
| Installments and leasing (LeaseLink, Santander eRaty), purchase on invoice (Ratepay) |
older platform versions |
Purchase in installments or leasing, also for businesses; in Germany purchase on invoice and direct debit |
Installments and leasing |
| PayU Classic, TrustPay, Paysera, mobilPay, Payline, Ingenico |
older platform versions |
Local payments in foreign markets (CZ, SK, LT, RO, FR, BE, NL) |
Payments in foreign markets |
- From version 2.20 - payment assignment to views, topping up the difference, repeating and changing payment.
- Individual online payment integrations have their own versions - see the table above and each payment's own page.
- An account and access data with the payment provider (PayU, Przelewy24, PayPal, InPost, an installments or leasing provider) - set up and configured by the store itself.
- Linking payments with deliveries - Delivery methods - overview.
- Default success, warning and error messages (Content -> Contents), or messages set separately for each payment.
- Non-integrated and internal payments work right after an update - they only need to be set up on the payment list (symbol, description, views, linked deliveries).
- Online integrations (PayU, Przelewy24, PayPal, InPost Pay, installments and leasing) each require their own implementation - the scope and time are described on each integration's page.
- Minimum estimated time: configuring a single non-integrated or internal payment (symbol, description, views, messages) - from 0.5 h. The time for a specific implementation depends on its scope - we quote it individually.
- Repeating a payment doesn't block the earlier attempt - in rare cases a customer can pay for an order twice with the same method; staff verify this manually in the order's Payments tab.
- Manually changing the payment status in the panel doesn't perform the operation in the payment gateway (e.g. a refund) - such operations are done in the payment provider's panel, or, if the gateway supports it, in the order's Payments tab.
- We do not verify the configuration for legal compliance - the terms of service and payment information are set by the store.
Can one payment be available only in selected store views?
Yes. From version 2.20, every payment has a Views setting that decides which views it shows in - useful e.g. with separate B2B and B2C views.
What happens if the customer doesn't finish an online payment?
It depends on the status: if the result isn't known yet, the customer sees a warning message and can check the status later; if the payment ended in an error or was canceled, they can repeat it or switch to a different method.
Can the customer change the payment method after placing the order?
Yes, if the previous payment failed - as long as the store allows it in that payment's settings (whether it can be switched to, and from which payments).
Which online payment integrations are available in the Hummerce standard?
PayU, Przelewy24 with BLIK, PayPal, InPost Pay, installments and leasing (LeaseLink, Santander eRaty), purchase on invoice with Ratepay and local providers in foreign markets - each has its own page with its implementation scope.
How long does setting up a new payment take?
It depends on the type: a non-integrated or internal payment can be set up from 0.5 h, while implementing an online integration (e.g. PayU, PayPal) is described on its own page.
Want to see how payments could work in your store? Contact the Hummerce team (in Polish).
- Default settings for all payments: Configuration -> Settings -> Technical configuration -> Payments.
- Default selected payment: Configuration -> Settings -> Orders -> Default payment.
- Managing the payment list: Configuration -> Payments - adding, sorting and sub-payments; the most important fields: Symbol, Views, Description, Cash on delivery, Online payment type, Possible deliveries, Success / error / warning description, and the repeat and switch-payment settings.
- Default messages: Content -> Contents -
defaultPaymentSuccess, defaultPaymentAlert, defaultPaymentError (can be overridden separately for each payment).