Refer merchants using APIs

This documentation provides comprehensive guidance for integrating with PayU's Partner Integration API. This API enables businesses and individual partners to integrate PayU's payment solutions into their platforms, onboard merchants, and manage the complete merchant lifecycle.

Overview

PayU merchant onboarding APIs allows partners to:

• Onboard merchants to the PayU platform
• Manage merchant KYC processes
• Verify bank account details
• Handle electronic signatures for agreements
• Receive real-time status updates via webhooks

Authentication and Authorization

PayU Merchant Onboarding employs token-based authentication with OAuth 2.0 standards. Partners must obtain tokens through appropriate authentication endpoints before accessing the API resources.

Token Management Flow

The token-based authentication works as follows:

• Partners obtain an access token using their credentials
• This token is included in subsequent API requests
• Tokens expire after a set period and must be refreshed

Important: Access tokens should be securely stored and never exposed in client-side code.

Merchant Onboarding Process

The Partner Onboarding flow follows a 16-step sequence. Each step depends on the previous one. Call GetToken (Step 00) first, then proceed through merchant creation, verification, KYC, and e-sign.

Use GetMerchant (Utilities) between steps to check verification and onboarding status.

List of APIs

The APIs used in the onboarding flow are listed below. These map to the Partner APIs reference section:

KYC Document Management

The KYC process requires merchants to provide various identification and business documents. These APIs facilitate document upload and verification.

Document Requirements

Different merchant types require different documentation. The exact requirements should be determined by referencing the official PayU documentation.

Document Types and Guidelines

PayU accepts various document types for KYC verification, including:

• Identity proofs (PAN Card, Aadhaar, etc.)
• Address proofs
• Business registration documents
• Bank account proofs

For an exhaustive list of documents required for an entity, please refer to KYC Checklist.

For an the business category & subcategory details, please refer to Partner Category List.

E-Sign Flow

The electronic signature process is required to complete merchant agreements. PayU provides specific APIs to manage this workflow.

For e-signature specifications, please refer to:

Webhooks for Real-Time Updates

Webhooks allow partners to receive notifications about changes in merchant status without polling the API.

For webhook integration details, please refer to:

• Register Webhooks API
• Get Real-Time Merchant Status Using Webhooks

Security Considerations for Webhooks

Webhook requests should be authenticated to ensure they come from PayU. Implementation details can be found in the webhook documentation.

Error Handling and Troubleshooting

Common KYC Errors and Solutions

KYC document verification can encounter various issues. For detailed information on common errors and their solutions, please refer to:

Common issues include:

• Document quality problems
• Information mismatches
• Missing required fields
• Format incompatibility

Flow Diagram

Here is a diagram for the high-level integration flow:

Security Best Practices

When integrating with PayU's APIs, follow these security best practices:

• Implement proper token management
• Use HTTPS for all communications
• Validate webhook signatures
• Securely store sensitive data
• Implement proper error handling

Testing Recommendations

Testing is essential before moving to production. PayU provides a sandbox environment for testing purposes. Test key aspects including:

• Authentication flows
• Merchant creation and updates
• Document uploads
• Bank verification
• Error handling
• Webhook processing