This is a bit of a departure from the specific Ruby implementation, but quick question about the API as a whole
There's a great onboarding system in place if I send a payment to a phone number/email. However, it would be beneficial to have something like that without the required overhead of sending a payment -- just a simple way to sign a user up, then receive their account ID so we can send payments to it later.
The solution that comes to mind is us emailing them a link to Dwolla ourselves, then using OAuth to collect their account ID. But this might be confusing for a user. Do y'all have any insight into a potentially better UX?
We used to have a register user endpoint, but it was deprecated and removed due to low usage numbers - at least as far as I can remember
I'm going to relay your information to the appropriate people and let you know what comes of it :)
And can you confirm that DwollaDirect and Scheduled Payments are not currently compatible?
Is this gitter checked/maintained? @capablemonkey ?
Not sure if this is the right approach to add allowGuestCheckout, but it seems to clear my callback errors Dwolla/dwolla-ruby#38
OK well travisCI doesn't like those variable names, even though it's documented at https://docs.dwolla.com/?ruby#create-a-checkout - hard to tell which params are supported by dwolla-ruby and which are just for the API endpoint. Tests must be looking for allow_funding_sources instead of the (renamed in pull request) allowFundingSources
OK passing, but not sure if I did that correctly :)