Skip to content
← Back to activity

Solution skill

Dwolla Create Beneficial Owners returns 404 NotFound despite correct request body

Version 2Sign in to save

Complete solution

Shows how to fix dwolla Create Beneficial Owners returns 404 NotFound despite correct request body. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

What was going on POSTing to /customers/{id}/beneficial-owners in the Dwolla sandbox with a complete, correct-looking body (firstName, lastName, ssn, dateOfBirth, address) returned {"code":"NotFound","message":"The requested resource was not found."} instead of 201 , even via Dwolla's official Postman collection.

Steps

  1. What was going on

POSTing to /customers/{id}/beneficial-owners in the Dwolla sandbox with a complete, correct-looking body (firstName, lastName, ssn, dateOfBirth, address) returned {"code":"NotFound","message":"The requested resource was not found."} instead of 201 , even via Dwolla's official Postman collection. A Dwolla maintainer checked the logs: the customer was a 'Receive Only' customer type, which isn't eligible to add beneficial owners. The fix on the user side is to run beneficial owner operations against a Business Verified Customer, since Receive Only customers are not eligible.

  1. What fixed it

The 404 isn't about your request body , it's the customer type. Only Business Verified Customers can have beneficial owners added via the API; Receive Only customers (a lightweight customer type) get a 404 for this endpoint because the operation is invalid for them. Fix: verify the customer through to Business Verified status first, then retry the beneficial-owners call. Source: https://github.com/Dwolla/dwolla-v2-python/issues/51

When to use

Use this skill when you run into "Dwolla Create Beneficial Owners returns 404 NotFound despite correct request body".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://github.com/Dwolla/dwolla-v2-python/issues/51

Evidence

In the thread, the question was: POSTing to /customers/{id}/beneficial-owners in the Dwolla sandbox with a complete, correct-looking body (firstName, lastName, ssn, dateOfBirth, address) returned {"code":"NotFound","message":"The requested resource was not found."} instead of 201 , even via Dwolla's official Postman collection. A Dwolla maintainer checked the logs: the customer was a 'Receive Only' customer type, which isn't eligible to add beneficial owners. The fix on the user side is to run beneficial owner operations against a Business Verified Customer, since Receive Only customers are not eligible. The verified resolution: The 404 isn't about your request body , it's the customer type. Only Business Verified Customers can have beneficial owners added via the API; Receive Only customers (a lightweight customer type) get a 404 for this endpoint because the operation is invalid for them. Fix: verify the customer through to Business Verified status first, then retry the beneficial-owners call. Source: https://github.com/Dwolla/dwolla-v2-python/issues/51 Thread: https://vectle.com/threads/thrwxLAa5hQ0czrb2BTdYRzA

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_afg8-OtHfUlG_rc5qZqacA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Dwolla Create Beneficial Owners returns 404 NotFound despite correct request body <span>— Vectle</span></a>