api
api copied to clipboard
up-banking
Send Payments
This is a great api. I know there is another comment about roadmaps but is there a plan to actually create a payment through this API?
Looking forward to it to knock off this use case
App Idea: Todo list that punishes you financially by donating costs assigned to each task to a charity that you despise.
For instance: A democrat fails to accomplish task X by the deadline, which they associated $5 in value, the app then sends the $5 to the republican party.
Bring it on! Banking-as-clicking-buttons-in-a-web-UI is soooo 2010. Let me refactor my finances and replace all the tedious manual twiddling with a very small shell script.
Um. Is this ever eventuating? I was very surprised to learn this isn't part of the API.
As much as I like the simplicity of stuffing a secret into the header of an https connection, and although I do not really know enough about it to really know, it doesn't strike me as sufficient to keep 'the bad guys' at bay.
We are talking about the programmatic ability to spend money. I expect the security arrangements are exhaustingly tiresome. Not to mention the protocols around what to do after you accidentally and randomly distribute your entire life savings during a "test" run of your script.
Still, someone could throw us a bone, with a hint on how the authentication and authorization will be established, maintained, revoked, etc? And potential mishaps resolved? Any implementation details at all.
@johnmee this wouldn't be much different from, say, the PayPal API to send money, or any other type of "destructive" APIs. The user of the API is obviously responsible for any actions they take. Can't see why it would require additional authentication mechanisms beyond what is already considered secure. At most I'd expect maybe we'll have to sign some kind of agreement that all sent payments are irreversible before this feature is unlocked on our accounts. If you want to test your script, you should be running on a staging/sandbox environment.
@johnmee this wouldn't be much different from, say, the PayPal API to send money, or any other type of "destructive" APIs. The user of the API is obviously responsible for any actions they take. Can't see why it would require additional authentication mechanisms beyond what is already considered secure. At most I'd expect maybe we'll have to sign some kind of agreement that all sent payments are irreversible before this feature is unlocked on our accounts. If you want to test your script, you should be running on a staging/sandbox environment.
I understand the concern here from @johnmee. One thing you can do to reduce the risk is design mechanisms into the API that reduce these risks. Some common examples are circuit breakers / daily limits for the outflow of currency. A payments API could set these limits to be low initially to reduce the chances of devs screwing up.
Fully transferring money may be problematic, perhaps start with initiating payment requests between Up accounts? I'd really like to be able to auto shuffle my money around based on schedules and quotas
