403 Forbidden on Verified Customer Creation

We just received our production keys and are now receiving a 403 forbidden when attempting to create a verified customer. Everything is working properly in our staging env hooked up to your sandbox. We are wondering if it may be a similar issue to Unable to get on demand authorization with production keys. I have confirmed the env vars setting the key and secret are correct.

Hi @gthom – it does look like a similar issue to the post your mentioned. Apologies on behalf of Dwolla for the inconvenience!

I have notified our team to enable the correct settings in your account to match your contract. However, the team has signed off work for today, but should be able to get to it the first thing tomorrow morning Central Time when they’re back in the office!

Again, we’re sorry for the troubles! I’ll keep you updated!

Update: Just got confirmation from our team member that we’ve corrected the settings.

When you get a chance, please give it a try and let us know if you run into any issues! :pray:

@shreya Thank you so much, the issue has been resolved.

1 Like

Awesome! Thanks for the update, and for your patience with us on this!

@shreya

Getting a similar error on out Production account when trying to allow users to add their banks (Get Authorization) - 403 Authorization.

Sample User ID failing from Live acccount: 6164a7bc-4f2e-45b9-8452-048bfb2e9f25

Thanks!

Hi @Pasquale_Scaife – thanks for that ID!

I’m not seeing attempts to add a funding-source to that Customer. Would you be able to share the request ID of the request that was failing? It can be found under the response headers as x-request-id.

Ah, I am seeing some POSTs failing with 403 status code to the following endpoint -

http://api.dwolla.com/on-demand-authorizations

On-demand authorizations isn’t enabled by default and needs further approval from the Dwolla team before enabling for your account. I just circled back with our Account management team and they were able to enable it for you!

Would you be able to give it another a try when you get a chance and let us know if you run into any issues?

Here’s the response error. I just tried again for ID: 61ddce89-7f95-4812-a612-37d79ff7fed7

Workflow error - Plugin action Dwolla - Create on-Demand Authorization error: Error: {“code”:“Forbidden”,“message”:“The supplied credentials are not authorized for this resource.”} at errorFrom (/var/task/node_modules/dwolla-v2/src/dwolla/Token.js:49:15) at /var/task/node_modules/dwolla-v2/src/dwolla/Token.js:70:29 at tryCatcher (/var/task/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/var/task/node_modules/bluebird/js/release/promise.js:547:31) at Promise._settlePromise (/var/task/node_modules/bluebird/js/release/promise.js:604:18) at Promise._settlePromise0 (/var/task/node_modules/bluebird/js/release/promise.js:649:10) at Promise._settlePromises (/var/task/node_modules/bluebird/js/release/promise.js:729:18) at _drainQueueStep (/var/task/node_modules/bluebird/js/release/async.js:93:12) at _drainQueue (/var/task/node_modules/bluebird/js/release/async.js:86:9) at Async._drainQueues (/var/task/node_modules/bluebird/js/release/async.js:102:5) at Immediate.Async.drainQueues [as _onImmediate] (/var/task/node_modules/bluebird/js/release/async.js:15:14) at processImmediate (internal/timers.js:461:21) Error: Outer Error (see above for inner error) at Block.wait (/var/task/u.js:420:34) at Object.async_fn [as async] (/var/task/index.js:302:35) at eval (eval at build_function (/var/task/index.js:72:21), :16:22) at /var/task/index.js:335:23 at run_fn (/var/task/u.js:594:18)

Hmmm…I’m not seeing any recent calls to that endpoint from your Production account. The last call was at 11:22:17.444 AM CT before the setting was enabled.

Would you be able to give it a try again?