Payment gateways
Configure offline bank payments and review references
Publish seller-matched instructions and approve only funds independently confirmed on the bank statement.
About 3 min read
On this page
Choose the installed workflow
The legal-name matching rules in this baseline guide describe the approved licensed 1.3.8 implementation. The reviewed newer source separates System bank-method configuration from Business review and allows an explicitly configured bank account holder to differ from the seller. Use the newer payment workspace manual only with that matching released core; do not assume a website documentation update changes the installed payment rules.
Enable the correct module and scope
Install and enable the reviewed Offline Payments addon through Modules & addons. Open Offline payments; settings changes require settings.manage, and accepting a submission requires payments.record. Free module installation and merchant bank configuration are separate steps.
| Method field | Required decision |
|---|---|
| Brand and optional storefront | The invoice's issuing seller; an existing method cannot move between them. |
| Country and currency | The seller's legal country and an enabled invoice currency. |
| Title | A clear customer label, such as Bank transfer. |
| Merchant legal name | Must match the configured legal seller after whitespace/case normalisation. |
| Instructions | Actual bank details and payment-reference instructions, up to 6,000 characters. |
| Merchant acknowledgement and active | Explicitly confirm ownership before enabling. |
A method with submission history cannot change its merchant, country or currency; create a separate method instead. The active brand must allow offline sales. The invoice must be payable and have a known legal country and seller. An unrelated seller's bank details must never be shown as fallback.
Customer workflow
Open an unpaid invoice, read its bank instructions and transfer funds using the requested reference. A verified customer with billing.pay submits the method, positive amount within the balance, bank reference and optional note. This creates pending evidence, not payment or licence/hosting activation. One unresolved reference or online checkout prevents conflicting payment starts; an exact repeat of the same pending reference is idempotent.
Staff review
Check the merchant's bank statement independently. Accept with the confirmed amount, actual received date, a meaningful review note and the settled-funds acknowledgement, or reject with a reason. Acceptance records the normal payment ledger entry once; it does not perform a transfer. The accepted amount may reflect the actual settled amount within the current balance. Do not approve solely from an uploaded image or customer claim.
Missing methods
Check module integrity/enabled state, active merchant acknowledgement, nonempty instructions, exact brand/storefront, country, currency and legal name. A method configured for another seller or currency is intentionally unavailable. Inspect an in-progress checkout or pending reference before retrying. The module's workspace and status actions provide navigation/status only; its event handler performs no payment mutation.