Beneficiary Registration Framework

Beneficiary Management lets you define and manage the recipients of your payouts. PayU supports two approaches: Manual (API-based) Registration, where you explicitly register beneficiaries before initiating a payout, and Auto Beneficiary Registration, where PayU registers the beneficiary automatically inline during payout processing when supported and enabled.

This section descrobes what a beneficiary is, how beneficiary registration works, and the difference between manual and auto beneficiary registration. For enablement or configuration changes, contact your Key Account Manager (KAM).

Payouts require a defined recipient (a beneficiary). You can manage beneficiaries in two ways:

• Manually through APIs before payout, or
• Automatically inline during payout, when supported and enabled.

📘

Enable Auto Beneficiary Registration: To enable Auto beneficiary registration, contact you PayU Key Account Manager.

Auto beneficiary registration applies only when both of the following are true:

• The merchant is enabled for the feature.
• The bank and payout method support auto registration.

What is a beneficiary?

A beneficiary is the recipient of a payout. Beneficiaries are typically identified by:

• Bank account — account number + IFSC, or
• UPI ID — VPA (Virtual Payment Address)

Before processing a payout, the beneficiary typically needs to be registered with the bank or payout system.

What is Auto Beneficiary Registration?

Auto Beneficiary Registration allows PayU to automatically create a beneficiary during payout processing if it does not already exist:

1. You initiate a payout with beneficiary details.
2. If the beneficiary is not registered, the system creates it.
3. The payout proceeds without a separate registration step.

Why this matters

Manual Registration Flow

flowchart TD
    A(Merchant collects beneficiary<br/>details Account+IFSC or VPA) --> B(Merchant calls Create/Register<br/>Beneficiary API)
    B --> C(PayU registers beneficiary<br/>with bank / payout rail)
    C --> D(Merchant initiates payout<br/>using beneficiary reference)
    D --> E(PayU executes the payout)

    classDef start fill:#00ffde,stroke:#00ffde,stroke-width:2px,color:#002124,font-weight:bold
    classDef process fill:#002124,stroke:#00ffde,stroke-width:1.5px,color:#ffffff
    classDef success fill:#00ffde,stroke:#00ffde,stroke-width:2px,color:#002124,font-weight:bold

    class A start
    class B,C,D process
    class E success

    linkStyle default stroke:#00ffde,stroke-width:1.5px,color:#00ffde

Manual Registration Limitations

• Higher integration complexity.
• Additional API calls.
• Requires storage and state management.

Auto Beneficiary Registration

When enabled (and supported), PayU automatically registers the beneficiary during payout processing if required.

Auto Beneficiary Registration Flow

flowchart TD
    A(Merchant initiates payout<br/>with complete beneficiary details) --> B{Beneficiary<br/>already registered?}
    B -->|Yes| D(PayU executes the payout)
    B -->|No| C{Auto registration<br/>supported & enabled?}
    C -->|Yes| E(PayU auto-creates beneficiary<br/>inline)
    E --> D
    C -->|No| F(Payout requires manual<br/>beneficiary registration)

    classDef start fill:#00ffde,stroke:#00ffde,stroke-width:2px,color:#002124,font-weight:bold
    classDef process fill:#002124,stroke:#00ffde,stroke-width:1.5px,color:#ffffff
    classDef decision fill:#0a3a3d,stroke:#00ffde,stroke-width:1.5px,color:#ffffff
    classDef terminal fill:#4d174d,stroke:#00ffde,stroke-width:1.5px,color:#ffffff
    classDef success fill:#00ffde,stroke:#00ffde,stroke-width:2px,color:#002124,font-weight:bold

    class A start
    class E process
    class B,C decision
    class F terminal
    class D success

    linkStyle default stroke:#00ffde,stroke-width:1.5px,color:#00ffde

Key characteristics — Auto Registration

• No mandatory pre-registration step.
• Beneficiary creation handled inline.
• System manages missing-beneficiary scenarios.

Benefits — Auto Registration

• Reduced API overhead.
• Faster payout initiation.
• Lower risk of failure due to unregistered beneficiaries.
• Simplified integration flow.

Manual vs Auto Registration

📘

Note: If these conditions are not met, payouts may require manual beneficiary registration. In some cases, no beneficiary registration is required at all — your KAM can confirm what applies to your account.