Sandbox update: Improvement to simulating bank transfer processing

(Spencer Hunter) #1

In early 2014 we released our public Sandbox to third-party developers so they could test against the Dwolla API. Along with the release of the Sandbox environment, developers needed a way to simulate bank transfer processing, so we introduced a tool called the “Sandbox Console”. The Sandbox Console’s primary function was to give developers the ability to view transactions initiated to/from test accounts and provide a way to trigger the outcome (processed or failed) for bank transactions. Overall, it performed its function, but was missing key functionality to test various scenarios that may occur in production, and at times, it was unreliable.

After consideration of the current state of the Sandbox Console and its increased usage we decided to go out with the old and in the the new…

What’s new?

Over the past few months we’ve been hard at work making enhancements to the developer experience within the Sandbox. Our main focus being simplifying our Sandbox and getting developers up and running much quicker with the Dwolla API. Previously, the existing experience required a lengthy signup process with far too much interaction between different Dwolla applications. After the introduction of our Dashboard and Admin, we thought this would be a great fit for an all-encompassing UI for developers.

The “Process bank transfers” button

A “Process bank transfers” button is now available in the Sandbox Dwolla Dashboard. This button can be used to simulate bank transfer processing. Once the button is clicked, Dwolla will initiate or fail the last 500 bank transfers (see below for how-to trigger bank transfer failures) that occurred on your Sandbox account or the White Label Customer accounts you manage.

Trigger bank transfer failures

We now allow you to trigger various bank transfer failures by specifying an “R” code in the funding source name parameter when creating or updating a funding source for a Dwolla Account or White Label Customer. When a transfer is initiated using a funding source that has an “R” code assigned to its name, a transfer failure event will trigger and the status will update to failed when you click the “Process bank transfers” button (as mentioned above).

####Example of using a sentinel value to test bank transfer failures

Content-Type: application/vnd.dwolla.v1.hal+json
Accept: application/vnd.dwolla.v1.hal+json
Authorization: Bearer pBA9fVDBEyYZCEsLf/wKehyh1RTpzjUj5KzIRfDi0wKTii7DqY
  "routingNumber": "222222226",
  "accountNumber": "123456789",
  "type": "checking",
  "name": "R03"

Reference our testing resource article for more information on simulating bank transfer processing and other test cases that can be produced in our Sandbox environment. If you have any questions on the updates mentioned above or feedback/thoughts on other Sandbox enhancements, please don’t hesitate to let us know!

Test automation using UAT
Showing transfer status "pending" in Sandbox environment
How deposit funds to test funding sources
(Spencer Hunter) #2

(Yakovivanov) #3

Is there an API for the “Process Bank Transfers” button?

(Spencer Hunter) #4

@yakovivanov, Yep! Reference the request below, which does the same thing as the Process bank transfers button. Note: this is a POST with an empty request body.

Accept: application/vnd.dwolla.v1.hal+json
Content-Type: application/json
Authorization: Bearer {accessToken}