What are the responsibilities and job description for the Bank Transfer Revolution position at mypresta.rocks?
A euro order paid into a pound account, or an old IBAN copied from an invoice printed last year, turns a simple transfer into a week of reconciliation. Bank Transfer Revolution keeps a bank account per currency, can show several on one order and freezes those details on the order, so the paperwork still matches months later.
PrestaShop Bank Transfer keeps one set of account details per currency and picks the right one from the currency the order is actually placed in – not whatever the shopper happened to be browsing in. A single account on every order quietly costs you money: someone paying in pounds into a euro account loses on conversion, or the transfer is returned days later. If nothing matches an order, the method stays hidden rather than showing an account that would receive the payment badly.
Yesterday's orders keep yesterday's details
When a store changes bank, the usual result is that every unpaid order silently starts showing the new account – including orders whose confirmation email quoted the old one. Customers pay into a closed account and someone loses a morning untangling it. Here the details are copied onto the order the moment it is placed, and every later screen and email reads that copy. Editing an account changes what new orders are told, and nothing else.
Payments you can actually match to orders
Bank statements arrive as a list of amounts and half-remembered names, and without something to match on, reconciliation turns into guesswork. You decide the shape of the payment reference – your own prefix with the order reference, order number or customer number – and it appears on the payment step, the confirmation page, the order page and the email, identical every time. When the money lands, the reference on the statement is the one you are looking for.
A scannable code instead of a typed IBAN
Copying a 22-character IBAN into a banking app on a phone is where transfers go wrong – one wrong character and the payment bounces or lands somewhere else. For euro accounts the instructions include a scannable code that fills in the payee, account, amount and reference in most European banking apps. It is drawn on your own server as part of the page, so no order or payment detail is sent to an outside service to produce it. Accounts in other currencies simply show the details without a code.
See who still owes you, and chase it
Unpaid transfer orders pile up quietly, and the ones worth chasing are the ones nobody notices. A dedicated screen lists everything still awaiting payment with the amount outstanding, the reference and how long it has been waiting, so the oldest rise to the top. You can mark an order paid from there in one step. Reminder emails go out on a schedule you set, and orders still unpaid after a number of days you choose can be cancelled automatically, which returns the reserved stock to your catalogue.
Built to sit quietly in your store
The module installs no core overrides, so it will not fight your theme or stand in the way of a PrestaShop upgrade, and it runs from 1.6 through 9 on one codebase. Multi-store setups keep their accounts apart: details set up for one shop are never offered on another. It is worth being plain about the boundary – the module presents and tracks the transfer, it does not connect to your bank, so marking a payment received stays a decision you or your team make.
PrestaShop 1.6 to 9, PHP 7.1 and newer
One ZIP installs on every PrestaShop release from 1.6 through the current 9.x, and runs on PHP 7.1 and every version since.
- Flexible account fields. IBAN and BIC, UK sort code, US routing number, bank address, plus your own labelled rows for anything a particular bank needs.
- Hidden when nothing fits. If no account matches the order, the payment method does not appear at checkout at all, unless you deliberately configure a catch-all.
- Chosen on your server. The account is worked out from the order itself, so nothing arriving with the request can influence which details a customer is shown.
- Matching beyond currency. Optional rules narrow by country, zone, customer group, carrier or order value, and the most specific rule wins.
- Instructions in each language. Add your own wording per language, shown alongside the account details wherever they appear.
- Split baskets stay one payment. When a basket becomes several orders, the customer is asked for a single transfer covering the combined total.
- Retire an account without deleting it. Switching one off stops new orders selecting it while it stays in your list, so older orders can still be traced back to it.
- Visible to your team. The back-office order page shows support the exact details the customer received, next to the amount still outstanding.
PrestaShop Bank Transfer keeps one set of account details per currency and picks the right one from the currency the order is actually placed in – not whatever the shopper happened to be browsing in. A single account on every order quietly costs you money: someone paying in pounds into a euro account loses on conversion, or the transfer is returned days later. If nothing matches an order, the method stays hidden rather than showing an account that would receive the payment badly.
Yesterday's orders keep yesterday's details
When a store changes bank, the usual result is that every unpaid order silently starts showing the new account – including orders whose confirmation email quoted the old one. Customers pay into a closed account and someone loses a morning untangling it. Here the details are copied onto the order the moment it is placed, and every later screen and email reads that copy. Editing an account changes what new orders are told, and nothing else.
Payments you can actually match to orders
Bank statements arrive as a list of amounts and half-remembered names, and without something to match on, reconciliation turns into guesswork. You decide the shape of the payment reference – your own prefix with the order reference, order number or customer number – and it appears on the payment step, the confirmation page, the order page and the email, identical every time. When the money lands, the reference on the statement is the one you are looking for.
A scannable code instead of a typed IBAN
Copying a 22-character IBAN into a banking app on a phone is where transfers go wrong – one wrong character and the payment bounces or lands somewhere else. For euro accounts the instructions include a scannable code that fills in the payee, account, amount and reference in most European banking apps. It is drawn on your own server as part of the page, so no order or payment detail is sent to an outside service to produce it. Accounts in other currencies simply show the details without a code.
See who still owes you, and chase it
Unpaid transfer orders pile up quietly, and the ones worth chasing are the ones nobody notices. A dedicated screen lists everything still awaiting payment with the amount outstanding, the reference and how long it has been waiting, so the oldest rise to the top. You can mark an order paid from there in one step. Reminder emails go out on a schedule you set, and orders still unpaid after a number of days you choose can be cancelled automatically, which returns the reserved stock to your catalogue.
Built to sit quietly in your store
The module installs no core overrides, so it will not fight your theme or stand in the way of a PrestaShop upgrade, and it runs from 1.6 through 9 on one codebase. Multi-store setups keep their accounts apart: details set up for one shop are never offered on another. It is worth being plain about the boundary – the module presents and tracks the transfer, it does not connect to your bank, so marking a payment received stays a decision you or your team make.
PrestaShop 1.6 to 9, PHP 7.1 and newer
One ZIP installs on every PrestaShop release from 1.6 through the current 9.x, and runs on PHP 7.1 and every version since.