WSB HUB3 is a plugin for Woocommerce that shows all needed data for Croatian banks direct transfer payment, including on-the-fly generated barcode for mobile banking payment. Payment details and barcode are shown on thankyou page, order details page and also in notification email. Details are visible only if selected payment method is Bank transfer and order status is the one selected in general settings (default: on-hold).
Plugin uses bigfish.software API to generate barcodes: https://hub3.bigfish.software/.
You can display payment details to the customer either in text/html format, or generated HUB-3A slip in jpg with all details on it.
If admin updates an order from the backend (i.e. adds a new product to the order or apply a coupon code), barcode and HUB3 slip will be re-created.

Need locally generated HUB-3 barcodes or SEPA QR codes?

WSB PayByCode for WooCommerce is a separate paid alternative supporting Croatian HUB-3 barcodes and EPC QR codes for compatible banking apps. It generates payment codes locally on your server and adds payment reminders and bank account rules. WSB HUB3 remains free and maintained. Deactivate WSB HUB3 when switching to PayByCode.

3.0.1: If there is more than one IBAN (bank accounts) in BACS payment method, customer can choose which one to use for payment at checkout. If only one IBAN, no choice is shown.

3.1.0: Big update focused on payments that banks accept, a better customer experience and privacy:

FINA rules for payment models and references: choose HR00, HR01 (check digit added automatically) or HR99. The reference follows FINA rules (at most 3 numeric parts separated by hyphens, 22 characters), and the settings show a live preview for your latest order.
HUB-3 validation: settings accept only values the HUB-3 barcode allows, with live character counters, input masks and IBAN check digit validation. Croatian letters and text pasted from other documents are handled correctly.
Bank account choice in block and classic checkout: with more than one Direct bank transfer account, customers choose one at checkout (radio buttons under the payment methods), and the slip and barcode use that account.
Images embedded in emails: slip and barcode are sent inside the email, so they show even when the website is not reachable (e.g. Cloudflare “Under attack” mode) or the email client blocks external images.
Safer image storage: images are stored in the uploads folder, so plugin updates no longer delete them, and file names contain a random part, so other customers’ slips can’t be opened by guessing an order number. Missing images are recreated automatically.
Shortcodes on custom thankyou pages: [wsb_hub3] and [wsb_barcode] now work on any page, shown only with a valid order key or to the customer who placed the order. The new Nothing (use shortcodes) option prevents showing payment details twice.
Clear messages when something is wrong: admin notices for settings that banks or the barcode service would reject, and order notes and WooCommerce logs when a barcode can’t be generated or the reference had to be adjusted.
Compatibility: declared compatible with WooCommerce Cart and Checkout blocks and HPOS; bundled Croatian translations fill in strings missing from the WordPress.org language pack.

After updating, check the payment model and reference in HUB3 recipient settings, and the bank accounts in the Direct bank transfer payment method.

Requirements

PHP version 7.4 and above
GD library installed on server
WordPress version 5.0 and above
Woocommerce plugin installed and enabled (v 7.1 or greater)
Direct Bank Transfer payment plugin (BACS) enabled
EUR as a default payment currency

Features

Sequential order number plugins supported
Multiple IBANs: customers choose the bank account at checkout (block and classic checkout)
Selectable display options for payment details
JPG, PNG or GIF format can be selected for barcode image
Adjustable reference number pattern with live preview in settings
Payment models HR00, HR01 (check digit added automatically) and HR99
Validation according to HUB-3 and FINA rules, with live character counters and input masks in settings
IBAN check digit validation
Payment details on thankyou page, order details page and in notification email.
Slip and barcode embedded in emails, so they show even if the website is not reachable
Barcode image in your favorite color
Payment details shown only to Croatian customers (optional)
Placeholder [order] can be used in payment description (order ID)
Shortcodes for HUB3 slip and barcode display on custom thankyou page
Order notes and WooCommerce logs when a barcode can’t be generated

More about WSB PayByCode

PayByCode replaces WSB HUB3; it is not an add-on or an unlock inside the free plugin. The two plugins are not intended to run together.

WSB PayByCode offers:

Local generation, privacy and GDPR: customer and payment details needed to generate payment codes are processed on your store’s server, without sending them to an external barcode service. This reduces third-party processing and gives you more control over personal data in the context of GDPR.
No network wait for code generation: no sending data over the network or waiting for a barcode API response. Actual generation time still depends on your server.
Independence from a barcode service: code generation does not depend on an external service’s availability, rate limits or response times.
Wider coverage: HUB-3 for Croatia and EPC QR codes for supported SEPA payments. Scanning EPC QR codes requires a banking app that supports the format; SEPA support alone does not mean that an app can scan EPC QR codes.
Bank account rules: manage accounts by country and currency, with an optional account choice at checkout.
Follow-up and practical tools: payment reminders, automatic cancellation of unpaid orders, copy buttons for payment details, WP Overnight PDF invoice integration, and custom text translations through Polylang or WPML.

The privacy benefit applies to payment code generation. License activation and update checks communicate separately with the licensing and update service. Local generation alone does not guarantee GDPR compliance.

PayByCode requires PHP 8.2+, WordPress 6.5+ and WooCommerce 9.0+. A paid license includes one year of updates and email support. The installed plugin’s features continue to work after the license expires.

To switch: back up your site, deactivate WSB HUB3 without deleting its settings, then install and activate WSB PayByCode. In PayByCode > Import WSB HUB3, review and import your existing settings and order data; import also works while WSB HUB3 is inactive. Check your bank accounts and display settings and place a test bank transfer order. Keep WSB HUB3 deactivated when using PayByCode.

Reference number pattern

For payment reference number you can select one of several predefined patterns:
– order (can be custom order number provided by other plugin)
– date
– order-date
– date-order

If you use date in the reference number, then you can select its format:
– ddmmyyyy
– ddmmyy
– ddmm
– mmyyyy
– mmyy
– yyyy
– yy

Also you can add sufix and/or prefix to the reference number (up to 6 digits for each). The recipient settings show a live preview of the reference for your latest order.

The reference follows FINA rules:
– at most 3 parts, so with order-date or date-order use either a prefix or a sufix, not both
– digits only; other characters in order numbers (e.g. WEB-123) are removed
– at most 12 digits per part and 22 characters in total, including hyphens

If a reference would still be too long (e.g. when order numbers grow), the sufix, then the prefix, then the date are left out. The order number is always kept, and a note is added to the order.

Payment model

HR00: reference without check digit
HR01: check digit (MOD11INI) is added to the reference automatically
HR99: payment without reference

Recipient data limits

The HUB-3 barcode allows only a limited number of characters, so the settings don’t accept longer values:
– Recipient name: 25 characters
– Address: 25 characters
– Postcode: 5 digits
– City: 21 characters (postcode and city together can have 27)
– IBAN: HR and 19 digits, with valid check digits
– Purpose code: 4 capital letters (e.g. OTHR)
– Payment description: 35 characters. When [order] is replaced with the order number, the text around it is shortened if needed.

If recipient data saved with an older plugin version is too long, a notice is shown in the admin area.

Bank accounts (IBAN)

The slip and barcode use the bank accounts of the Direct bank transfer payment method:
– one account: it is used automatically
– more accounts: the customer chooses one at checkout, shown as radio buttons under the payment methods (block checkout) or in the bank transfer description (classic checkout)
– no account with a valid IBAN: the IBAN from HUB3 recipient settings is used

When Show bank accounts is enabled, the chosen account is listed first and marked on the thankyou page and in emails.

Emails

Slip and barcode are embedded in emails, not linked from the website. They show even when the website is not reachable (e.g. Cloudflare “Under attack” mode) and in email clients that block external images. If your email plugin sends emails through an API that doesn’t support embedded images, turn off Embed images in emails in the general settings.

Shortcodes

[wsb_hub3 width="1100"] shows the HUB-3A slip
[wsb_barcode width="400"] shows the barcode

Use them in the Order Confirmation template (block themes), on the checkout page (classic themes) or on a custom thankyou page that has order_id and key in its URL (e.g. ?order_id=123&key=wc_order_...). They show images only for a valid order key in the URL or to the logged-in customer who placed the order. To avoid showing payment details twice, set Show on thankyou page to Nothing (use shortcodes).

Where are the images stored?

Slips and barcodes are stored in wp-content/uploads/wsb-hub3/, with a random part in each file name, so they can’t be found by guessing an order number. Images of orders from older plugin versions are moved there or recreated automatically when needed.