The Sandbox Dashboard allows you to manage Customers, as well as transfers associated with the Customers that belong to your Sandbox account. Once your application has created its Customers, you can access the Sandbox Dashboard to validate that the request was recorded properly in our test environment.
There are various reasons a Verified Customer may have a status other than
verified after the initial Customer creation. You will want your app to be prepared to handle these alternative statuses.
In production, Dwolla will place the Verified Customer in either the
suspended state of verification after an initial identity verification check.
For personal Verified Customers, reference the guide on customer verification for more information on handling identity verification for Verified Customers. To simulate the various statuses in the Sandbox, submit either
suspended in the firstName parameter in order to create a new Verified Customer with that status.
For business Verified Customers, reference the guide on customer verification that goes over information on properly verifying a business's Controller, the business and associated Beneficial Owners. To simulate the various statuses in the Sandbox, submit either
suspended in the controller firstName parameter in order to create a new Verified Customer with that status. To simulate different verification status for Beneficial Owners, submit either
document in the beneficial owner firstName parameter.
With business Verified Customers, documents may be needed for the Controller, the business, or both the Controller and business. To simulate the
document status for the controller, submit
document in the controller firstName parameter.
Similarly, to simulate the
document status for the business, submit
document in the businessName parameter. To simulate both the Controller and the business in
document in both the controller firstName and the businessName parameters.
If a Personal Verified Customer isn’t systematically identity-verified after their second attempt to retry their information, the Customer may be placed in a
kba status and will be required to successfully answer at least three out of four knowledge based authentication (KBA) questions in order to pass verification.
To simulate the
customer_kba_verification_passed event as the result of KBA success in Sandbox, answer all four questions with either “None of the above” or “I have never been associated with this vehicle”. As a result, the Customer will be placed in a verified status and the
customer_verified event is triggered.
To simulate the
customer_kba_verification_failed event as the result of KBA failure in Sandbox, answer the questions with any answer choices other than “None of the above” or “I have never been associated with this vehicle”. As a result, the Customer will be placed in a document status and the
customer_verification_document_needed event is triggered.
If a Verified Customer isn't systematically identity-verified, the Customer may be placed in a
document status and will require an identifying document to be uploaded and reviewed. Reference either the personal customer verification or business customer verification guide for acceptable forms of identifying documents for
Since the document review process requires interaction from Dwolla, sample test documents can be uploaded in the Sandbox environment to simulate the
Use sandbox environment to test API requests.
All funds transfers made using the Dwolla Platform are performed by a financial institution partner, and any funds held in a Dwolla Balance are held by a financial institution partner. Learn more about our financial institution partners.