Warning: session_start() [function.session-start]: open(/home/content/30/7423630/tmp/sess_66tj9lercetq88ag0quu1gucu0, O_RDWR) failed: No such file or directory (2) in /home/content/30/7423630/html/wp-content/plugins/simple-twitter-connect/stc.php on line 33

Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/content/30/7423630/html/wp-content/plugins/simple-twitter-connect/stc.php:33) in /home/content/30/7423630/html/wp-content/plugins/simple-twitter-connect/stc.php on line 33

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/content/30/7423630/html/wp-content/plugins/simple-twitter-connect/stc.php:33) in /home/content/30/7423630/html/wp-content/plugins/simple-twitter-connect/stc.php on line 33
ACH Payments Archive - TransSwipe - Merchant Services and Credit Card Processing

TransSwipe - Merchant Services and Credit Card Processing

Archive for the ‘ACH Payments’ Category

Sending ACH payments programmatically through an API

What provider offers the best way to send ACH payments programmatically through an API?

Automation is prized—the more you effectively automate, the more you can reduce errors and ensure efficiency and accuracy. Better yet, successfully automating a process can free up a ton of time, so you can focus on different tasks and optimizing every aspect of your business.

A process prime for optimization and automation is payments, specifically payouts.

We are (or should be) far beyond writing paper checks—a process that costs businesses about $13 billion annually or $7.15 per check. Additionally, payouts via credit cards can unleash painful hidden fees or added costs, making it scary if you’re not in constant manual monitoring mode.

However, programmatically sending payments via the ACH network has proven effective and efficient for many businesses.

Automate payments via ACH

The best provider for programmatic payments isn’t always the cheapest. You’ll want to consider:

  • Ease of integration
  • Cost per transaction
  • Quality of API support

Ease of integration

How quickly and easily can the new API be implemented to deliver payouts programmatically? If a solution has a cumbersome, clunky or outdated API, then it’s not worth the investment of time and money to integrate. Even if this solution proves to be the least expensive upfront, that doesn’t mean it will provide the same return on investment.

Your developers’ time is worth money. That’s imperative to understand (and respect). If your team is busy updating or reintegrating a payments API that’s constantly in-flux, then you’re wasting time and money.

Dwolla-white-label-ach-apiDwolla has a future-proof technology stack, but don’t take our word for it…the proof is in the integration. Enter, Popular Pays. Popular Pays was able to integrate Dwolla’s new White Label receive-only functionality in two weeks with one developer. A major hallmark for their choosing Dwolla’s White Label ACH APIs over the other competitors was RESTful API that could scale quickly and automate an ACH transfer process for both their accountants (overseeing company payouts) and contractors (receiving payment directly to their bank account).

Cost per transaction

After exploring options for programmatically sending ACH payments, you’ll quickly realize the trend. Most options charge you a per-transaction fee. This per-transaction fee can be burdensome, a punishment for high usage on your platform. Every payout means another fee.

Instead, Dwolla’s partners enter into a custom contract for use of the ACH APIs, based on monthly pricing.

Quality of API support

Payments can be a confusing field to negotiate—lots of players and regulations involved. You’ll want a partner who understands the ins and outs of the industry and can provide insight into how you’re performing therein.


Dwolla does this in a few ways. First, we walk through your integration to help you ensure you’re meeting our requirements; you’re not left in the dark, guessing. Second, once in a White Label contract you have access to an account manager as well as an integration specialist. If something comes up that poses a question, simply shoot it our way and we’re happy to help.

Third, Dwolla’s API allows for real-time status updates. These updates and insights into transactions allowed one rental management platform to decrease time spent on manually processing reversals by 90% while simultaneously improving transaction-related communications.

Perhaps the cherry on top of the Dwolla’s API is the Dashboard and Admin, an intuitive interface for managing payments and customers. When you’re sending thousands of payments programmatically, the dashboard beautifully tracks and graphs that progress along the way.


If you’re ready to automate another process and start sending payments programmatically, give us a shout.

Interested in learning more? Contact Dwolla

When and where to Integrate ACH Payments, 4 Examples


Credit cards are common, well known and widely used, but their ubiquity doesn’t make them the best payments option for every new application and platform being built. When you’re integrating payments, you have to make the smartest decision on how to move money therein.

That’s where ACH transfers come in, and integrating ACH payments is more functional than ever with Dwolla’s bank transfer API. Whether you’re moving money between users’ bank accounts or paying out thousands of service providers, consider an ACH solution.

But wait, that sounds pretty abstract, right? How do I do what?! Let’s make it more tangible—take a look at some proven examples of integrating with the Dwolla’s ACH API to improve payments.

1- Integrate ACH into mobile applications

slider-mockup-1Consumers are relying on mobile applications more than ever, and new services and apps are being developed to serve this rising trend. We’ve gotten to know a few companies building their own innovative applications, who are also leveraging the ACH network via Dwolla.

One example is Sweep, a mobile application that encourages better savings habits by using various spending ‘buckets’ to track goals, expenses and bills. With Dwolla, Sweep users have the ability to move funds between bank accounts and savings buckets within the app.

Another example is Lenny, which uses Dwolla’s ACH API to send GPA-based micro-loans to students bank accounts , all within the mobile application.

2 – Integrate ACH to deliver payouts to service providers

If you’ve built the best platform tailored to a unique demographic or target audience, be sure you’ve also integrated the best option for that audience to get paid. Consider college referees for example…

Hundreds of sporting events take place every week, but have you ever stopped to think about how those refs get paid? The folks at Blue Zebra Sports did. Their platform is a one-stop-shop for managing refs and officials, from scheduling to payments.


They chose Dwolla to deliver payouts to refs—here’s why:

“The reason we decided to use Dwolla is that it fit perfectly with making things easy for officials. To get paid, they enter their bank account information in Dwolla, and then they can get paid. It’s also easier for our conference clients; they connect a bank account and make payments directly from their checking account—no managing wire transfers or ACH deposits into a third party account before being able to pay officials.“

Jeff Wigal, Founder and CTO

3 – Integrate ACH to improve your marketplace

Similar to paying out service providers is paying out sellers in a marketplace. We have a wide variety of partners that use our ACH API to deliver payouts to their vendors. One of our favorite examples comes from boutique marketplace  Jane.com.Jane.com Blog Header

By building bank transfers right into their platform with our  API, Jane.com is able tohey programmatically deliver payouts to thousands of boutique sellers. The the boutique’s sales are paid right to their bank account.  

Another example of using ACH for payouts is Wunder, a solar energy investing platform. Their investors and investees are paid out solely via Dwolla’s API. To invest in solar energy, just connect a bank account.

4 – Integrate ACH to offer an additional payment option on your platform

Finally, a simple, yet smart addition of ACH payments is as an additional payments option, right alongside credit cards. For businesses, there is supreme benefit to encouraging adoption of ACH over paying with a credit card—you keep more money because you cut out those pesky percentage-based transaction fees.

WODTogether did just this. They’ve built a platform for better gym management and integrated Dwolla’s bank transfer technology (in two weeks) to save its users money in collecting recurring membership fees.

WODTogether dashboard

Whether you’re looking to move money in a mobile application or make payouts to the thousands using your platform, tapping into the ACH network is always a smart option to explore.

For more information on how you could improve payments processes, contact an integration specialist today. Just drop a line in below.

Get started with ACH transfers

We’ll help you design your ideal payments experience.


Thank you

A Dwolla representative will reach out to you within one business day.


There was an error and your the form was not submitted.

ACH Payments for Developers (by a developer)

ACH for developers blog header

So you want to integrate payments into your application?

You head over to Google and search ‘integrate payments’ and the barrage of information is seemingly endless, countless options each with their unique value prop. In your search you’ll come across ACH transfers.

If this term is foreign, don’t stress. We’re going to break down ACH transfers for developers right here, and then we’ll explain more specifically what you need to know about an ACH transfer powered by Dwolla.

A brief overview of ACH

ACH refers to the Automated Clearing House, an electronic network that allows banks and their customers  to send funds between one another in the United States. Basically, when you pay a bill online and opt to use a ‘bank account’ rather than a credit card, your payment is being processed through the ACH network. By entering your account and routing number instead of your credit card number, you’re initiating an ACH transaction.

For a more details breakdown of ACH, check out this ACH for beginners blog post.

How ACH works with Dwolla

Think of Dwolla as the on-ramp to the ACH network. Dwolla’s API alone does not let you process payments, but rather it connects you to enable bank transfers between you and your users.

Integrating Dwolla into your platform or application allows you to enable bank transfers via the ACH network. With Dwolla White Label our ACH transfers fall behind the look and feel of your brand—better yet, some partners have even integrated this in as little as two weeks.

Dwolla ACH transfer lifecycle and events

Dwolla’s API simplifies the ACH bank transfer process down to a single API call. Your application tells Dwolla the “funding source”(Bank Account) of the payer, and the destination account or email. Behind the scenes Dwolla handles the necessary steps to send the transfer through the ACH network, notifying your application along the way of any ‘Event` that occurs throughout the transfer process via webhooks.

In this example, we’ll outline a Dwolla user, “Bob” making a payout from your application at 2pm CST on Monday from his bank account to “Alice’s” email address, an email that is not associated with an existing user account.

It is important to note that Dwolla is a network in itself, meaning that all bank transfers are routed through the Dwolla network before reaching their intended destination. Think of this as an archway the funds pass through before reaching Alice’s account.

Assumption: Bob has a Dwolla account already created and has linked and verified his bank account.

Transfer created

Bob will specify which bank account he intends to use as the source of his transfer—represented as a unique funding source resource within Dwolla—and where he wants those funds to go. In this example, he wants the funds to go to an email address.

Using the transfer API and with authorization from Bob, your application will call Dwolla’s API telling Dwolla to create an ACH transfer. If the API call was successful, Dwolla will create a unique transfer ID: 8576f0c3-d1cd-e511-80de-0aa34a9b2388. At which point, a notification with the topic of ‘transfer_created’ is sent asynchronously to your application.

         "href":"mailto: alice123@email.com"

Events: bank_transfer_created and transfer_created
Transfer status: “pending”

Transfer in-process

Dwolla’s cut off for bank transfers is 4pm CST, and once our file has been sent out for the day, the process described in our <ACH for beginners blog post> takes over.  While the transfer is being processed through the ACH network, the transfer status remains as “pending”.

Transfer status: “pending”

Transfer settlement

Once the funds have cleared in the Dwolla network, Alice will receive an email stating that she’s received funds from Bob, and she can quickly claim these funds by creating a Dwolla Direct account—a simple process in which she provides her routing and account number. As soon as these funds have cleared, a transfer_completed event is sent via webhook to your application and the transfer status is updated to “processed”. All subsequent transfers to Alice’s email address will be routed directly to her linked financial institution.

Events: bank_transfer_completed and transfer_completed
Transfer status: “processed”

Transfer failures and ACH returns

Due to the nature of ACH, a bank transfer can fail for a number of reasons, even after the transfer has been processed (Insufficient funds, payment dispute, closed bank account, etc.). Your application should be prepared to handle ‘transfer_failed’ events from Dwolla. More information here.

As a developer, facilitating ACH transactions can be simple, and the first step is getting familiar with what that flow looks like. Now that we’ve explained what an ACH transaction looks like with Dwolla, get started with your integration today!

view the documentation

Building your own ACH solution vs. Building with Dwolla White Label

fintech-1 copy

ACH is cheap—at least that’s what you’ll find when you Google for cost comparisons of facilitating bank transfers versus processing credit cards. However, while the transaction itself can cost mere pennies, what does it really take to get up and running with ACH for payments?

While the inexpensive per transaction cost of ACH is the siren call that draws many businesses and developers to the network, its complexities and traditional inflexibility are fraught with hidden costs and requirements that often drive hopefuls away. When you have a product you want to share with the world, you don’t want to spend tedious months building your own ACH payment solution as well.

Building your own ACH solution

One of the most common do-it-yourself solutions requires you to work with a commercial bank’s interface, uploading a CSV file that contains a batched deposit amount with beneficiary account details. Customer and bank verification is a must—and it’s on the business to handle.

Bank account verification can usually be accomplished by making micro-deposits in the customer’s account. For any miskeyed or inaccurate account numbers, error notifications will be generated. You’ll need these to be collected each day, and customers must be notified in order to resolve the issues. Finally, if you are going to handle bank information in the slightest you’ll need to understand SSL and how to properly encrypt your customer’s data.

On top of that you have to handle ACH rejection codes, fraud mitigation, suspicious activity reports, etc.

Do you have the staff to support building and maintaining your own ACH infrastructure, as well as the capacity to expand upon additional feature sets when your customers ask for them?

Dwolla White Label

Dwolla has been working on innovating the way that businesses and developers interact with the ACH network for the past five years. We’ve built a White Label API that allows you to design your ideal ACH solution, with consultative support from our payments professionals and developers each step of the way.

5 Reasons to choose Dwolla for your ACH payments integration:

1. Easy to integrate

The Dwolla API comes with clean documentation and developer resources, as well as an easy-to-use sandbox testing environment. Dwolla plays nicely alongside any existing payments technologies you’re utilizing today.

2. Customize the experience

Enable bank transfers for your application that look and feel like your brand. From account creation to payment notifications, design the ideal end-to-end payments experience for your customers with our White Label API.

3. Security matters

We built our platform with security in mind. Let us help you manage the complexities of compliance, so you can focus on what really matters.

4. Get to market faster

Cut your implementation to a fraction of the time without cutting corners. Our team of payment experts and developers will help you build programmatic payments into your platform so that you can get to market faster.

5. Predictable costs

We don’t charge a per transaction fee, we simply work with you to determine a flat monthly-rate for your custom ACH solution. Paying partners will receive priority support and access to industry professionals every step of the way.

Leverage our team and the Dwolla White Label API to get your own reliable payment experience baked into your platform or application, without needing to hire your own team of in-house payments experts.

Get started today.

Dwolla Case Study: How Sweep Uses Dwolla ACH API for Bank Transfers

How Dwolla’s White Label ACH API quickly allowed fintech platform, Sweep to get to market.

Download the case study as a PDF

slider-mockup-1According to Center for Financial Services Innovation, consumers who have regular savings habits are 4X more likely to be financially healthy than those who don’t. Unfortunately, 57% of Americans still struggle financially and more than 72% suffer from stress and anxiety related to money (American Psychological Association). Sweep hopes to fix that.

Problem: A consumer fintech platform wanted to offer its customers an automated savings product using bank-to-bank  transfers.  The company needed to meet all regulatory and compliance requirements in an aggressive timeline.

Results: The company integrated Dwolla’s White Label payments API to facilitate ACH transfers in around 40 hours and successfully announced product on-stage at Money2020.

The Situation

How Sweep Uses Dwolla ACH API for Personal Financial Planning App

Sweep was created to help young, millennial consumers save and stay ahead of their needs.  After downloading Sweep’s mobile app, users connect the platform to their bank accounts and then organize their funds into “buckets” for goals, expenses and bills.  

From the very beginning, the vision and roadmap included automating these savings behaviors to fill those buckets and grow savings according to the user’s needs.  For example, a user who created a “Wedding” bucket would be able to automatically transfer $100 from her main checking account at a multinational bank each payday to a savings account associated with the goal—in this case, say, at her local credit union. Unfortunately, Sweep encountered a number of regulatory and technical hurdles that prevented them from including and automating bank-to-bank transfers in its initial launch earlier in 2015.

The Challenges

Lacking this functionality to programmatically transfer funds meant users had to visit separate online banking portals and manually transfer funds between banks to fulfill their savings goals. Automating the process was critical for millennials and they didn’t have it, yet. 

FinTech Application Sweep Uses Dwolla API for Bank Transfers

“Unfortunately, our ideas were too new for the banks and traditional payments processors. We considered building our own payments gateway but the banking relationship and compliance requirements would have blown up our roadmap and crippled our product plan.  We needed an innovative technology partner with a proven banking relationship.”  

CEO and Co-founder, Jackson Gates

Jackson - Sweep

Time to market

An end-to-end payments solution would require a direct banking relationship and 3-6 months of development time, not including the upfront compliance and regulatory hurdles.  Other payment gateways were working on new banking relationships but couldn’t guarantee a timeline or necessary functionality.  Sweep needed an immediate solution.

Solution: Unlike other payments solutions, which used non-descriptive and difficult to parse XML, Sweep leveraged Dwolla’s “clear and concise API documentation and excellent engineering and customer support” to build the solution in around 40 hours.

Outcome: With Dwolla’s White Label API, Sweep was testing live payments within days, and completed all production testing in-time for its Money 2020 announcement.

Regulation and compliance concerns

In addition to the time and cost associated with compliance and regulatory requirements, the uncertain and shifting regulatory climate made it difficult to predict the mid- to long-term needs of supporting a proprietary payments infrastructure.

Solution: Through Dwolla’s API and built-in processes, Sweep outsourced its payments back end, including bank transfers via ACH, to Dwolla. By partnering with Dwolla, Sweep leveraged Dwolla’s experience for managing the compliance, fraud, and security elements of its payments experience.

Outcome: Sweep launched its automated savings product with fixed and comparatively minimal direct and indirect costs. By leveraging Dwolla’s banking relationships, Sweep avoided holding customer funds or inserting itself in the funds-flow, thereby reducing regulatory and compliance challenges.

Core functionality and user experience

Sweep’s strength is its ability to create a simple, beautiful mobile interface and user experience.  The company was wary of integrating any functionality that would feel foreign to the app or confuse the customer.

Solution: Dwolla’s payments platform helps with handling KYC, customer records, adding bank accounts, and initiating ad-hoc and recurring transfers using event-based webhooks. The white-label API allows Sweep to offer a seamless user experience while maintaining the look and feel of the Sweep app.

Outcome: Today, Sweep users enjoy a full-featured, powerful savings tool embedded in a Sweep branded, beautiful mobile experience.

Screen Shot 2016-01-21 at 12.28.02 PM

Screen Shot 2016-01-21 at 12.27.26 PM

Interested in learning more about an ACH API for better payments? It’s simple. Reach out to an integration specialist to learn more.

Reach out now, green

Gym membership payments made easy with platform WODTogether

Gym management platform, WODTogether, integrated Dwolla’s bank transfer technology (in two weeks) to save its users money in collecting recurring membership fees.


According to Forbes, there are now nearly 11,000 CrossFit gyms worldwide, up 22-fold from nine years ago. That’s a massive market that’s only growing larger. With the exploding number of CrossFit gyms and gym go-ers, three friends saw an opportunity to build software to ease running a training facility.

About WODTogether

WODTogether provides software to help run gyms, from membership management and billing features to coordinating group fitness facilities. Self-proclaimed “CrossFitters doing CrossFit, and coding”, Brian Holub, Michael Starich, and Adam Holub have a built a solution that meets all needs.

For a flat monthly fee, registered gyms get the support they need from a gym management software, including workout tracking, scheduling, tools for athletes and billing management.

The Problem

To create a holistic solution, WODTogether needed to offer the best possible payment options for gym managers. They had previously integrated credit card payments, but—as most business owners can relate to—those fees were high and hard to for gyms to manage so WODTogether wanted to provide an additional payment choice.

“The payments industry can be complicated, frustrating, and expensive for our users. We’re always looking for better options, and Dwolla’s fees (or lack thereof) is a game changer. The great API and documentation made it a no brainer.”

Brian Holub, CEO

b headshot - WODTogether

The best option would be easy to integrate, simple for users to get going, and cut out those percentage-based fees gym owners stress over.

The Solution

It was clear WODTogether needed a payment integration that was simple, straightforward in cost, and would allow for payments for both recurring services as well as one-off expenses. Dwolla met these requirements, and then some.

Dwolla’s bank transfer software allowed for:

  • Easy on-boarding of members—entering banking information is easier than inputting credit card information, no need to pull out the wallet and enter a string of 16 digits from a credit card
  • Payment of recurring gym membership fees
  • Collecting on individual expenses like refreshments, supplements, apparel, private training, or special event fees
  • A quick integration turnaround time from the WODTogether teamce

As an additional bonus, WODTogether use Next Day Transfers, so funds are moved in 1-2 business days, which—in their words—“crushes” traditional ACH payments processing times.

WODTogether dashboard

Just like a good CrossFit workout, the team at WODTogether needed an efficient and effective integration. Using Dwolla’s PHP Library, their team was able to integrate our co-branded solution in just a couple weeks. A quick turnaround time for a very lean development team.

Their biggest point of delight: the test environment. They were able to build and test the solution in UAT, allowing a quicker ramp up time.

Now, users simply select to connect their bank account via Dwolla, and are sent through the OAuth flow.

Fast, Simple and Focused

WODTogether touts software that is fast, simple and focused, helping gym managers and coaches keep ahead of their demanding day-to-day. To provide the best possible solution, WODTogether integrated Dwolla.

Now as gyms scale, they can avoid losing valuable profit to credit card fees and they’ll be able to count on their users’ membership payments coming in regularly—thanks to recurring payments in the API.

“CrossFit gyms vary greatly in size, from as little as a few thousand dollars to tens of thousands in monthly revenue. Whatever the size, gyms stand to save hundreds of dollars a month if they accept payments via Dwolla. We’re now able to offer greater value to our members.”

Michael Starich, President (and gym owner)

m headshot - WODTogether

Curious how your payments could improve? Drop our consultants a line.

Read out to Learn more, blue

Solar investing platform uses Dwolla API to power bank transfers

Case Study Header - Wunder

Investing in the renewables industry has notoriously come with a high barrier to entry and has been reserved for the likes of Google and Berkshire Hathaway. But as more money is pumped into the market, renewable technologies advance, risk is minimized, and these barriers begin to erode.


Wunder is on the leading edge of this change, bringing opportunities to invest in the burgeoning solar energy business to individual accredited investors. By leveraging proprietary algorithms and a team of solar specialists, Wunder is able to screen solar investment opportunities more accurately and efficiently than most banks. Once these opportunities are thoroughly vetted, selected investments are bundled into funds and made accessible to individual accredited investors through an online investment platform. With Wunder, accredited investors can quickly and securely invest in these diversified portfolios of high-return solar projects with as little as $1,000.

On a mission to simplify the financing and investing experience for both solar installers and investors, Wunder has delivered an easy-to-access marketplace for both parties to connect and scale more effectively.

The Problem

A key component to the Wunder platform involves the movement of both investments and returns through the platform. Bank transfers over the ACH network are central to providing a streamlined investor experience, but building this infrastructure from the ground up would be wildly cost prohibitive. After launching the platform earlier this year, it quickly became apparent to the Wunder team that anything short of a fully automated payments solution would be untenable at scale and that real-time insight into the changing statuses of ACH transactions would be crucial.

The Solution

Dwolla allows Wunder to brand the account set up experience and fold the bank account linking into the registration process. Additionally, Dwolla gives Wunder increased visibility into the funds flow, from collecting individual investments to batching the funds and distributing them to the solar installation projects. Each month, Wunder receives payments from the energy customers repaying their loans and distributes those returns to the fund investors.

Wunder is also able to leverage Dwolla’s API to send branded communications to their customers via a series of webhooks, alerting customers to changes on their account or transaction status.

“We have looked high and low for a provider capable of seamlessly and securely facilitating our ACH transactions, and we couldn’t be happier to be partnered with Dwolla. Their API allows us the flexibility that we need to deeply integrate ACH transactions into our platform without disrupting our user experience. From customer identity verification to bank account verification to the transactions themselves, Dwolla takes the complex world of payment processing and wraps it up into an API that is painless to integrate. And perhaps most importantly, working with the Dwolla team has been an absolute pleasure.”

Dave Riess, CTO of Wunder


Are you evaluating your payment software? If so, contact us.

Contact our team orange

Integrating with Dwolla’s powerful white label ACH payouts solution

White Label Payments with Dwolla

Last week we released our white label solution for businesses and nonprofits looking to streamline their ACH payouts. Within your own application or online portal, Dwolla white label puts a powerful ACH payments platform behind your brand and logo.

The white label solution allows you to transfer funds seamlessly, from customer on-boarding to how your businesses name is displayed on your customer’s bank statement.

While managing the role as payment originator, Dwolla provides a simple, easy-to-implement API to power your payments and help you manage risk, fraud, and compliance.

When implementing Dwolla’s white label payout solution, there are three major components that require different levels of verification to get going:

  1. The creation of a customer record
  2. The association of a funding source with that customer record
  3. The transfer of funds between linked accounts

To test the API requests, you’ll want to first create a sandbox account.

Creating a Customer Record

Once you’ve set up a testing account, you’ll begin by creating a customer record, which requires at least a full name and email address for each user you’d like to transfer funds to. Once the customer record is created, you will find the customer object URL in the location header.

Pro tip: To enhance Dwolla’s ability to monitor fraud, we strongly recommend providing the IP address of the end-user accessing your app as the ipAddress parameter.

Here’s what the request and response should look like:


Connect a funding source

Once you’ve successfully created a customer record, the next step is to associate a funding source. This step calls for three additional pieces of information, so funds can automatically be sent to this customer record:

  • Bank account
  • Routing number
  • Account type (ie. government, nonprofit, business)

All information provided in this step is securely stored with Dwolla.


Subscribe to Webhooks

In order to transfer funds between your account and the customer record, you’ll first set up webhooks to notify your customer when an event occurs. To create these webhooks, start by creating a client access token and use the credentials provided.

Once you’ve generated this token, continue on to creating the webhook subscription. Start by calling the webhook-subscriptions endpoint with your callback URL.


Now that you’ve made your subscription, Dwolla will send webhook notifications to the provided URL. Responses take about 20 seconds to deliver after the event has occurred, but if you miss one, no worries—8 delivery attempts are executed over the course of 72 hours. An example webhook is shown below.

Transfer funds from account to account

The final step in this process is creating a transfer from your account to a customer. To do so, you’ll need the information for the bank account that sources the funds and the customer to which the funds will go.

The transfer of funds is a three-step process. In short you will follow these steps:

  1. Fetch a list of available funding sources using the List Funding Sources (Account) endpoint.
  2. Create a transfer by specifying the account’s funding source as the source and the customer as the destination.
  3. Check the transfer status by referring to its ID.

Once this action is complete, a receipt of a webhook will indicate a change. This can be used as a trigger to communicate with the customer, sending an email with an update on the status of funds.

Above we’ve provided a quick breakdown of what the integration process looks like with our white labeled bank transfers solution. To get the full guide, visit our developer portal.

If you’re interested in learning more about Dwolla’s powerful payments tools and API, reach out to sales@dwolla.com.

reach out now

©2018 TransSwipe


Warning: Unknown: open(/home/content/30/7423630/tmp/sess_66tj9lercetq88ag0quu1gucu0, O_RDWR) failed: No such file or directory (2) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0