Warning: session_start() [function.session-start]: open(/home/content/30/7423630/tmp/sess_ehcvennl2kgcnje0mnokpsqts4, 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
Product Updates Archive - TransSwipe - Merchant Services and Credit Card Processing

TransSwipe - Merchant Services and Credit Card Processing

Archive for the ‘Product Updates’ Category

We’ve moved! Visit the blog at dwolla.com/updates

Posted in Blog, For Developers, Knowledge Base, Product Updates, Use Cases on July 6th, 2016

Check out the Dwolla Blog at dwolla.com/updates.

Case Study: Instagram Ad platform leverages Dwolla API for payouts

A pioneering advertising platform for Instagram leverages Dwolla’s White Label Bank Transfer API to send ACH payouts to “creators”.

Download the Case Study PDF 

popular-pays-ios-screenAccording to eMarketer, social network ad spending will reach $35.98 billion by 2017, representing 16.0% of all digital ad spending globally. Popular Pays is a marketplace that connects brands with content creators on social networks. The brand has a story they want to tell or a product to promote and the creator helps them do that.


A popular payment platform created manual processes, lengthy transfer times, and unpredictable costs for a rapidly-growing advertising platform.


The advertising platform integrated Dwolla’s White Label bank transfer API in two weeks with one developer, slashing time spent performing manual payout processing tasks by 50% and reducing payouts processing costs by 31% in the first month.

The Situation

Brands use Popular Pays’ platform to partner with creators to produce powerful original content that tells the brand’s narrative.

Popular Pays invoices the brand for the cost of the campaign through payment provider A, and then facilitates ACH payouts to a creator’s bank account through payment provider B. Popular Pays’ accounting department was tasked with reconciling each payment by looking up a creator’s Popular Pays account and sending single payouts via its existing payout provider. The payout provider charged a high per transaction fee and took approximately 10 days to process.


The Challenges

Popular Pays should be able to simply automate payouts to its creators’ bank accounts. However, its existing payout provider had only a partially updated technology stack, making it difficult to build a seamless integration that would eliminate the daily chores for its accounting department—manual single-payment processing, fee computation, and reconciliation—without disrupting its creators’ experience.

Popular Pays’ existing payout provider also charged high per transaction fees, increasing its costs as transaction volume increased and making budgeting unpredictable.

While exploring payment solutions to replace its payout provider, such as tapping its existing invoicing software to process ACH payouts on the backend, Popular Pays discovered that many of these solutions required workarounds and higher transaction fees to support the automated funds flow that it desired for its marketplace.


Growing with only one or both of its existing payment solutions would restrict Popular Pays’ ability to scale, require an excessive amount of manual work, and impose a growing financial burden. Adding a cost-effective level of automation to its payment processing was critical for Popular Pays to grow and scale their platform.

“Working with their tech team on our integration was great. They were always quick to respond to questions and very receptive to feedback. A feature that we requested during a meeting with them went live only a few weeks later. This gives us the confidence that as our payment needs evolve, so will Dwolla.”

PopularPays CTO, Matt Moore

How Dwolla Helped

From manual to automatic

Popular Pays needed a flexible solution that would allow it to automate payment flows and reduce manual tasks for its accounts payable department. If it could solve this problem, it could then allocate more resources to scaling the client base and shortening the payment transfer period.

Solution: Popular Pays used Dwolla’s White Label API to link its creators’ bank accounts to their existing Popular Pays account, and designed its payout integration so that accountants could initiate payouts to creators in a few clicks of a button. This allowed for payments to be reconciled and initiated more quickly.

Outcome: The flexibility and payment automation of the Dwolla API allowed the accounting department at Popular Pays to decrease time spent on manual accounts payable tasks by 50% (and they expect to increase time saved as they scale and increase the level of automation), while drastically reducing reconciliation errors. Transfer times from Popular Pays to its creators were reduced from 10 business days to 1-2 business days.

Future proof technology stack

Popular Pays needed to integrate with a payment provider that consistently invested in updating its technology stack. Specifically, Popular Pays was looking for a RESTful API that could scale quickly while operating in a white label capacity—all without disrupting the customer experience.

Solution: Popular Pays added Dwolla’s White Label receive-only functionality, a narrow RESTful API, that programmatically and securely connects receivers (i.e. Creators) to their bank accounts within the platform’s payouts and registration processes. No additional steps were required by existing creators on the Popular Pays platform as a result of the switch to Dwolla. New creators connect their bank account during a seamless digital registration.

Outcome: Popular Pays was able to integrate Dwolla’s new White Label receive-only functionality in two weeks with 1 developer. Popular Pays on boarded 43% of its active creators within 3 weeks of launching its new payouts process, accelerating its rate of return from improvements in cost-efficiencies.

Improve cost-efficiency

For increased control of costs, Popular Pays needed a platform that offered predictable pricing month over month, rather than being charged a percentage on each transaction. Popular Pays needed a cost-effective payment solution with straightforward payment terms in order to scale effectively in its industry.

Solution: Popular Pays entered into a flat monthly payment structure to access Dwolla’s White Label bank transfers API—allowing it to automate payouts without losing large cuts of high dollar transactions to the payment platform.

Outcome: By lowering its costs of facilitating ACH payments and entering a predictable pricing model, Popular Pays was able to reduce its payouts processing costs by 31% in the first month. At the rate in which Popular Pays is growing its platform, it expects to increase this savings by 94% by the end of 2017.



Get started with your own integration

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.

Coming Soon: A new dashboard for Dwolla White Label integrations

Posted in Blog, Product Updates on June 1st, 2016

After countless wireframes, mockups, and some really informative customer interviews, we’re excited to give you a sneak peek of our new merchant dashboard—coming soon for Dwolla White Label partners.

1 - Dwolla Style Tiles DashboardV2 Dashboard

With the ever-increasing adoption of our White Label bank transfer API, we understood the need to build a dashboard that accurately reflects the power of that product. Partners need a way to manage the customers they are onboarding, as well as a simple way to view the health of their business from a volume and transactional perspective.

2 - Dwolla Style Tiles DashboardV2 Transactions

Currently we are only targeting those who are current White Label partners to test out the Alpha version of this product. When we’re able to build in the rest of the scoped work, as well as incorporate the feedback from our test partners, we look forward to a broader release.

5 - Dwolla Style Tiles DashboardV2 Customers

Interested in seeing what our White Label API can do for you and your platform? Fill out the form below to contact an integration specialist about the payments flow and user experience you’d like to support.

Get started with your own integration

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.

NEW Upcoming Webinar: An introduction to Dwolla OAuth and API v2

We’ve made some important investments in the Dwolla platform over the past year. From introducing a new developer portal to releasing a new version of our API (what we’re calling API v2), our goal has been to design a more intuitive developer experience.

To better understand the role of OAuth in API v2, such as how it relates to our improved webhooks as well as how it functions with Dwolla White Label, we’d love to invite you to register for our upcoming webinar: An introduction to OAuth and API v2.

Join us Thursday, June 2nd at 11am CT for a FREE 30-minute webinar, “An introduction to OAuth and API v2.”

Sign up Now: An introduction to Dwolla OAuth and API v2


If you’re considering a Dwolla payments integration or have developers that would like to get more familiar with Dwolla’s API, this webinar is perfect for you. Sign up!

What we’ll cover:

  • Basics of OAuth: We’ll explain the overarching principles of Dwolla OAuth and dive into how it’s used in API v2, including various integration options and how access tokens are used. This first section will also walk through a couple OAuth demos and examples.
  • OAuth Best Practices: Our team will walk you through best practices when implementing our bank transfer API, from how to optimize your integration to debugging and error handling.
  • Q&A: As with any good webinar, we’ll leave time at the end so our developers can address any questions that may come up.

You should attend if…

  • You’re a product manager making a decision on integrating ACH payments
  • You are a developer considering a Dwolla integration
  • You’re already using the Dwolla API and want to build depth of knowledge
  • You have just started exploring our bank transfer API and want to understand more

We look forward to you joining us on Thursday, June 2nd! Register right now.

Custom transaction limits and next day transactions for your users

Get paid more quickly with Dwolla NextDayWe understand that not all businesses are created equal and that each has different needs. Whether it’s faster processing times or higher transaction limits, we are here to help you design a payment solution tailored to your business.

For approved partners, as part of a paid white label solution, Dwolla can enable those sending you funds to send up to a custom amount for each transaction and/or have those transactions process the next business day.

This allows users sending to an approved partner to bypass Dwolla’s $5,000 per transaction limit for personal accounts and $10,000 limit for business or nonprofit accounts. This also speeds up transfer times for transactions destined for an approved partner’s Dwolla account to  one business day, instead of the standard 3-4 business day bank transfer processing time.

Partners that benefit from raising the per transaction limit on transactions destined for their account are those that need to regularly move large sums of money, such as investment platforms facilitating transfers from investors to development projects.

Partners that benefit from increasing the standard bank transfer processing times of their users are those that frequently receive many payments, such as property management platforms receiving transfers from tenants each month.

If your platform facilitates high dollar or a large volume of bank transfers, you need a payment platform that doesn’t hinder, but supports the way your business operates. Contact an integration specialist today.

Get started with your own integration

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.

FiSync and the Federal Reserve’s role in faster payments

The last week marks some memorable things:

  • 1 million accounts will have been created through the Dwolla platform
  • Billions of dollars will flow through Dwolla this year
  • 30% month over month revenue growth for nearly a year

Frankly, the third is what I’m most proud of. Releasing our white label products has been a great accelerant for our business and our customers’ businesses. Our focus has been to provide companies and organizations with an API to help move money more easily and get their new products to market faster.

This work, and all of the work that precedes it, has given us the opportunity  to contribute a detailed proposal (it’s 164 pages) to the Federal Reserve’s Faster Payment Task Force.

Advising on a better payment system

Last year, the Fed called on the industry to get its act together and join the rest of the world by creating an improved payment system for the United States. Over 500 stakeholders, payment experts, consumer groups, and regulators raised their hands and the Faster and Secure Payment Task Forces were formed. With the Fed’s help, the industry has created an effectiveness criteria and process to assess new payment systems—this is what Dwolla submitted to last Friday. A better payment system is also what we’ve always cared about building.

Why we choose to contribute

The industry is in a much different spot than it was 4 years, 2 years ago, even 6 months ago. The Task Force’s submission process hopes to help drive a kind of singularity in payments, where disparate innovations, ideas, and motivations converge to provide a new platform for money movement in the United States. When the Task Forces releases their final report early next year, they will have helped create a new market virtually overnight.

dwolla fisync federal reserve faster paymentsOur submission lays out some straightforward ideas for a faster payment system in the U.S. We know how this works because we already built one. It’s called FiSync and many of you may have already used it. Our submission reveals a lot about how FiSync works today and how it could work tomorrow inside an improved national payment system. I’m particularly excited about the path it paves for financial institutions to enjoy the type of platform growth we’ve seen over the years.

FiSync is a great technology. It assures real-time availability of good funds 24/7/365 to end users and is a tremendous leap forward in speed and security over today’s bank transfer system. Building it allowed us a very useful role in the payments world and forwarded an agenda we care about most: building the ideal way to move money.

Still the real-time payments landscape hasn’t accelerated like we thought. Maybe it’s our tech-centrism, but, we/I thought that if we built the best technology everyone would just use what we built. Instead of hoarding a technology that may or may not be relevant tomorrow, we believe sharing our ideas through the proposal will bring about a market for it to thrive. The more we listen and collaborate, the sooner everyone gets faster and more secure payments.

The thing about innovation is that it tends to occur and reoccur in the places that are built to nurture it. It’s time we hand off and share this innovation with the Task Forces in hopes that it accelerates how fast the market delivers faster payments at scale. We’re appreciative of the Fed for giving us the opportunity to help and the forum in which to do so.

For the time being, we’ve made sure our branded products at Dwolla.com and our white label APIs are ready for additional faster payment connections. So as new systems come online everything just gets faster without requiring those building on Dwolla to change a thing.

My final thought

One of the most exciting days in this company was getting FiSync to work for the first time. I wasn’t convinced originally I was looking at a production system until it was redone a few times and I took the time to log into my Veridian account. This was the first time we actually realized the money was moving faster than the website would load.

That feeling is something I’ll never forget. Equal parts fear and excitement but a healthy realization that this is just how it should work. Payments should be this fast and we think this step is the best way to get faster payments to everyone.

I thought, on a day like today, I’d be celebrating a million accounts and the billions of dollars customers are moving  through Dwolla, but in reality I’m just appreciative of the opportunity and am hopeful that all of this gets us one step closer to the ideal way to move money.

If you’d like to learn more, check out a couple links about Dwolla’s FiSync, the state of real-time, and the Fed’s Faster Payment Task Force:


Common White Label Bank Transfer Integration Questions

1 . What parts of Dwolla do my users need to interact with?

For most of your users, we will require that they accept Dwolla’s terms of service and privacy policy when they create a customer record. However, since your customers will create their records within your interface, you can do this in a few ways. The Dwolla TOS and privacy policy language can be accepted in a separate flow or in a combined flow with your own terms of service when they are completing record creation.

Exception: White Label Receive-Only Customers

Customer records created in a receive-only capacity (they will never need to send payments), will not be required to agree to Dwolla’s terms of service or privacy policy, but you will need to add a few lines of Dwolla-provided language into your TOS to give us authorization to originate payments on their behalf.

2. If my user has a Dwolla account, does that affect my WL integration?

If you have users that already have pre-existing Dwolla accounts, they will not be affected when becoming White Label users of your application. We have built our White Label solution in a way that keeps partner integrations and their corresponding ecosystems separate. However, if you are a current Dwolla partner with a pre-existing user base built on Dwolla, we have a way for you to programmatically transition customers over to your White Label application.

3. Do I have to send emails to my customers when I facilitate payments?

In most cases, we require that you send emails to your users in regards to their payment status. For users that are verifying their financial institutions using our micro-deposit or instant account verification software, as well as those that will be sending funds in your system, we require you to put in place email communications that satisfy Reg E and other regulatory requirements. Sending these emails is not only legally required but also an essential part of providing quality customer service and establishing valuable touch-points with your customer. Design the tone, look and feel of your emails in a way that accurately reflects your brand, while leveraging our webhooks to send these communications automatically.

4. What kind of reporting do I get?

We have an extensive series of webhooks that you can utilize to pull your own custom reports. We are actively in development of a dashboard for White Label partners in which reporting on customers and transactions will be displayed, so stay tuned.

5. What kind of information do I need to collect from customers?

For customers that will be sending funds:
At a minimum, you will need to collect the customer’s full name and email address. You also will need to verify customers’ bank accounts. We provide both instant account verification (IAV) and a micro-deposit method for verifying bank accounts within our White Label solution.

For customers receiving funds only:
At a minimum, you will need to collect the customer’s full name, email address, and a parameter of “receive-only.” You will connect a bank account associated with that customer by providing both account and routing number.

What if I want to use my own bank verification software?

The Dwolla White Label API is flexible and works easily with other software providers you may already have in place. If you have established your own bank verification software, such as Plaid or Yodlee, you can utilize their services to verify bank accounts instead of implementing our bank verification processes. However, we will ask to see evidence that this software is in place and being utilized appropriately.

Integrate our White Label payment solution right into your own platform’s user experience, and start facilitating bank transfers to, from, or between your users. Contact us today and let us help you design a payment solution that fits your needs.

Get started with your own integration

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.

How we navigated the first weeks at a fintech startup

This is a blog post co-written by two of our newest team members, Chris and Cody. Both with more corporate backgrounds, both now part of the Dwolla Sales team and navigating the startup world. As many who have transitioned to new positions know, there are adjustments—especially when transitioning to fintech. (Also, we’re hiring!)

Rather than tell the story of how we somehow found ourselves working in a culture filled with open office plans and ping pong balls, we decided to take a different spin on it. In the next few paragraphs, we’ll walk you through the biggest surprises found working at a fintech company as explained by letters, F-I-N-T-E-C-H.

Think of this as your ABC’s of jumping in feet first to a world of APIs and compliance terms that you’ve never had to understand before. Here goes nothing…

F is for flexibility

We’re not talking about Yoga here—your daily workflow and schedule will change at a moment’s notice. We’ve learned that you need a willingness to go with the flow and adapt to needs of both internal and external partners, everyone’s on the same team afterall. As part of the business development team, our objective is to help customers understand their needs and offer clearly outlined, tailored solutions. Since every partner has a unique use-case and is in different industries, it’s imperative that we’re flexible in creating a dynamic payments solution specific to its objectives. It’s no longer one size fits all. But the good news is, we only had to learn a simple set of APIs.

I is for independence

From our perspective, the level of independence you have at a fintech startup really stands out. There is a well thought out onboarding strategy put in place to acclimate you to the office, but in the startup world you need to be self-motivated to learn—no one is going to hand you a textbook of every process, because these processes are still taking shape. In an industry that is both fast-paced and demanding, there’s no time to wait around for step-by-step instructions. We’ve learned the value in asking questions of the right people, even if they’re not directly on your team.

N is for nomenclature

The acronyms and industry language can be daunting, especially for someone entering a fintech startup from a wholly different industry. Did you know that the USA PATRIOT ACT is actually an acronym? Google it. That will likely be the longest acronym that you come across, but be prepared to learn not only ones on the tech side like API or PHP, but also on the financial jargon of the business (e.g. KYC, AML, BSA, OFAC). They all matter.  

T is (obviously) for technology

One of the reasons the fintech sector is booming is the potential value-add tech creates for businesses and banks. The “fintech” industry is broad, encompassing a wide range of ideas and use-cases, things from developing more efficient means of moving money to the automation of financial transactions that were once manual. The “tech” in fintech is profound, and hard to wrap your mind around until you get more integrated in the industry.

E is for environment

The startup culture is a huge benefit to working in fintech. We’ve all heard about it, from hoodies and casual office attire to foosball breaks and beer on tap; the culture is a sharp contrast to a corporate environment. There are tradeoffs to any office culture truthfully, but what really sets the tone are the people. The time spent with a team at a fintech company is unique—you’ll work hard and long hours, developers will get angry about problems we can’t begin to understand and things will change profoundly in a matter of days. But it all comes with a healthy dose of joy and passion, the kind of passion and excitement you’ll be hard pressed to find elsewhere. And there are bean bag chairs too.

C is for compliance

Before diving into fintech, we didn’t fully realize the amount of thought and care that goes into any company (much less one dealing with other’s money) to remain compliant. Be warned, you may not find the world of compliance as fascinating as our compliance officer does (and frankly, we’re very thankful for his and his team). However, it was still important for us to spend a ton of time getting familiar with regulatory and compliance requirements early on. We didn’t fully realize the training and detail that we would be asked to understand—we’re not working at a bank…right? Any fintech company is going to be heavily regulated and expected to protect its customers and monitor for fraudulent behavior. Understanding these complexities can be arduous, but we found it best practice to invest the time early on, learning what questions to ask and to get answered. After all, this knowledge base can be quite a value-add for our partners.

H is for here goes nothin’

The first few weeks have been be a blur, but in all the best ways. We’ve been surrounded by team members encouraging us to dig deeper and get uncomfortable. The challenges have been matched by the celebrations—a holiday party on the very first day. Venturing into the world of fintech hasn’t been a cakewalk, but it’s been inspiring to dive into a world that we all operate in every day, and understand the tech powering what we take for granted. Here goes nothin…

Sound like something you’re interested in? Join the team. We’re hiring!

Your brand, our payments platform

This blog post provides insights from our VP of Product, Brent Baker.

Over the past year we’ve made a strategic pivot, transitioning our focus away from a consumer application to a SaaS model designed for businesses who need to access the ACH network and incorporate bank transfers into their own application or service.

This is not a signal that there are major changes in service with dwolla.com. In fact, we continue to invest in this area (sneak-peek) and leverage the application as an operational showcase of our feature rich payments platform. Unlike market alternatives, the Dwolla solution allows businesses to send money to, receive money from, or transfer money between their customers.

Take for example our integration with GOAT, a two-sided marketplace for high-end sneakers.  GOAT had an existing solution for marketplace disbursements that fell short of merchant expectations. The supply side of their business (shoe sellers) grew increasingly unhappy with the existing process for receiving money from the shoes they sold. With our V2 API, GOAT was able to quickly integrate a seamless, white label payouts solution in under 10 days. Further, customer complaints from its sellers dropped 80%.

GOAT is only one example of what drives the direction of our product, simplify what was unnecessarily complex.

Looking back:

What’s possible with our API today was not possible a year ago. In the summer of 2015, we removed the already low per transaction fee. This allowed us to align revenue with what was truly providing value, a feature rich payments platform. Last fall, we introduced a new version of our API or what we refer to as V2. In addition to a simplified design, we moved away from a Dwolla branded experience, allowing partners to customize the end-user experience for their customers. It’s the Dwolla platform that drives the payment—it’s your brand that drives the experience.

Getting to this point required asking hard questions of our existing product and its position in the market. It also required that we take the next step as a maturing business and no longer apply the “start-up” label as a backstop to decision making. This strategic shift was about building a lasting business and we were fortunate to have a solid foundation to build upon.

Getting out of the way:

We believe that accessing the ACH network was unnecessarily complex. In addressing these complexities, we engaged with existing customers to truly understand the friction within the existing offering, understand where we fell short of expectations and get insight into what more was needed to compete in the market.

What we found was that in order to provide the ideal end-to-end experience, the payments aspect needed to move into the background and become a function of the service. As a part of this, we (Dwolla) needed to fade to the background.

This input and perspective shaped our Dwolla White Label service. Now our partners enjoy the benefits of branding their own payments experience, without needing to build it from the ground up (just making it look like they did).

Why? Empowering businesses to bring value:

By providing straightforward API documentation and dedicated developer support, businesses can go to market in as much or as little time as they desire—you set the pace and we’ll get you through the finish line.

It’s widely agreed upon that integrating a white label solution may prove easier and smarter than building your own version of a SaaS product. That holds especially true when dealing in payments. Building your own ACH solution calls for bank partnerships and an increased understanding of compliance.

We’ve spent the better half of the last decade boiling down a heavily regulated and complex payment process into a simple-to-use API, one that you can get started with immediately. If you don’t have time to reinvent the wheel, focus all your energy on breaking new ground in the finance / property management / e-commerce industry. We’ll help you manage the payment process in the background.

We are never done:

This past year’s pivot has brought a great deal of change for Dwolla—change for any organization is hard and we are fortunate to have the team and culture that does not shy away from big challenges. As we move forward, our team will deliver new functionality (rather than shiny new features) to continue to drive the value of a full-stack payment solution.

Get started with your own integration

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.

Watch our latest webinar, upgrading to Dwolla White Label

Posted in Blog, Knowledge Base, Product Updates on April 19th, 2016

If you’ve ever considered taking steps to improve customer experience, you’ve likely thought about what the payments flow feels like. You want users to seamlessly glide through registration steps, attach a funding source, and complete setup as easily as possible.

In the webinar below, we talk you through the differences between your current Dwolla-branded integration and offer up solutions using our White Label product to power payments. Our team of experts explains the value of a white label integration, the technical aspects and benefits of our new API, and introduce you to a migration tool for getting customers on-boarded in the most seamless way possible.

Whether you’re working with pay-ins, payouts, or sending or receiving funds, Dwolla White Label can work for you. We’ll help you learn how in the webinar below:

When we hosted this live session, we received some great questions from attendees. Here’s an outline of those questions and their corresponding answers to get you on the right track. For more information, reach out to an integration specialist right now.

How long does a typical integration take?

It depends on the integration you’re doing and the level of complexity. Spending time in the sandbox before going into a contract can speed things up. We’ve had partners up and running in as little as 10 days while some have taken 1-2 months based on their needs. Basically, Dwolla’s support is here to help you understand your time frame and get you going by your target launch date.

What level of technical support would a partner get?

Dwolla has various packages, each with varying technical support. In our co-branded, premium solution you get email access to our team while our white label package comes with more direct contact with the developer relations team—direct chat, real-time answers, and the option to hop on a call for a truly white glove experience.

Can you clarify the options for speeding up payments from 3-4 business days?

As part of a package, we offer a feature called Dwolla Next Day which speeds up standard ACH transfer time from 3-4 business days, and cuts that wait time to 1-2 business days. With White Label, subject to approval by Dwolla, you can enable Next Day for your entire application.

If my user has a Dwolla Account, does that affect my White Label integration?

We made the White Label product in its own “silo”, so no, this would not affect your integration. Your user’s Dwolla account exists entirely independently from a White Label account—transactions made in a white label setting won’t appear on a Dwolla account.

Additionally, you can programmatically transition a customer’s existing account data to a new White Label integration. So if you’ve been using a co-branded Dwolla integration, you can get customers on-boarded with White Label in a less invasive way.  

What kind of information do I need to collect from my customers?
Required information collected varies based on your payment needs and customer account types. We will help you determine which account types best suit your platform’s needs when you contact us.  

Get started with your own integration

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.

©2018 TransSwipe


Warning: Unknown: open(/home/content/30/7423630/tmp/sess_ehcvennl2kgcnje0mnokpsqts4, 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