PayU Gateway for Magento 2

主な機能

Native Magento 2 payment module under app/code/Ecosire/PayU built on the gateway service contracts (command pool, request/response builders, value handler pool, validators) and wired via di.xml + payment.xml

Region-aware integration targeting your specific PayU entity — PayU India (PayUbiz), PayU LATAM, PayU CEE or PayU Africa — with the correct endpoint, hash/signature scheme and settlement model

Cards, UPI, net banking and wallets for the India market, configured against your PayU merchant key and salt

Regional method packs for LATAM (cash vouchers, installments) and CEE (local bank methods) added per your PayU contract

Hosted secure redirect checkout (PCI SAQ-A) by default, with seamless iframe or server-to-server card capture available within your approved PCI scope

Webhook / IPN controller for asynchronous payment confirmation, with HMAC/hash signature verification and idempotent order state transitions

Online refunds (full and partial), authorize-and-capture and authorize-only flows mapped to Magento invoice and credit-memo actions

EMI / installment plan selection and tokenized recurring payments where your PayU agreement supports them (vault integration via Magento\Vault)

REST and GraphQL support so the gateway works in headless / PWA Studio and Hyvä storefronts, not just Luma

Admin configuration under Stores > Configuration > Sales > Payment Methods with ACL-protected fields, sandbox/production toggle and encrypted credential storage via core_config_data

Order status mapping, fraud/3-D Secure handling and a cron-backed reconciliation job to resolve pending transactions against PayU

Structured logging (var/log) and a verbose debug mode for gateway request/response tracing during go-live

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

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.

得られるもの

Installable Magento 2 module (Ecosire_PayU) delivered as composer package or app/code drop-in, compatible with Open Source and Adobe Commerce

Installation and configuration on your environment (staging first, then production) including setup:upgrade, di:compile and static-content:deploy

Configured PayU credentials, region, integration mode and enabled payment methods matched to your live PayU account

Webhook/IPN endpoint registered and verified end-to-end against PayU sandbox and production

Test transaction walkthrough covering authorize, capture, partial refund and webhook confirmation in your environment

Short technical handover document plus an agreed post-launch support and compatibility-update window

これは誰のためのものですか

Indian D2C merchant on Magento 2

Needs UPI, net banking, wallets and EMI through their existing PayUbiz account, with a checkout that converts on mobile and reconciles cleanly against settlement reports.

LATAM / CEE cross-border store operator

Sells into Colombia, Mexico, Brazil or Poland and needs PayU's local cash, installment and bank methods wired correctly to the right regional PayU entity — something generic extensions handle poorly.

Adobe Commerce solution architect / agency

Wants a maintainable module built on Magento's gateway service contracts and GraphQL, not a black-box plugin, so it survives upgrades and fits a headless or Hyvä storefront.

PayU Gateway for Magento 2 の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
Correctly targets your specific PayU region/entity (India / LATAM / CEE / Africa)	付属	部分的なサポート	部分的なサポート	含まれていない
India rails: UPI + net banking + wallets + EMI	付属	部分的なサポート	部分的なサポート	含まれていない
Built on Magento gateway service contracts (command pool, di.xml, payment.xml) — upgrade-safe	付属	部分的なサポート	部分的なサポート	含まれていない
REST + GraphQL for headless / PWA / Hyvä storefronts	付属	部分的なサポート	含まれていない	含まれていない
Webhook/IPN with signature verification and idempotent order transitions	付属	部分的なサポート	部分的なサポート	含まれていない
Online partial/full refunds, partial captures and tokenized recurring (vault)	付属	部分的なサポート	部分的なサポート	含まれていない
Installed, tested in sandbox+production and supported for you	付属	含まれていない	含まれていない	含まれていない

PayU Gateway for Magento 2 に関するよくある質問

How long until the PayU gateway is live on my store?

Typical delivery is 5–10 business days from when we receive your PayU credentials, target region and environment access. A single-region hosted-checkout build is at the short end; multi-region method packs, seamless iframe or server-to-server card capture, EMI and recurring add time. We install on staging first, verify against the PayU sandbox, then deploy to production.

What ongoing support and updates do I get after launch?

Every build includes an agreed post-launch support window for bug fixes and a compatibility-update commitment covering Magento 2 / Adobe Commerce minor releases and PayU API changes. Because we hold the source under app/code/Ecosire/PayU, we can patch signature-scheme or endpoint changes quickly. Extended maintenance retainers are available.

Is this the same as a PayU extension from the Adobe Commerce Marketplace?

No. This is build-to-order. There is no instant download — you purchase the build and we engineer, install and support a module tailored to your PayU entity, region, PCI scope and storefront (Luma, Hyvä or PWA/headless). Generic Marketplace extensions usually cover one PayU region and one flow; we configure exactly what your account supports.

Which PayU regions and payment methods are supported?

PayU India (cards, UPI, net banking, wallets, EMI), PayU LATAM (cards, cash vouchers, installments), PayU CEE (cards, local bank methods) and PayU Africa. The methods we enable are bounded by what your specific PayU merchant contract and approval allow — we wire the rails your account actually has.

Does it work with headless / PWA Studio and Hyvä, and does it need PCI compliance?

Yes. The module exposes REST and GraphQL so it works in PWA Studio and Hyvä storefronts as well as Luma. The default hosted/redirect flow keeps you at PCI SAQ-A (no card data touches your server). Seamless iframe or direct card capture is possible where your PCI scope permits — we build to your approved level.