Bank Transfer Accounts: setup and help

Upload the Bank Transfer Accounts ZIP from your back office's Modules page and install it.

Requires PrestaShop 1.6.0.0 or later and PHP 7.1 or later.

Prepare your receiving bank details. You do not need a bank login or external service key. The module displays transfer instructions. You check your bank and confirm payment yourself. Legacy checkout uses displayPayment; PrestaShop 1.7 and later uses paymentOptions.

Select one shop if multishop is enabled. You must have access to that shop and the relevant employee permissions to add, edit or retire accounts. Settings require edit permission. Accounts and currency assignments belong to the selected shop and this module.

Open Bank Transfer Accounts to reach the Bank accounts screen. Use the installed module card's Configure action to reach Configuration. The generated menu groups Configuration under the module's Settings area.

1. Open Bank accounts in the shop you want to configure and add an account.
2. Enter Internal label. Enter Account holder in the shop's default language.
3. Enter at least one complete payable identifier set: IBAN, both UK fields or both US fields. Fill any other identifiers your bank requires.
4. Select the intended Currencies, keep Active set to Yes and save.
5. Open Configuration. Keep Bank accounts on the confirmation page set to The account for the order currency, or choose All bank accounts. Save.
6. Check PrestaShop's payment restrictions, then place a test order with Pay by bank transfer in each supported currency.
7. Verify the confirmation amount, reference and bank details. Check the instructions email and reopen the order while it is in Awaiting bank transfer.

Use your own bank details. The reference images contain example account information and do not provide details for real payments.

You use the same form to add or edit an account. A new account starts active, with Position 0, empty identifiers and empty translated text.

Empty translations of account details fall back to the shop's default language. Translate Display name, Account holder, Bank name, Bank address, Payment instructions and Note where needed. The identifier fields themselves are shared across languages.

At least one complete payable set is required: an IBAN, a UK sort code and account number pair, or a US routing and account number pair. A BIC alone is insufficient. Every supplied identifier is checked, even if another valid set is present.

Whitespace is removed from identifiers and letters are uppercased. Hyphens are also removed from UK sort codes. The module checks IBAN country length and checksum, BIC structure and country code, UK digit lengths, and US routing structure and checksum. Leave unused optional fields empty rather than entering placeholders.

There is no bank-format dropdown. Fill the identifiers relevant to your account. The display includes non-empty fields from the selected account. It does not infer a separate format from the order currency.

For a GBP receiving account, enter UK sort code and UK account number. You can also enter a valid IBAN and BIC if you want customers to have those details.

For a USD receiving account, enter US routing number and US account number. Optional empty identifiers are omitted from the displayed details.

Use Payment instructions for explanatory text. Add Custom labelled rows for other bank information. Translate both the row label and its value. For example, add a Branch label and the bank's branch value.

You can save up to 50 custom rows per account. Each non-empty translated value needs a label. A saved custom row also needs a label in the shop's default language. Empty translated custom rows can fall back to that language. The row sequence follows the saved custom-row order.

Use Currencies to select the order currencies assigned to this account. A currency has one assignment per module and shop. Assigning it to another account moves that assignment.

For a new account, saving with no selected currencies assigns every active shop currency that is still unassigned. For an existing account, clearing Currencies removes its assignments. Deactivating an account keeps its assignments but makes it unavailable to customers.

For example, assign EUR to the account you want selected for EUR orders. Assign GBP to the account you want selected for GBP orders. One account can cover more than one currency if those are the receiving details you intend to provide.

Open Configuration. Bank accounts on the confirmation page is a radio setting with two choices. The default is The account for the order currency.

Save after choosing the mode. This selection also controls the account details in the instructions email and reopened order pages.

In All bank accounts mode, a EUR order can show an active USD account as well as an active EUR account. With three active accounts, the customer receives three sets of bank details. The displayed order amount remains in the order currency. The module does not calculate a separate converted amount for each receiving account.

In currency mode, Configuration warns about active shop currencies without an active assigned account. Edit an account, assign those currencies and enable it. Disabling a previously assigned account can cause the warning without resetting your other settings.

The module adds one Pay by bank transfer choice to checkout. Customers do not select a separate checkout payment method for each receiving account.

Check PrestaShop's payment restrictions for currency, customer group, country and carrier where applicable. Then place a test order in each currency you offer. Confirm the intended account selection on the order confirmation page.

The module creates the order in its own Awaiting bank transfer state. This is an unpaid state. The confirmation provides the amount to transfer, order reference and selected bank details. For split orders sharing a cart and reference, the confirmation can combine the outstanding amount across the related module orders.

During order creation, the module attempts to send an instructions email for each order. It includes that order's amount, reference and selected accounts in the order language. The awaiting state itself has email sending disabled, so it does not produce an additional state-triggered bank-instructions email.

Check actual delivery through your shop's mail system. An instructions-email failure is logged and does not stop order creation. The module does not provide a scheduled retry or reminder process.

Customers can reopen authorized order details while the module's order remains in Awaiting bank transfer. The instructions use the currently configured account selection and details. Editing an account, changing display mode or changing assignments can therefore change existing order pages. Emails already sent keep their original content.

Copy buttons are provided for account holder, bank name, supplied identifiers and custom rows. Copied appears after a successful copy. Bank address, Note and formatted Payment instructions are not copy fields. The amount and order reference do not have these account-field copy buttons.

Verify receipt in your bank, then update the order state in PrestaShop. The module does not connect to your bank, reconcile transactions or mark an order paid automatically. It does not provide transfer discounts, QR codes, reminders or automatic cancellation.

The account list shows the internal label, display name, bank, masked account, active status and position. Use the edit form to change details. Bulk actions can enable, disable or retire selected accounts. Deleting through the account list retires the account and removes it from customer selection.

If the awaiting state is unavailable, open Integrity and check Awaiting bank transfer state. Its repair action can restore the module's state and shop mapping. Repairs require edit permission.

Back up your account details, translated instructions, custom rows and settings before removal. Resolve outstanding transfers and retain the information customers need for existing orders.

Uninstalling removes this module's accounts and configuration. Its awaiting state is retained when orders or order history still use it. An unused owned state can be removed.

If you move to another payment module, verify its account data and checkout instructions before removing this one. Account migration is not performed by this module's uninstall action.