Flow Release Notes | Version 3.9.5
Verifpay V3 Branch Details Enhancements
Deployment Date: October 30, 2026
The VerifyPay V3 API now returns an is_verified boolean attribute within the branch_details object. This informs merchants whether the bank branch associated with the provided IFSC has been cross-verified against authoritative banking datasets.
Sample API Response Snippet
{
"decentro_txn_id": "17FC953DF0AA4E1DA8A90ADE7EE412D1",
"api_status": "SUCCESS",
"message": "Account details retrieved successfully",
"data": {
"upi_vpa": "8972241839@upi",
"name_as_per_bank": "KAPIL DEV",
"account_number": "XXXXXXX1983",
"ifsc": "HDFC0000001",
"bank_reference_number": "e77691a8146a45d5bc85b6e6fee1c45b",
"payout_status": "SUCCESS",
"payout_amount": "1.00",
"account_type": "SAVINGS",
"name_match_score": 81,
"original_customer_name": "Kapil Kumar Dev",
"branch_details": {
"branch_verification_response_key": "success_branch_details_found",
"bank": "HDFC Bank",
"ifsc": "HDFC0000001",
"branch": "TULSIANI CHMBRS - NARIMAN PT",
"centre": "MUMBAI",
"district": "MUMBAI",
"state": "MAHARASHTRA",
"contact": "919890603333",
"address": "101-104 TULSIANI CHAMBERSFREE PRESS JOURNAL MARGNARIMAN POINTMUMBAI MAHARASHTRA 400 021",
"imps": true,
"rtgs": true,
"neft": true,
"micr": "400240003",
"city": "GREATER MUMBAI",
"swift": "HDFCINBB",
"upi": true,
"is_verified": true
}
},
"response_key": "success_account_details_retrieved"
}Compatibility & Action Required
Backward Compatible: Existing integrations will continue to function without changes. Existing response keys and payload structures remain intact.
Integration Action: Merchants wishing to automate branch trust checks can consume the is_verified flag directly to validate payout destinations during onboarding or transaction verification.
Deprecation of Remitter Whitelisting and Settlement Account Management for the V3 Virtual Account Platform.
As part of our ongoing security audits and compliance requirements, the following APIs have been deprecated:
To update the relevant details, please send an email to [email protected] with the information currently submitted through the respective APIs. Our team will assist you in updating the details in our database.
Please note that the Turnaround Time (TAT) for such requests will be 2 working days.
UPI: Dynamic QR Restrictions for Specific MCCs
As per NPCI Circular OC 141, Dynamic QR generation is now restricted for configured Merchant Category Codes (MCCs) that are not supported by certain PSPs.
Key Changes:
- QR generation requests for restricted MCCs will be rejected with an appropriate error response.
- Payment Links opened on desktop browsers will no longer automatically display a Dynamic QR for restricted MCCs.
- Users will instead see an informational screen prompting them to continue the payment on a mobile device.
- Existing payment flows remain unchanged for mobile users and non-restricted MCCs.
{
"api_status": "FAILURE",
"response_key": "error_dynamic_qr_not_supported_for_mcc",
"message": "Dynamic QR generation is not supported for the merchant's category."
}