Panapay

Panapay Payment Gateway Overview for Merchants

Panapay is a payment gateway built for Indian merchants that want to accept UPI and NetBanking payments and also initiate withdrawals to customer bank accounts. The platform focuses on INR-only processing, supports both hosted checkout and host-to-host (H2H) flows, and provides a REST API designed to be integrated into web and app experiences. Panapay also positions its service around fast processing and operational availability, with published performance and uptime figures and 24/7 support.

What Is Panapay?

Panapay provides payment acceptance and payout capabilities centered on India’s account-to-account rails:

• Deposits via UPI and NetBanking
• Withdrawals (payouts) to bank accounts using bank details (account number, IFSC, and bank name)
• REST API integration with IP whitelisting and API key authentication
• Hosted and H2H payment experiences to match different checkout needs

Panapay also reports scale and reliability metrics, including active merchant count, monthly processed volume, and uptime.

Panapay Payment Methods And Coverage

Panapay’s acceptance stack is built around UPI and NetBanking:

UPI Ecosystem Support

UPI coverage includes major UPI applications (explicitly naming Google Pay, PhonePe, Paytm, BHIM) and a broader set of banking UPI apps.

NetBanking Coverage

NetBanking integration is positioned as support for dozens of banks, including major institutions such as SBI, HDFC, ICICI, and Axis.

Currency Support

Panapay’s API documentation specifies INR as the only supported currency for transactions.

Transaction Flows: Deposits And Withdrawals

Panapay separates flows into deposit (collect) and withdrawal (payout):

Deposit Lifecycle

Deposit transactions support multiple statuses, including:

• pending: payment link generated, but the user has not paid or has not provided a reference (RRN/UTR)
• processing: payment submitted and pending approval
• approved: final success status
• rejected: failure (for example, incorrect RRN/UTR or settlement failure)
• abandoned: user did not initiate payment within 24 hours

A key operational element for some flows is UTR/RRN submission after an external payment is collected, enabling validation and finalization of status.

Withdrawal Lifecycle

Withdrawals are initiated with bank details and return processing initially. Withdrawal statuses include:

• processing
• approved (final)
• rejected

Checkout Options: Hosted Payment Page Vs Host-to-Host

Panapay supports two primary checkout patterns for deposits:

Hosted Payment (Redirect)

• The merchant initializes a transaction and receives a payment link.
• The customer is redirected to a Panapay-hosted payment page to complete payment.
• The request can include both a callback URL (status updates) and a redirect URL (post-payment return).

Host-to-Host (H2H)

• The merchant sets an H2H flag and receives payment details directly.
• For UPI, the response can include: a base64-encoded QR code, a generic UPI redirect link, app-specific redirect links (explicitly including Paytm, PhonePe, and Google Pay links in the response example).
• For NetBanking, the response includes bank payment details.
• Panapay indicates that H2H payment details are time-limited (10 minutes).

Withdrawals do not use the H2H checkout model in the same way and are processed through the standard flow.

API And Developer Experience

Panapay provides an API documentation, including a published base URL and core endpoints.

Security, Reliability, And Support

Panapay’s published operational and support signals include:

• IP whitelisting as a baseline security control for API access
• Stated uptime and 24/7 support availability
• Reported processing performance indicators (transaction speed, success rate, and daily capacity)

Support channels include support email addresses for merchant contact.

Analytics And Reporting

Panapay states that it provides a dashboard with transaction analytics, including visibility into outcomes such as success rates and performance indicators. This positions the platform as not only an API layer, but also a merchant-facing reporting surface for monitoring payment operations.

Pricing And Commercial Terms

Panapay presents pricing as:

• Transparent (no hidden fees claim)
• Volume-based customization, with custom pricing aligned to business volume

Specific numeric fee schedules are not published in the content reviewed here, so merchants should expect pricing to be provided through a sales or onboarding motion.

Typical Merchant Fit

Panapay’s examples and positioning align with merchants that:

• Sell to customers in India and want to accept UPI and NetBanking
• Need fast checkout flows using redirect or QR-based experiences
• Want to operate at scale (high transaction volumes) with uptime and support expectations
• Require both collections and payouts as part of their business model (for example, platforms with withdrawals)

Conclusion

Panapay is an India-focused payment gateway for merchants that need UPI and NetBanking deposits and bank-account withdrawals in INR. It offers both hosted and host-to-host checkout patterns, an API-key plus IP-whitelisting security model, callback-driven status updates, and merchant reporting via a dashboard.