-
Notifications
You must be signed in to change notification settings - Fork 13
Add upibankvalidator for UPI payment address resolution #10
Comments
Thank you for filing this issue! I think it would be useful to implement this as a fallback provider. I'll keep you updated. |
@qurbat i think we should make this the primary provider. This doesn't need api key thus simplifies it much more for the users using project. |
Ideally - API providers must be a configuration option - and its upto users to chose which one they would want to use. |
I agree with @srikanthlogic on this. The API provider should be based on user choice. While I see value in and will be implementing upibankvalidator as an API provider, I will leave it as a secondary option at the moment. My reasoning is:
Given the above concerns, it may be possible that the maintainer(s) of the website, while providing a functional service, could use the data collected from queries for malicious, or more simply for non-ethical purposes. An example scenario: building a parallel database collating successful queries made with their API. Increased documentation of their project would help with accountability, however, given that no information about the maintainer(s) of the website is currently available, and that the homepage of the project is currently essentially a mimic of the landing page of several, for the lack of a better word, "shady" API projects, I am not convinced that In any case, I will keep this issue open, as I will be making a PR soon introducing support for the Thank you for the issue. I will keep you updated on the PR @leovarmak =) |
@qurbat maybe you can use this API to fetch the registered names of all the UPI
https://upibankvalidator.com/
The text was updated successfully, but these errors were encountered: