PayU is not a single API. It is a family of regional gateways — PayU India (PayUbiz/PayU Money), PayU LATAM (Colombia, Brazil, Mexico, Argentina, Peru), PayU CEE (Poland, Czech Republic, Romania) and PayU Africa — each with different endpoints, hashing schemes, settlement rules and supported methods. A generic Adobe Commerce Marketplace extension typically targets one of these and treats the rest as an afterthought. ECOSIRE builds this gateway to your PayU account, your region and your checkout flow.

We deliver it as a proper Magento 2 payment module under app/code/Ecosire/PayU, implemented against the Magento payment service contracts — a gateway command pool (Gateway\Command), request/response builders, a value handler pool and a validator, all wired through di.xml and payment.xml. It plugs into both the Luma checkout and the Hyvä/PWA front end, exposes REST and GraphQL mutations for headless storefronts, and registers webhook/IPN endpoints for asynchronous settlement confirmation.

Because PayU's hosted/redirect flow and server-to-server flows differ per region, we configure the exact integration mode you are approved for: hosted secure checkout (PCI SAQ-A), seamless iframe, or direct card capture where your PCI scope allows. UPI, net banking and wallet rails are wired for India; LATAM cash/installment and CEE local methods are added as method packs. Refunds, partial captures, EMI/installments and tokenized recurring are supported where your PayU contract enables them.

This is honest build-to-order work: you purchase the build, we collect your credentials and requirements, then engineer, install and support the extension. It is not an instant Marketplace download.