Magento 2 & Adobe Commerce UPI Gateway Module: High-Volume Setup

Large Indian retail enterprises, electronics distributors, FMCG brands, and fashion conglomerates frequently run their digital storefronts on Magento 2 (Adobe Commerce). With support for complex multi-store catalogs, custom B2B pricing tiers, and ERP integrations (SAP, Oracle, NetSuite), Magento is built for enterprise scale.

However, at enterprise scale, standard payment aggregator pricing becomes unsustainable. When an Adobe Commerce store processes ₹2 Crores to ₹10 Crores monthly, paying a 2% gateway commission siphons tens of lakhs of rupees straight out of corporate net profits.

Here is the architectural guide for implementing an enterprise direct-to-bank UPI payment module in Magento 2 capable of handling thousands of concurrent transactions with zero percentage commissions.

---

The Enterprise Scale Challenge in Magento 2

In high-volume Adobe Commerce deployments, checkout operations face two core constraints:

1. Database Lock Contention: During high-traffic flash sales (such as Diwali sales), hundreds of simultaneous webhook updates can cause database deadlocks on the sales_order and sales_order_grid tables.
2. Third-Party Rate Limits: Centralized payment aggregators often rate-limit merchant API calls during high-concurrency spikes, causing checkout timeouts for customers.

Deploying a self-hosted or direct-to-bank gateway like VyaparGateway eliminates third-party gateway bottlenecks and allows orders to settle directly into corporate accounts.

---

The Financial Drain of 2% Fees at Enterprise Scale

Enterprise Adobe Commerce Financial Impact:
┌─────────────────────────────────────────────────────────────┐
│ Monthly Gross Merchandise Value:      ₹ 5,00,00,000 (5 Cr)  │
│ Standard Payment Gateway Cut (2%):    ₹   10,00,000         │
│ 18% GST on Gateway Cut:               ₹    1,80,000         │
│ Total Monthly Payment Fee Deduction:  ₹   11,80,000         │
├─────────────────────────────────────────────────────────────┤
│ Annual Revenue Lost to Intermediaries:₹ 1,41,60,000 (1.4 Cr)│
│ Settlement Delay:                     48 Hours (T+2 Days)   │
└─────────────────────────────────────────────────────────────┘

Surrendering ₹1.41 Crores every year on domestic UPI transactions represents an unacceptable operational cost for CFOs. By contrast, running an enterprise direct UPI pipeline with VyaparGateway costs a predictable flat monthly software fee.

---

Module Architecture: RabbitMQ & Asynchronous Ingestion

To prevent database bottlenecking during sales events, decouple the bank’s incoming webhook from Magento’s internal order state machine using RabbitMQ:

[Bank / NPCI Core]
         │ (Push Webhook: UTR 609415892014, Amount ₹4,500)
         ▼
[VyaparGateway Engine] ──(Sub-50ms HMAC Verification)
         │
         ▼
[Magento 2 Webhook Controller] ──► Pushes Message to RabbitMQ: `vyapar.payment.confirmed`
                                              │
                                              ▼
                             [Consumer Worker (Async Background)]
                                              ├── Load Order via Repository
                                              ├── Register Invoice & Capture
                                              ├── Append Bank UTR to History
                                              └── Trigger ERP / SAP Sync

---

Magento 2 Custom Payment Adapter Code (PHP)

Here is the implementation of the asynchronous webhook consumer in Magento 2:

<?php
namespace Vyapar\DirectUPI\Model\Consumer;

use Magento\Sales\Api\OrderRepositoryInterface;
use Magento\Sales\Model\Order\Invoice;
use Magento\Sales\Model\Service\InvoiceService;
use Magento\Framework\DB\Transaction;
use Psr\Log\LoggerInterface;

class PaymentConfirmedConsumer
{
    protected $orderRepository;
    protected $invoiceService;
    protected $transaction;
    protected $logger;

    public function __construct(
        OrderRepositoryInterface $orderRepository,
        InvoiceService $invoiceService,
        Transaction $transaction,
        LoggerInterface $logger
    ) {
        $this->orderRepository = $orderRepository;
        $this->invoiceService = $invoiceService;
        $this->transaction = $transaction;
        $this->logger = $logger;
    }

    public function process($message)
    {
        $payload = json_decode($message, true);
        $orderId = $payload['order_id'];
        $utr = $payload['utr'];

        try {
            $order = $this->orderRepository->get($orderId);

            if ($order->canInvoice()) {
                $invoice = $this->invoiceService->prepareInvoice($order);
                $invoice->setRequestedCaptureCase(Invoice::CAPTURE_ONLINE);
                $invoice->setTransactionId($utr);
                $invoice->register();

                $transactionSave = $this->transaction->addObject($invoice)->addObject($invoice->getOrder());
                $transactionSave->save();

                $order->addCommentToStatusHistory(
                    "Direct UPI Payment Confirmed via VyaparGateway. Bank Reference (UTR): {$utr}",
                    \Magento\Sales\Model\Order::STATE_PROCESSING
                );
                $this->orderRepository->save($order);
                
                $this->logger->info("Order #{$orderId} successfully invoiced with UTR: {$utr}");
            }
        } catch (\Exception $e) {
            $this->logger->critical("Asynchronous Payment Ingestion Error: " . $e->getMessage());
            throw $e; // Re-queue message for retry
        }
    }
}

---

Tuning for High-Concurrency Festive Sales

To prepare your Magento 2 payment infrastructure for large flash sales:

1. Configure Read-Write Database Splitting: Point all checkout order creation queries to your primary PostgreSQL/MySQL master, while routing webhook lookups to read replicas.
2. Enable Redis Caching for Product Blocks: Ensure payment intent generation queries never trigger cold database catalog re-renders.
3. Deploy Non-Custodial Infrastructure: By removing intermediary payment aggregators, your store communicates directly with banking switches via VyaparGateway, ensuring zero third-party downtime, instant bank settlement, and complete margin preservation.