Bank Details
Use the Bank Details query loop to show where a customer should send a direct bank transfer after placing an order. BricksUltimate reads the accounts configured in WooCommerce. One loop item equals one receiving bank account, letting you design one account card that repeats for every saved account.
This feature displays payment instructions. WooCommerce still owns the Direct bank transfer gateway, identified internally as bacs. The loop does not collect the customer's bank details, initiate a transfer, or mark the order as paid.
Configure WooCommerce and BricksUltimate
- Open WooCommerce → Settings → Payments. Enable and open Direct bank transfer. If you renamed the gateway, use the name shown in your payment settings.
- Under Account details, add the receiving account name and bank name, then fill in the local account number and routing details, or the IBAN and BIC/SWIFT, as appropriate. Save the settings. Add another account only when shoppers should see it as an additional transfer option.
- Under Bricks → BricksUltimate → Misc, enable Ultimate Woo Query Builder and save. This is the WooCommerce query provider, separate from Ultimate Query Builder.
- If you also want the dedicated (BU)Bank Details field element, enable Checkout Builder under Woo Elements. The field element is part of that element group. It is optional when using dynamic tags.
Build the Bank Details Loop
- Open your WooCommerce Thank you template in Bricks. If you use Bricks Checkout v2, place the section in its Thank you state. Use the WooCommerce order confirmation flow so there is a current order; a standalone WordPress page does not supply one.
- Add an outer section for the payment heading, instructions, and account cards. Add an inner Block that will repeat once per bank account.
- On the inner Block, enable Use query loop. Set the query type to Ultimate Woo Query Builder, then set Woo query type to Bank Details.
- Add Basic Text or Heading elements inside the repeated Block and insert the dynamic tags below. Keep the main payment heading and any order-level instructions outside the loop so they appear once.
- Set the payment conditions on the outer section, then save and place a test order using Direct bank transfer. Check that each saved account appears once.
Bank Account Dynamic Tags
Use Bricks' query_array tag with @key to read one field from the current bank account. This tag requires a Bricks version that supports query_array (introduced in Bricks 2.1). Use the exact keys in this table.
| WooCommerce field | Dynamic tag |
|---|---|
| Account name | {query_array @key:'account_name'} |
| Account number | {query_array @key:'account_number'} |
| Bank name | {query_array @key:'bank_name'} |
| Sort code / local routing code | {query_array @key:'sort_code'} |
| IBAN | {query_array @key:'iban'} |
| BIC / SWIFT | {query_array @key:'bic'} |
For example, put {query_array @key:'bank_name'} in a Heading and IBAN: {query_array @key:'iban'} in a Basic Text element below it. For optional fields, hide the entire label and value row when its dynamic value is empty. Avoid using {query_array} without a key on the storefront because it can output the whole account record.
Alternative: Use (BU)Bank Details
Inside the same repeated Block, add (BU)Bank Details. Under Content, select one field, then set the optional Label. Use Typography for the value, Label typography for the label, and Layout to arrange them. Add one instance for each field you want to show.
The dedicated element needs both a current order and a bank account loop item. On the storefront, it renders its field only for an order using bacs. Bank rows can still contain blank values, so include only the fields customers need or hide empty rows in your layout.
Show Instructions Only for Bank Transfers
- On the outer section, open Conditions. Choose Payment gateway and set it to equal Direct bank transfer (or your gateway's custom title). Keep the section in the Thank you template or state; use Is thank you page? as an additional condition if the same section can be used elsewhere.
- Optionally add an Order status condition if the instructions should appear only while payment is outstanding. A standard WooCommerce bank transfer order with a positive amount usually starts On hold. Verify that status against your own workflow before adding the condition.
- Test one bank-transfer order and one order using a different gateway. Also test the guest confirmation flow if guest checkout is enabled. These visibility conditions do not replace WooCommerce's order access checks; keep the section within the normal order confirmation flow and out of shared page caches.
Add the Amount and Payment Reference
In a text element outside the bank account loop, use the Woo Order Details tags to personalise the instructions for the current order:
- Payment reference:
{bu_cust_order_number}. Ask the customer to use this number so you can match their transfer to the order. - Order total:
{bu_cust_order_total_price}. For example, writePlease transfer {bu_cust_order_total_price} and use order {bu_cust_order_number} as the reference. - Payment method title:
{bu_cust_order_payment_method_title}shows the customer-facing gateway name.{bu_cust_order_payment_method}returns its internal identifier, such asbacs.
Include any instructions your store needs, such as the currency to transfer or when the order will ship. Keep the account details as selectable text so customers can copy long account numbers and IBANs. This layout changes the storefront only; the gateway's own email instructions are still configured in WooCommerce.
Multiple Accounts and Troubleshooting
- Multiple accounts: The loop reads all saved account rows in their stored order. It does not choose a bank account based on the order's currency or country, or run the filter that WooCommerce applies to its native BACS output. If customers must use a specific account, make that clear in the instructions and verify what the custom loop displays before publishing.
- The query type is missing: Make sure WooCommerce is active and Ultimate Woo Query Builder is enabled in Misc. Reopen the editor after saving.
- The loop or a field is empty: Confirm the account row was saved in the gateway settings. Check the exact tag key and make sure the field is inside the Bank Details loop, not inside a different nested loop.
- The field element is blank in preview: It needs an order as well as a bank account. An editor preview may not match the storefront order. Verify on the real confirmation screen for a test bank-transfer order.
- Bank details appear twice: WooCommerce's native BACS Thank you output may be present alongside your Bricks section. Check whether the template or hook element already renders the native instructions. Keep one storefront presentation without disabling the payment gateway or its email instructions.