- Accueil
- Apps
- SaaS Tools
- Deferred / Offline Bank Transfer Payment for Magento 2
Aperçu illustratifA custom-built Magento 2 / Adobe Commerce payment method that lets MENA and South-Asia merchants accept manual
bank transfers: it shows per-store bank account details at checkout, stamps a unique payment reference on every order, takes a customer proof-of-payment upload, routes orders into an admin verify-and-approve queue, and auto-cancels unpaid orders on a cron timeout. Built, installed and supported by
ECOSIRE — not an instant Marketplace download.
Qu'est-ce que Deferred / Offline Bank Transfer Payment for Magento 2 ?
A custom-built Magento 2 / Adobe Commerce payment method that lets MENA and South-Asia merchants accept manual bank transfers: it shows per-store bank account details at checkout, stamps a unique payment reference on every order, takes a customer proof-of-payment upload, routes orders into an admin verify-and-approve queue, and auto-cancels unpaid orders on a cron timeout. Built, installed and supported by ECOSIRE — not an instant Marketplace download. Built to order by ECOSIRE for Magento 2 / Adobe Commerce (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
Fonctionnalités clés
Fait sur commande, clé en main
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
- 1
Vous commandez
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
- 2
Nous développons et installons
ECOSIRE la développe, la configure et l'installe sur votre Magento 2.
- 3
Mise en ligne + assistance
Vous êtes en ligne en une semaine ouvrée environ, avec deux semaines d’assistance après la mise en production. Les défauts du code que nous livrons sont corrigés gratuitement.
À propos de ce produit
Magento Open Source ships a thin "Bank Transfer Payment" core method that does little more than print static instructions and drop orders into Pending. It has no per-store bank accounts, no unique reference per order, no proof-of-payment upload, no structured approval queue, and no automatic cleanup of abandoned transfers. For merchants in MENA and South Asia — where bank wire, IBAN transfer and over-the-counter deposit are still the dominant way customers pay — that gap means manual reconciliation, mismatched payments, and stale orders clogging the dashboard.
This extension is a real Magento 2 module delivered under app/code/Ecosire/BankTransfer. It registers a gateway method via Magento\Payment\Model\Method\Adapter and payment.xml, wired through di.xml with a custom CommandPool, ValueHandlerPool and a ConfigInterface-backed config provider. Checkout rendering uses a Knockout/UIComponent .js renderer so the method appears natively in the one-page checkout, and a GraphQL resolver plus REST endpoint expose it to headless / PWA Studio storefronts.
At checkout the customer sees the correct bank account for the active store view (driven by ScopeInterface::SCOPE_STORE), a unique payment reference generated against the order increment ID, and an upload field for their deposit slip. An sales_order_place_after observer persists the reference; uploaded proofs are validated and stored on the configured media/filesystem. Admins get a dedicated grid and a verify-and-approve action gated by a custom ACL resource, which invokes the invoice/order service contracts on approval. A cron job cancels orders left unverified past the configurable timeout and restocks them.
ECOSIRE builds, installs and supports this for you. We tailor the bank fields, reference format, email templates and timeout to your business, deploy it on your Open Source or Adobe Commerce instance, run setup:upgrade, and stand behind it.
Ce que vous obtenez
- Installable Magento 2 module under app/code/Ecosire/BankTransfer (or a Composer package) with registration.php, module.xml, di.xml, system.xml, payment.xml and ACL
- Source code tailored to your bank accounts, reference format, timeout and email copy, with PHPDoc and inline comments
- Admin configuration guide and a short merchant runbook for the verify-and-approve workflow
- Installation and deployment on your staging and production instances (setup:upgrade, di:compile, static-content:deploy) by an ECOSIRE engineer
- Transactional email templates (placement, proof received, approved, rejected) localized to your required locales
- Post-delivery warranty period with bug fixes plus optional ongoing support and Magento version-compatibility updates
Pour qui c'est
MENA / Gulf store owner taking bank wires
A UAE, Saudi or Egyptian merchant whose customers prefer IBAN bank transfer over cards. They need the correct local bank account shown per store view, an Arabic instruction block, and a clean way to confirm a wire arrived before shipping.
South-Asia merchant with manual deposits
A Pakistani, Indian or Bangladeshi seller accepting over-the-counter and online bank deposits. They want each order to carry a unique reference so they can match a bank statement line to an order, and an upload field so the buyer can attach the deposit slip.
Operations / finance admin
The person who reconciles payments daily. They live in the admin verify queue, approve or reject proofs, and rely on the cron auto-cancel to keep abandoned transfers from piling up — all under role-based ACL so only finance can approve.
Comment Deferred / Offline Bank Transfer Payment for Magento 2 se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Natif Magento 2 |
|---|---|---|---|---|
| Per-store-view bank accounts (multi-store / multi-currency) | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Unique payment reference per order | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Customer proof-of-payment upload with validation | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Admin verify-and-approve queue with ACL | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Cron auto-cancel of unpaid orders with restock | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| GraphQL / REST support for PWA Studio / headless | Inclus | Prise en charge partielle | Non inclus | Non inclus |
| Installed, tailored and supported for your store | Inclus | Prise en charge partielle | Non inclus | Non inclus |
| Arabic / Urdu RTL instruction blocks out of the box | Inclus | Prise en charge partielle | Non inclus | Prise en charge partielle |
Foire aux questions sur Deferred / Offline Bank Transfer Payment
How long does delivery take, since this is build-to-order?
This is not an instant Adobe Commerce Marketplace download. After we confirm requirements (your bank accounts, reference format, locales and timeout), a typical build is 5 to 10 business days. We then install it on your staging instance for sign-off before deploying to production. If you need a faster turnaround we will tell you honestly whether the timeline is feasible.
Do I get ongoing support and updates after install?
Yes. Every build includes a warranty period covering bug fixes at no extra cost. Beyond that we offer an optional support and maintenance arrangement that covers compatibility updates as you upgrade across Magento 2.4.x / Adobe Commerce minor versions and PHP releases, plus enhancements. You own the source code either way.
Does this work on Adobe Commerce as well as Magento Open Source?
Yes. The module targets both Magento Open Source 2.4.x and Adobe Commerce 2.4.x on PHP 8.1 to 8.3. It uses standard service contracts and the payment gateway framework, so it does not depend on any edition-locked feature. If you run a B2B or multi-website Adobe Commerce setup we wire the per-website bank accounts and customer-group restrictions accordingly.
How is this different from Magento's built-in Bank Transfer Payment method?
The core method only prints static instructions and leaves orders Pending. It has no per-store bank accounts, no unique reference per order, no proof upload, no approval queue, and no auto-cancel. This extension adds all of that, plus GraphQL/REST exposure for headless storefronts and a full admin audit trail.
Will it work with my PWA Studio or headless storefront?
Yes. Alongside the Luma/Knockout checkout renderer, we ship a GraphQL resolver and a REST endpoint that expose the payment method, its instructions and the generated reference, so a PWA Studio, Next.js or mobile-app checkout can offer offline bank transfer and submit proof through the API.
Modules associés

Custom Report Builder (Drag-and-Drop)
A drag-and-drop report builder for Magento 2 / Adobe Commerce that lets merchandisers and finance teams combine orders, products, customers, and shipments into unlimited bespoke reports — built, installed and supported by ECOSIRE on your store.

CyberSource Gateway for Magento 2
A build-to-order CyberSource (Visa Acceptance Solutions) payment gateway module for Magento 2 and Adobe Commerce — global card processing, Decision Manager fraud screening, tokenization, 3D Secure 2 and recurring billing, built and supported by ECOSIRE.

Easypaisa Gateway for Magento 2
A build-to-order Magento 2 payment method that lets Pakistani merchants accept Easypaisa mobile-wallet (OTP) and card payments natively at checkout, with auto order confirmation on successful payment.

eBay Marketplace Connector
A build-to-order Magento 2 extension that connects your store to eBay, syncing listings, inventory, pricing, and orders in real time. Custom-built, installed, and supported by ECOSIRE on your own Magento instance.
Deferred / Offline Bank Transfer Payment
A custom-built Magento 2 / Adobe Commerce payment method that lets MENA and South-Asia merchants accept manual bank transfers: it shows per-store bank account details at checkout, stamps a unique payment reference on every order, takes a customer proof-of-payment upload, routes orders into an admin verify-and-approve queue, and auto-cancels unpaid orders on a cron timeout. Built, installed and supported by ECOSIRE — not an instant Marketplace download.
- Native payment method registered via Magento\Payment gateway adapter (CommandPool / ValueHandlerPool / ConfigProvider), appearing in the standard one-page checkout step
- Per-store-view bank account details (bank name, IBAN/account number, SWIFT, branch, beneficiary) resolved through store scope so multi-store / multi-currency merchants show the right account
- Unique payment reference generated per order from the increment ID and persisted via an sales_order_place_after observer for easy bank-statement matching
- Customer proof-of-payment / deposit-slip upload with server-side MIME and size validation, stored on the configured Magento filesystem