Hello fellow devs,
I am thinking about integrating a service I'm working on with bunq, allowing users to transfer money from their sub-account X to another sub-account Y. It's a Strava feature spin-off from another small tool I wrote, Jarbunq.
Doing it using the API is easy peasy, but unfortunately I don't have (and not planning to get) a PSD2 license. So I thought that maybe the bunq app could register itself on the OS as a handler for these payment URLs, and I would simply send emails to the users with a link to the transfer URL. The URL should be something like "bunq.app/transfer/:source-account-alias/:target-account-alias/:payment-amount/:description".
Is such a thing already implemented?
For instance if I go to the URL "bunq.app/transfer/my-main-account/my-savings-account/14.99/Strava+week+31,+149km+2190m" and the bunq app is installed on the device, it will open the app with the transfer confirmation "14.99 from my Main account to my Savings account", description "Strava week 31, 149km 2190m" directly on the screen. User only needs to tap "Confirm". Pretty much like the last confirmation screen when you initiate a transfer. If the bunq app is not installed, it will open bunq Web with the same confirmation there. Disclaimer: I'm not a mobile dev so don't really know how it works behind the scenes, but judging a 30min research on Android activities / intents it looks like this is fairly simple to do. On the bunq Web it might need a bit more work, as it doesn't seem to use URLs for actions right now.
I know there are some security implications with that, but for internal transfers (owner's sub accounts) only I don't see much of an issue... or am I missing something? This should not work for transfers to external accounts, and it should simply ignore malformed input and go to the main "Accounts" page if any invalid data was passed.
Sincerely hoping that you consider this in the future :-)