PayU Review

Regional Breakdown

India is the largest market by volume, though the 2026 Online Gaming Act ends the skill-gaming and fantasy deposit flows that drove that volume on the iGaming side. UPI still dominates Indian eCommerce, and PayU's PA license plus direct UPI integration matters at the rail layer for permitted and non-gambling categories. Poland is the strongest CEE market for iGaming. PayU is one of the top three checkout methods in Polish eCommerce, BLIK runs through PayU as a native participant, and the consumer brand is recognized at checkout. Romania, Czech and Hungary are smaller but real. Turkey runs through PayU's local entity with TRY card acquiring. Southeast Asia is mostly card-funded with some wallet support (Paytm and PhonePe equivalents exist as separate integrations market-by-market). For LATAM-focused operators, EBANX, dLocal or AstroPay are the correct conversation. For Africa, PayU's exit was complete. Look at Flutterwave or Paystack instead.

Verticals

PayU explicitly markets to eCommerce, marketplaces, hospitality, ride-hailing, education, SaaS and SMB, in roughly that order of public visibility. Gaming is mentioned only as one example use case for PayU Payouts ('disburse winnings to gaming platforms') without a dedicated industry page or any named iGaming client. Indian skill-gaming and fantasy operators (Dream11, MPL, Games24x7) drove Indian iGaming deposit volume until the 2026 Online Gaming Act banned real-money play and they shut down or pivoted to free-to-play in late 2025; none were publicly named as PayU clients in any case. For Polish lottery and licensed sports betting, PayU is widely accepted but not publicly attributed to specific operators. Compare with AstroPay (500+ iGaming clients disclosed, Betano and Novibet named, Premier League shirt sponsorships) or PayRetailers (SoftSwiss connector built specifically for gambling). PayU serves iGaming as one of many verticals, not as a specialism.

• eCommerce
• SaaS
• marketplaces
• hospitality
• ride-hailing
• education
• gaming (India)
• lottery/state operators

Deposits are instant on UPI, cards, wallets and BLIK. India settlement is T+2 by default: money clears to merchant accounts two business days after transaction. PayU Priority Settlements compresses this to 15 minutes for an additional fee, supports all payment modes, and works 24/7. CEE settlement follows local norms, T+1 to T+3 depending on method. Refunds debit from next settlement and complete in 5-7 business days to the customer's account. PayU Payouts is the disbursement product: bulk payouts via IMPS clear in minutes, NEFT in 30 minutes to 2 hours, UPI is near-instant, SEPA in CEE follows local clearing times. There's no published per-day or per-month mass payout limit, which gaming operators handling player withdrawal volume should confirm directly with PayU sales. Onboarding speed is split: PayU India advertises sub-10-minute self-serve sign-up and ~1 day average end-to-end onboarding, which is competitive against Razorpay and Cashfree for SMB. Enterprise KYB realistically takes 2-4 weeks per Capterra and G2 reviewers, with some reporting 35+ days stuck in document approval, typical for the segment but not faster than competitors. PayU EMEA onboarding is slower (2-6 weeks) due to KNF and local regulator requirements. For iGaming-specific onboarding expect at least the upper end of those ranges plus extra time for risk-profile assessment, since PayU doesn't have a gambling-vertical fast-track. Updated May 2026.

Integration Assessment

Four integration paths: Direct API (server-to-server REST), Hosted Checkout (redirect-based, lowest dev effort), Drop-In / Web SDK (embedded checkout for white-label flows), and Payment Links (one-off invoice flows). REST API documented at docs.payu.in for India and developers.payu.com/europe for CEE, two separate portals that share concepts but not endpoints, which is the main integration friction for operators serving both markets through PayU. Mobile SDKs on iOS, Android, React Native, Flutter and Cordova, one of the broadest mobile-SDK lists in the segment. Android distributed via JFrog (payu.jfrog.io), iOS on GitHub. Postman collection published. Sandbox available with test cards. Pre-built plugins for WooCommerce, Magento, Shopify, OpenCart, PrestaShop and Wix, heavy on eCommerce platforms, none of the iGaming-specific connectors (no SoftSwiss, no EveryMatrix, no Slotegrator). npm packages payu-websdk (PayU India web SDK) and payu-sdk both exist but with modest download counts (combined ~1k weekly), suggesting most integrations call the REST endpoints or use the platform plugins directly.

Compliance Context

PCI DSS Level 1, the highest tier, audited annually. Network tokenization plus vault tokenization (India follows RBI card-on-file tokenization rules from 2022). 3DS 2 with dynamic version routing via the Decision Engine to minimize friction while maintaining SCA compliance. AI-driven anti-fraud machine that scores transactions in real time using velocity rules, device fingerprinting and historical fraud patterns. Smart Routing Engine doubles as a fraud optimization layer by routing through the acquirer most likely to approve based on past patterns. Regulatory stack: RBI Payment Aggregator license for India (mandatory since the 2020 PA/PG framework), NBFC license via PayU Finance for LazyPay credit, KNF authorization for PayU S.A. in Poland, regulated payment-institution status across the CEE entities, and Turkey's BDDK framework for PayU Bilgi Teknolojileri. KYC for merchant onboarding integrates with DigiLocker, CKYC and Aadhaar verification in India. Chargeback liability sits with the merchant by default, standard for the segment. 3DS 2 SCA shifts liability to the issuer when authentication is fully completed.

Review Analysis

Trustpilot shows 1.2/5 from ~45 reviews on payu.in, the primary Indian-market profile. Polish payu.pl sits even lower at 1.1/5 with similar review volume. PayUmoney consumer wallet profile is 1.3/5. The reviews are almost entirely end-consumer complaints about merchants where PayU appeared on the cardholder statement, plus a smaller cluster of merchants reporting onboarding rejections and document approval delays. This is the same pattern that hits Adyen (1.3/5, 418 reviews), Paysafe (1.3/5, 1,132 reviews) and BitPay (1.2/5, 289 reviews), high-volume payment processors with consumer-facing brand recognition get systematically negative Trustpilot ratings because the people who write reviews are angry consumers, not satisfied B2B merchants. The signal value is low. G2 is more useful: 3.1/5 from 25 verified B2B reviews. Distribution: 36% 5-star, 20% 4-star, 16% 3-star, 4% 2-star, 24% 1-star, a polarized split. Positives focus on integration ease, smart routing performance and security. Negatives focus on opaque onboarding (rejections after weeks of documentation), high effective fees once add-ons are counted, and slow customer support response. Capterra is more positive at 4.0/5 from 49 reviews (Ease of Use 4.2, Customer Service 3.6, Features 4.0, Value for Money 3.8), but Capterra reviews skew toward smaller merchants who use the self-serve tier where PayU is competitive. Glassdoor sits at 3.6/5 from 1,013 reviews. 59% would recommend, 57% positive business outlook, compensation rated 3.3/5 and declining ~2% YoY. Bangalore office matches the global rating. Recurring employee themes: heavy growth pressure, ambiguous middle management, learning opportunities praised. No GitHub-based developer-experience review aggregation exists for PayU specifically.

Context for Operators

For a payment processor of PayU's scale, the public review distribution is largely uninformative. The 45 Trustpilot reviews on payu.in are noise against 10+ million daily transactions. That's roughly one Trustpilot review per 80 million transactions, which makes the rating statistically meaningless. The G2 score is more informative because it's 25 actual merchant reviews, but a sample of 25 against 450,000+ merchants is still a thin signal. The diligence inputs that matter for an iGaming operator are: the RBI PA license (verifiable on RBI's website), the KNF authorization (verifiable on KNF's register), the PCI DSS Level 1 certification (annual audit, request the AOC), and the absence of named iGaming clients in the public record (which is itself a signal). Push PayU sales for named gambling references during the procurement conversation. If none are forthcoming, weight that against integrating.

Notable Clients

Public client list skews hard toward Indian and CEE consumer brands. India: Amazon India, Flipkart, Jio, BookMyShow, Swiggy, Zomato, Ola, MakeMyTrip and most of the major Indian eCommerce and OTA players have had PayU integrations at some point. CEE: PayU Poland is integrated into the top Polish eCommerce platforms (Allegro, Empik, MediaMarkt-equivalents). 450,000+ active merchants globally per PayU's own reporting, 10+ million daily transactions. No publicly attributed iGaming clients in either region despite obvious volume from Indian skill-gaming operators and Polish licensed sports betting. For an iGaming operator doing diligence, request named gambling references from PayU's sales team specifically. The absence of public disclosure isn't proof of absence of relationship, but neither is it evidence of one.