HI, I’m just getting started with the Dwolla API (white label), so as to evaluate it as an ach gateway for my mobile platform.
I currently need to leverage an ach gateway into my backend system state machine, so it can process the ‘charge customer’ steps I have, but does implies that I need my backend to be able to consume the api seamlessly; and I can’t seem to figure out how to fit that with the oauth-user needs to login-model.
I’d basically be charging my customers (ach transfer from their accounts to my concentrating one), so I don’t really need them to login, I would just use my own dwolla account at every time.
Any suggestions around this, and how can I approach the auth. model for this purpose?