# Funding source location empty but 200 OK response

**URL:** <https://discuss.dwolla.com/t/funding-source-location-empty-but-200-ok-response/8089>\
**Category:** Funding Sources\
**Created:** [May 20, 2022, 2:09pm UTC](https://discuss.dwolla.com/t/funding-source-location-empty-but-200-ok-response/8089 "2022-05-20T14:09:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brent\_Y](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@Brent\_Y](https://discuss.dwolla.com/u/Brent_Y)\
**Post date:** [May 20, 2022, 2:09pm UTC](https://discuss.dwolla.com/t/funding-source-location-empty-but-200-ok-response/8089/1 "2022-05-20T14:09:15Z")

</div>

I’m using Plaid to get a Dwolla processor token, then I created a customer in Dwolla and now creating a funding source for the customer.  
This code was working successfully before and not sure what I did to make it stop.  
I was able to go through the entire process and complete a funds transfer but it’s not working now.

I’m making the call to customerUrl/funding-sources with the Plaid processor token and the account name.  
The response comes back with ‘200 OK’ but there is no location property in the header.

Request (the header does have the ‘Authorization: Bearer xxxx…’ present):

{“name”:“Plaid Checking”,“plaidToken”:“processor-sandbox-9f2c5db7-bb27-4f21-8ecd-172251c3e89a”}

The response includes the id, email, name, etc. of the customer, but no location in the header.

If I login to the Dwolla sandbox dashboard, the customer is present but no funding sources exist.

How can I troubleshoot what the issue is?  
Thanks,  
Brent

---

<div class="post-metadata">

**Author:** ![shreya](https://sea2.discourse-cdn.com/dwolla/user_avatar/discuss.dwolla.com/shreya/32/2154_2.png) [@shreya](https://discuss.dwolla.com/u/shreya)\
**Post date:** [May 20, 2022, 8:01pm UTC](https://discuss.dwolla.com/t/funding-source-location-empty-but-200-ok-response/8089/2 "2022-05-20T20:01:14Z")

</div>

Hi @Brent_Y – do you have any Customer IDs handy as examples?

---

<div class="post-metadata">

**Author:** ![Brent\_Y](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@Brent\_Y](https://discuss.dwolla.com/u/Brent_Y)\
**Post date:** [May 21, 2022, 12:16am UTC](https://discuss.dwolla.com/t/funding-source-location-empty-but-200-ok-response/8089/3 "2022-05-21T00:16:07Z")

</div>

The last one that was related to that token was: d2a40894-b371-4294-9a24-f71f3f38abcd

---

<div class="post-metadata">

**Author:** ![Brent\_Y](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@Brent\_Y](https://discuss.dwolla.com/u/Brent_Y)\
**Post date:** [May 23, 2022, 3:17pm UTC](https://discuss.dwolla.com/t/funding-source-location-empty-but-200-ok-response/8089/4 "2022-05-23T15:17:56Z")

</div>

Never mind, I was able to find the issue. I was passing the customerUri without the ‘funding-sources’ at the end. Strange how it returned success though.

Brent

---

<div class="post-metadata">

**Author:** ![shreya](https://sea2.discourse-cdn.com/dwolla/user_avatar/discuss.dwolla.com/shreya/32/2154_2.png) [@shreya](https://discuss.dwolla.com/u/shreya)\
**Post date:** [May 25, 2022, 4:25pm UTC](https://discuss.dwolla.com/t/funding-source-location-empty-but-200-ok-response/8089/5 "2022-05-25T16:25:26Z")

</div>

Hi @Brent_Y – thanks for the update! Yup – I was able to recreate this as well. Looks like the endpoint just treats it as an update to the customer resource, when it should fail validation with a BadRequest error. Thanks for reporting this!
