Release Changelog
Get StartedExport API CollectionSupport
Back to All
added

Flow Release Notes | Version 3.6.3

April 3rd, 2025 by Akhil Halgeri

This release note covers updates related to UPI AutoPay, eNACH Mandate, and Virtual Account APIs.

UPI Autopay

Release Date: 03-Apr-2025

Feature: Collect Request & TPV Support in Create Mandate API

Summary: Merchants can now initiate collect request-based mandates with optional Third-Party Verification (TPV). This provides an alternative to intent links for better control over mandate registrations.

New API Flags:

  • is_collect_request – Mandatory parameter. Accepted values: true/false.
  • is_tpv – Conditional mandatory parameter. If is_collect_request = true, this parameter must be provided. Accepted values: true/false.

Behaviour Changes:

  • If is_collect_request = true, mandates are initiated via collect requests, and the following fields are mandatory:
    • payer_details.name
    • payer_details.virtual_address
  • If is_collect_request = false, mandates are initiated via intent links.
  • If is_tpv = true, the payer’s account number payer_details.account_no is required for validation along with payer_details.name & payer_details.virtual_address
  • If is_tpv = false, payer_details.account_no must be null.
  • The existing intent link flow remains unchanged for backward compatibility.

Feature: Introduction of redirect URL in Create Mandate API

Summary: Merchants can pass the redirection URL in the Create Mandate API & once we receive the terminal statues, user will be redirected to merchant provided URL.

New API Params:

  • redirect_url - This is a optional parameter. Merchants can pass the redirection URL. Max support of characters are 2048.
{
    "reference_id": "{{$randomUUID}}",
    "consumer_urn": "{{consumer_urn}}",
    "mandate_name": "TPV Testing",
    "amount": 1.00,
    "frequency": "daily",
    "purpose_message": "TPV Testing",
    "rule_type": "AFTER",
    "amount_rule": "MAX",
    "start_date": "2025-04-28",
    "end_date": "2025-04-29",
    "expiry_time": 10,
    "default_amount": 1,
    "is_managed_by_decentro": false,
    "is_qr_requested": true,
    "is_collect_request": false,
    "is_tpv": true,
    "payer_details": {
        "name": "abc",
        "virtual_address": "nihal@okhdfcbank",
        "account_no": "50100425803737"
    },
    "generate_psp_uri": false,
    "is_downpayment": true,
    "redirect_url": "https://www.google.com",
    "mandate_action_callback_subscriber_data": {
        "url": "https://webhook.site/XXXX",
        "method": "POST",
        "headers": {
            "content-type": "application/json"
        }
    }
}

Enach Mandate

Release Date: 03-Apr-2025

Feature: Introducing UIStreams for Mandate Registration

Summary: This release introduces UIStreams-based mandate registration, allowing merchants to choose between three different initiation flows.

Three different initiation flows supported:

  • UIStreams with user details – User selects authentication mode only on the Decentro screen.
{
    "reference_id": "{{$randomUUID}}",
    "consumer_urn": "XXXX",
    "user": {
        "name": "somefirst somelast",
        "account_number": "696410110006674",
        "reference_number": "decentro-mandate",
        "account_type": "SAVINGS",
        "bank_code": "HDFC",
        "email": "[email protected]",
        "mobile": "9999999999", 
        "pan": "ABCDE1234F"
    },
    "start_date": "2025-04-03",
    "end_date": "2030-07-30",
    "amount": 10000.00,
    "amount_rule": "fixed",
    "category_code": "elec",
    "frequency": "weekly",
    "redirection_url": "https://google.com",
    "uistream": true
}

  • UIStreams without user details – User enters their details on the Decentro screen.
{
    "reference_id": "{{$randomUUID}}",
    "consumer_urn": "XXXX",
    "start_date": "2025-04-03",
    "end_date": "2030-07-30",
    "amount": 10000.00,
    "amount_rule": "fixed",
    "category_code": "elec",
    "frequency": "weekly",
    "redirection_url": "https://google.com",
    "uistream": true
}

  • Direct Link – User is redirected directly to NPCI.
{
    "reference_id" : "{{$randomUUID}}",
    "consumer_urn": "{{consumer_urn}}",
    "user" : {
        "name" : "XXXX",
        "account_number" : "XXXX",
        "account_type" : "SAVINGS",
        "reference_number" : "decentro-mandate",
        "bank_code" :  "CNRB"
    },
    "start_date" : "2025-04-20",
    "end_date" : "2025-06-20",
    "amount" : 200.00,
    "amount_rule" : "fixed",
    "category_code" : "elec",
    "frequency" : "weekly",
    "redirection_url" : "https://www.google.com",
    "authentication_mode" : "DebitCard"
}

Feature: New Mandate Registration Callback Structure

Release Date: 03-Apr-2025

Summary: The callback structure has been updated to ensure consistency with new feature UIStreams.

  • Updated Mandate Registration Callback Structure.
  • Callback now includes a user block with collected user details.
  • Optional fields like PAN, email, and mobile will be sent as null if not provided.
{
  "decentro_txn_id": "CE96A1309D02456091C8B534A8FC820B",
  "decentro_mandate_id": "5932",
  "consumer_reference_number": null,
  "user": {
    "name": "trywrthrgf",
    "account_number": "235234534",
    "account_type": "CURRENT",
    "bank_code": "SBIN",
    "email": null,
    "pan": null,
    "mobile": null
  },
  "status": "ACTIVE",
  "message": "Mandate successfully registered.",
  "response_key": null
}

Name Validation with PAN on Create and Update Virtual Account API

  • Name-PAN Validation Implemented: Decentro has introduced a name validation mechanism using PAN validation to ensure the Virtual Account holder's name matches the PAN record.
  • During Virtual Account Creation: When name and PAN details are provided via the Create Virtual Account API, the system validates the entered name against the name fetched from the PAN.
    • If the names match, the Virtual Account will be successfully created.
    • If there is a mismatch, the Virtual Account creation will be rejected.
  • During Virtual Account Update: The same validation logic applies to the Update Virtual Account API.
    • If either the name or PAN is updated, a name validation check is triggered.
    • The update will proceed only if the name matches the PAN record.
  • API reference:

"is_active" flag on Update Virtual Account API

  • Activation Status via is_active Flag: Platforms can now activate or deactivate a Virtual Account by using the is_active flag in the request payload of Decentro’s Update Virtual Account API.
    • Setting is_active to true will activate the Virtual Account.
    • Setting it to false will deactivate the Virtual Account.
  • API reference: