Flow Release Notes | Version 3.9.4

UPI Transaction Status API Enhancements

Deployment Date: October 22, 2026

We have enhanced the UPI GTS Basic API, GTS Advance API, and Transaction Status Callback to include the following additional fields:

payee_vpa – Merchant/payee VPA
collection_type – Type of collection (e.g., dynamic_qr, payment_link, collect_request)
split_settlement_rule_urn – Split settlement rule identifier

These fields will improve transaction reconciliation and reporting. Existing integrations remain backward compatible, and no changes are required from clients. However, need to consume new parameters added in the below APIs.

GTS Basic API - Updated Response

{  
  "decentro_txn_id": "7E261A79F04F4F07A9E1E8B979383D63",  
  "api_status": "SUCCESS",  
  "message": "Transaction status retrieved successfully",  
  "data": {  
    "reference_id": "103e2cc8-3529-4cd0-8b80-a3025581fcff",  
    "request_decentro_txn_id": "17B6A19D83AC4AB1928763DF09EB0EC7",  
    "transaction_status": "SUCCESS",  
    "transaction_status_description": "Payment Request is successful",  
    "bank_reference_number": "106395475124",  
    "npci_txn_id": "HDF80811885511646c998b66747db4885b6",  
    "transaction_authentication_timestamp": "2025-06-13 13:19:29",  
    "purpose_message": "Test Transaction",  
    "payee_vpa": "merchant.decfin@bank",  
    "collection_type": "dynamic_qr",  
    "split_settlement_rule_urn": "SS_123456789"  
  },  
  "response_key": "success_transaction_status_fetched"  
}

Doc - here

GTS Advance API - Updated Response

{  
  "payee_vpa": "merchant.decfin@bank",  
  "collection_type": "dynamic_qr",  
  "split_settlement_rule_urn": "SS_123456789"  
}

Doc - here

Transaction Status Callback - Updated Payload

{  
  "callback_attempt": 1,  
  "callback_txn_id": "8383948897EE4BB9ADF2899935812FBB",  
  "consumer_urn": "34AFC29BE7914D9A926FC856FD0B7E21",  
  "callback_timestamp": "2025-04-11T16:51:04.779879",  
  "original_callback_txn_id": "36A693A1DDC14A5399D2746C125A288F",  
  "transaction_status": "SUCCESS",  
  "transaction_status_description": "Payment Request is successful",  
  "amount": 10.2,  
  "decentro_txn_id": "8B1C03BE47CF48ACA8280019136EB018",  
  "reference_id": "robo-0063c9fe-9461-460f-8402-db5004",  
  "bank_reference_number": "A483C37DA1AC497FA8882773D5573386_169",  
  "npci_txn_id": "A483C37DA1AC497FA8882773D5573386_169",  
  "purpose_message": "Testing",  
  "collection_type": "dynamic_qr",  
  "payee_name": "Merchant Name",  
  "payer_name": "Customer",  
  "payee_account_number": "",  
  "payer_vpa": "customer@bank",  
  "payee_vpa": "merchant.decfin@bank",  
  "split_settlement_rule_urn": "SS_123456789",  
  "transaction_attempt_status": "SUCCESS",  
  "attempt_decentro_txn_id": "D7482B6121E34A8B871557B204BADCDF",  
  "transaction_authentication_timestamp": "2024-08-18T13:10:00.000000",  
  "paid_amount": 10.2,  
  "transaction_attempt_status_description": "Successful Payment Attempt"  
}

Doc - here

Note: split_settlement_rule_urn will be populated for transactions associated with Split Settlement. For other transactions, it will be returned as empty, as per the existing API response contract.