added

Flow Release Notes | Version 3.8.0

This release notes contains updates related to UPI Autopay & eNach.

UPI Autopay

Feature: Addition of error_key & presentation failure reasons in Get Presentation Status API & Presentation Callback

Release Date: 30-10-2025

  • The GPS Presentation Status API and Callback now include additional failure insights for better merchant visibility.
  • Introduced new field error_key → represents the failure bucket (e.g. error_at_remitter_bank, error_at_beneficiary_bank).
  • Enhanced presentation_status_description → provides a user-friendly reason derived from internal error-code mapping.
  • error_key will appear only for FAILED presentations.
  • For SUCCESS presentations, error_key is null in callback and omitted in GPS API response.
  • Changes applicable to both GPS API and presentation callback payloads.
{
  "presentation_status": "FAILED",
  "presentation_status_description": "Mandate presentation is failed",   //new
  "notification_sequence_id": "DFN-BA1DE0A3DB5342D281F19068BC56901B-00001",
  "remaining_representation_attempts": 3,
  "presentation_auth_timestamp": "2025-09-17 18:19:16.441098",
  "decentro_txn_id": "2308D9589EXXXXXEA4F635D2407C0",
  "callback_attempt": 4,
  "callback_txn_id": "21661E39XXXX98C5970A352FF656",
  "consumer_urn": "9F6C6EDBA758XXXXA8DC1EA4677F3",
  "callback_timestamp": "2025-09-17 18:20:49.230421",
  "original_callback_txn_id": "64846F3XXXXX8978265200E00E0171D",
  "reference_id": "cc4a6bf9-078XXXX-97aa-e0b33e80ecda",
  "bank_reference_number": "526018789018",
  "npci_txn_id": "YES634390feecXXXXXb265f7d7c01305",
      "error_key": "error_at_beneficiary_bank",             //new 
  "payer_vpa": "XXXXX@ybl",
  "decentro_mandate_id": "BA1DE0A3DB5342D281F19068BC56901B",
  "amount": "9.0000",
  "amount_rule": "MAX",
  "payer_name": "7304535723@ybl",
  "payee_name": "XXXXXXXXXXXXXXXXXX",
  "mandate_name": "XXXXXX",
  "frequency": "ASPRESENTED",
  "start_date": "2025-09-17",
  "end_date": "2028-10-01",
  "presentation_summary": {
    "total": 1,
    "success": 0,
    "failed": 0,
    "skipped": 0,
    "remaining": 1
  },
  "block_fund": false,
  "is_revocable": true,
  "last_action": "CREATE",
  "last_action_timestamp": "2025-09-17 18:18:01.374325"
}
{
  "decentro_txn_id": "B5621499184E4B00A8A4D862A0ACEBDE",
  "api_status": "SUCCESS",
  "message": "Presentation status retrieved successfully",
  "data": {
    "presentation_detail": {
      "status": "FAILED",
      "status_description": "Mandate presentation failed",  //new
      "error_key": "error_at_beneficiary_bank",             //new
      "bank_reference_number": "483605340610",
      "npci_txn_id": "MYB3C9815461FXXXXBFE2861FDEDC786",
      "transaction_authentication_timestamp": "Jan 15, 2025 03:02:39 PM"
    }
  },
  "response_key": "success_presentation_status_fetched"
}


Feature: Added CTAs for Autopay Mandate Registration, Presentation & Pre-Debit Notification in Merchant Dashboard

Release Date: 30-10-2025

  • Introduced dedicated CTAs in merchant dashboard to enable full lifecycle management of autopay mandates.
  • Merchants can now register the mandates, trigger the pre-debit notification & present the mandates via our dashboard.

Feature: Support for Autopay MIS Report Download in Merchant Dashboard

Release Date: 30-10-2025

  • Added MIS Report download functionality on merchant dashboard for Registrations, Presentations, and Pre-Debit Notifications.
  • Enables merchants to perform independent reconciliation and audit without relying on callbacks.
  • Available for both historical and recent transactions.

eNACH

Feature: Introduced UIStreams Mandate Registrations in Merchant Dashboard

Release Date: 30-10-2025

  • Added a new mandatory dropdown in the “Generate NACH Mandate” CTA on the merchant dashboard to choose how the mandate link should be generated.
    • Available options:
      • UIStreams with user block
      • UIStreams without user block
      • NPCI Direct Link
  • The mandate creation form will now render only after the user selects a method.
  • All other flows, validations, and link generation behaviour remain unchanged.
  • Generated links continue to appear in the existing data table for tracking and download.