Finvu is an app people use to share their financial data through a consent-based route, so when it is not working, the cause is most often one of three things: the mobile number or account details do not match, a verification step is failing, or a consent is expired or revoked. Check those, update the app and retry. Use only the official screens and never pass a code to another person.
What is consent-based sharing, in plain words?
Instead of handing your bank login to a third party, you approve a specific sharing request: what data, for how long, and to whom. You can usually see, pause or withdraw that consent later. we cannot detail the rules or timelines, so read the app's own help and the request screen before approving anything.
What should you check when linking fails?
- The mobile number linked to your bank account is the one you are using now.
- Your phone can receive messages, including from a different region or when roaming.
- The bank is offered in the list of institutions.
- Your account is active and not dormant or restricted.
- You have a working internet connection, preferably not a shared public one.
Common failure points
| What you see | What to check |
|---|---|
| No code arrives | Number registered with the bank, network signal, message blocking |
| Account not found | Spelling, mobile number, whether this account type is covered |
| Consent request shows an error | Time left on the request, whether it was already used or cancelled |
| Data not shared after approval | Ask the requesting service; the delay may be on their side |
A worked example: matching a shared figure to your statement
Say a lender asks for your account data and its form shows an average monthly credit of ₹58,000. You check your statements for three months, salary credits of ₹56,000, ₹56,000 and ₹62,000. Add them: 56,000 plus 56,000 plus 62,000 is 1,74,000. Divided by three, that is ₹58,000. The figure matches, so the data is behaving as you would expect.
If it did not match, look for a one-off credit such as a refund, or a transfer between your own accounts, which can distort a simple average. Ask the requesting party how they calculate it.
How do you manage your consents?
- Review active consents regularly.
- Withdraw those you no longer need.
- Note which service asked and why.
- Keep a screenshot of what you approved.
A different way to keep records
A consent-based link is one way to share data; another is to keep your own copy. SpendixAI does not connect to banks through such a route. You upload statements as PDF, CSV or Excel yourself and check the rows before they are saved, which keeps each step in your hands, and the 30-day recycle bin for deleted transactions gives you room to undo a mistake. Its privacy page explains how your records are handled.
What should you not do?
- Do not approve a consent request you did not start.
- Do not read out a code to anyone, including someone who says they are from your bank.
- Do not install extra tools that promise to speed up linking.
- Do not assume a withdrawn consent has deleted data held by the other party; ask them.
When in doubt, close the app, open it again yourself and look at the requests listed inside. A genuine request will be there, and a fake one will not.
When to ask for help
- Your bank says the account is fine, but the app rejects it.
- A consent still shows active after you withdrew it.
- Someone has pressured you to link an account.
- You cannot tell who is requesting the data.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

