fixed

Flow Release Notes | Version 3.7.9

Enhancements to UPI collection platform

Feature: Validate Bank Account v3

We’re excited to announce the launch of Validate Bank Account v3 — an upgraded version designed to make bank account verification faster, smarter, and more reliable.

What’s New?

  • Intelligent Provider Selection – Decentro now automatically routes each request to the most optimal provider in real-time.
  • Multi-Banking Architecture – Built-in redundancy ensures seamless fallback across multiple providers.
  • Higher Success Rates – Smarter routing logic minimizes verification failures and improves overall success.
  • Hassle-Free Validation – No need to maintain wallet balances. With the discontinuation of pay-as-you-go plan for VBA, you can easily use this service through prepaid or postpaid billing models.
  • Simplified Onboarding – Onboard on VBA v3 (via consumer creation) and integrate with the new API for activation. Please reach out to our support team for any help.

Why Upgrade?

  • Improved uptime and reliability.
  • Better success rates and reduced latency.
  • Streamlined billing and easier account management.

All of Validate Bank Account — but better!


Fix: Merchant Collect Request History

Introduced a new "Collect Requests" module to resolve an issue where merchants could not view or track their initiated collect request transactions.

New History Page:

  • Displays a new table listing all UPI and VA collect requests.
  • Key Columns: Includes Created on, Decentro txn ID, Bank Reference no, API status, Payer VPA, Payer name, andtransaction status
  • Search: Enabled for Decentro txn ID and Bank Reference no.
  • Filters: Added for API status and transaction status.
  • Sort: Available by Created on date.

Transaction Drilldown:

  • The Decentro txn ID is now a hyperlink, redirecting to a detailed drilldown page for that specific transaction.
  • The drilldown page displays attempt-level details (like Bank Reference no, Status, Decentro Response Message) and includes its own search, sort, and filter options.

Fix: Missing Reference ID in Push Transaction Callbacks

  • Resolved a critical issue where client callbacks for push transaction statuses were failing due to a missing reference_id.
  • We now ensure the company_urn is always populated for all push transactions using the standardized format PT_{unique_urn}. This ensures reliable callback delivery and also makes this ID available for client use in Global Transaction Search (GTS).