Partner Payments

Partner Payments API enables partners and resellers to integrate PayU's payment acceptance capabilities on behalf of their merchants. This API supports multiple payment flows including UPI Intent S2S, UPI TPV (Third-Party Validation), and standard redirect checkout flows.

How it works?

Partner Payments uses a three-step OAuth authentication flow followed by payment initiation via RESTful APIs. Here's the complete flow:

1. Authentication Flow — Partners get the access token through a two-step process:

   1. Receiving the auth_code on the redirect URI

   2. Validate this auth_code using the Validate Auth Code and Client API.

      You will receive an accesss_token.

   3. Use the access token in the Payment Initiation step.

2. Payment Initiation — Partners use the final access token to call the /partner/payments endpoint with:

   • Transaction details (amount, product info, customer details)
   • Partner identifiers (merchant_id, reseller_id)
   • Payment-specific parameters (UPI S2S flags, TPV beneficiary details, redirect URLs)
   • SHA-512 hash computed using the partner-specific formula with client_secret

3. Response Handling — PayU returns different response formats based on payment type:

   • UPI Intent S2S: Returns intentURIData and acsTemplate for rendering UPI intent
   • Redirect Flow: Returns redirectUri to redirect customer to PayU hosted checkout
   • UPI TPV: Returns intent data with validated beneficiary account

4. Webhook Delivery — After payment completion, PayU:

   • Sends callback to configured partner webhook URLs
   • Delivers comprehensive payload including transaction status, payment ID, and custom UDF fields
   • Includes SHA-512 hash for webhook verification using reverse hash formula

5. Payment Verification — Partners verify final payment status by:

   • Calling /partner/verifyPayment API with transaction ID
   • Validating response hash for authenticity
   • Reconciling payment status with webhook data

Customer Journey

The following diagram illustrates the end-to-end payment journey when partners integrate via WhatsApp or other channels:

%%{init: {
  "theme": "base",
  "sequence": {
    "mirrorActors": false,
    "rightAngles": true,
    "messageAlign": "left",
    "fontSize": 10,
    "actorFontSize": 10,
    "noteFontSize": 10,
    "actorMargin": 88,
    "width": 168,
    "boxMargin": 10,
    "messageMargin": 38,
    "diagramMarginX": 60,
    "diagramMarginY": 18
  },
  "themeVariables": {
    "fontFamily": "Arial, Helvetica, sans-serif",
    "fontSize": "10px",
    "background": "#FFFFFF",
    "primaryColor": "#A6C307",
    "primaryTextColor": "#002843",
    "primaryBorderColor": "#002843",
    "secondaryColor": "#F4F9E0",
    "lineColor": "#002843",
    "textColor": "#002843",
    "actorBkg": "#A6C307",
    "actorBorder": "#002843",
    "actorTextColor": "#002843",
    "actorLineColor": "#002843",
    "signalColor": "#002843",
    "signalTextColor": "#002843",
    "labelBoxBkgColor": "#F4F9E0",
    "labelBoxBorderColor": "#A6C307",
    "noteBkgColor": "#F4F9E0",
    "noteTextColor": "#002843",
    "noteBorderColor": "#A6C307",
    "activationBkgColor": "#E8F0C4",
    "activationBorderColor": "#002843"
  }
}}%%
sequenceDiagram
    box Partner Channel (WhatsApp)
        participant Cust as Customer
        participant WA as WhatsApp
    end
    box Partner Backend
        participant Partner as Partner Backend
    end
    box PayU
        participant PayU as PayU
    end
    box UPI App
        participant UPI as UPI App
    end

    Note over Cust,WA: 1. Customer initiates payment in WhatsApp

    WA->>Partner: 2. Send payment request (order ref, amount)
    Partner->>PayU: 3. OAuth token request
    PayU-->>Partner: 4. OAuth access_token

    Partner->>PayU: 5. POST /partner/payments (create UPI intent)
    PayU-->>Partner: 6. Return UPI intent (deeplink/QR, payment_id)

    Partner-->>WA: 7. Send Pay link to chat
    WA-->>Cust: 8. Display Pay link/button
    Cust->>UPI: 9. Open UPI app via intent
    UPI->>UPI: 10. Authorize payment
    UPI-->>PayU: 11. Payment result (success/failure)

    PayU-->>Partner: 12. Webhook: payment.status
    Partner->>PayU: 13. Verify payment (GET /partner/payments/{payment_id})
    PayU-->>Partner: 14. Payment details (status, txn_id)

    Partner-->>WA: 15. Send confirmation message
    WA-->>Cust: 16. Notify payment status

Typical Flow:

1. Customer initiates payment request through partner's interface (WhatsApp, app, web)
2. Partner backend generates OAuth access token (if not cached)
3. Partner calls /partner/payments API with payment details and computed hash
4. For UPI Intent S2S:
   • PayU returns intentURIData and acsTemplate
   • Partner renders UPI intent link or QR code to customer
   • Customer selects UPI app and authorizes payment
5. PayU processes payment and sends webhook to partner's configured URL
6. Partner verifies webhook hash and calls /partner/verifyPayment for confirmation
7. Partner updates customer with payment status

Features of Partner Payments

✅ OAuth 2.0 Secure Authentication — Three-step token generation flow with scope-based access control ensuring secure API access

✅ Multiple Payment Flows — Support for UPI Intent S2S, UPI TPV, redirect checkout, payment links, and subscriptions

✅ UPI Intent S2S Integration — Receive intentURIData and acsTemplate for seamless UPI app invocation without redirect

✅ UPI TPV (Third-Party Validation) — Validate beneficiary account details during payment initiation for enhanced security and compliance

✅ Partner-Specific Hashing — Dedicated hash formulas using client_secret instead of merchant salt for improved security isolation

✅ Configurable Webhooks — Database-driven webhook configuration supporting partner-level and merchant-level URLs with fallback behavior

✅ Comprehensive Webhook Payload — Receive complete transaction data including status, payment ID, UDF fields, and verification hash

✅ Payment Verification API — Programmatic verification endpoint to confirm final transaction status independently of webhooks

✅ Flexible UDF Fields — Five user-defined fields (udf1-udf5) for passing custom partner and merchant metadata

✅ Database-Driven Configuration — Control webhook delivery, disable merchant fallbacks, and manage partner-merchant relationships via partner_webhook_urls and partner_merchant_params tables

Benefits of Partner Payments

🚀 Faster Merchant Onboarding — Integrate once as a partner and onboard multiple merchants without per-merchant integration effort

🔒 Enhanced Security — Separate OAuth scopes, partner-specific hash formulas, and reverse hash verification prevent unauthorized access

💰 Revenue Flexibility — Support for commission tracking via UDF fields and partner-level reporting

📊 Real-Time Status Updates — Webhook-driven architecture ensures instant payment status delivery to partner systems

🔧 Reduced Technical Complexity — Merchants don't need to integrate PayU directly; partner handles all API communication

📱 Omnichannel Support — Integrate payments into WhatsApp, mobile apps, web portals, or any partner channel

⚡ High Performance — Optimized S2S flows reduce redirect latency and improve conversion rates

🛡️ Compliance Ready — Built-in TPV support for regulatory compliance in specific use cases

Next Steps

To integrate Partner Payments, refer to:

• Hosted Checkout
  • Partner Payments Hosted Checkout Integration
• Custom Checkout
  • Partner Payments UPI Intent Integration
  • Partner Payments UPI TPV Integration