Flow Release Notes

This release notes contain changes related to UPI Autopay & UPI Collections V3.

UPI Collections V3

Features Name : Transaction Level Split Settlements, Purpose Message Propagation, Enhanced Failure Visibility
Deployment Date: April 27th, 2026

Transaction Level Split Settlements

New Parameter: Introduced an optional split_settlement_rule_urn in the Generate Payment Link,Generate Dynamic QR, and Issue Collect Request APIs.
Flexible Distribution: Enables automated fund splitting at the individual transaction level (via percentage or fixed amount) instead of relying solely on daily aggregate settlements.

Purpose Message Propagation

Enhanced GTS Responses: The purpose_message is now propagated across all status values in the GTS Basic (within the data block) and GTS Advance (within transaction_description) APIs.
Channel Coverage: Supported for Generate Payment Link,Generate Dynamic QR, Issue Collect Request and Refunds APIs and .

Enhanced UPI Failure Descriptions

Dashboard & MIS Integration: Added a new error_key_description field to the Dashboard View Transactions table and UPI MIS downloadable reports.
Human-Readable Errors: For failed transactions, the field displays a formatted string combining the error code and reason (e.g., Z9 - INSUFFICIENT FUNDS IN CUSTOMER ACCOUNT).

UPI Autopay

Feature: PDN API – Migration to Asynchronous Flow

Deployment Date - 24/04/2026

All PDN requests are now processed asynchronously by default.
Synchronous execution is completely removed.
is_async flag is now ignored in PDN API.
API will always return api_status = SUCCESS when the PDN request is successfully accepted & notification_status = PENDING .
Final PDN status will be available only via:
- Callback
- Status Check API
presentation_sequence_id which is used for presentations, is shared via callbacks.

PDN Doc - here
PDN Callback Doc- here
PDN Status Check Doc - here