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

TransSwipe - Merchant Services and Credit Card Processing

Archive for the ‘For Developers’ 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.

Easy User-Onboarding with Dwolla OAuth: 2 Examples

Posted in Blog, Dwolla Flow, For Developers, Knowledge Base, oauth, Shift Payment on April 15th, 2016

We’ve added email to the OAuth scope. This makes it incredibly easy for Dwolla account holders to sign in and sign up for new services by reducing the amount of information you’re asked to re-enter.

Below, we walk through two examples of platforms making it easier to sign up with Dwolla, all within a simple and secure API. One is Discourse, a platform we utilize for hosting conversations between Dwolla customers and our own customer support and technical staff. The other is Shift, who developed a debit card that allows you to spend from your Dwolla balances wherever Visa is accepted.

Here’s what the two mentioned examples look like:


  1. Sign Up

Dwolla Oauth 1

2. Choose Dwolla

Screen Shot 2016-04-07 at 3.50.20 PM

3. Provide Dwolla email address and password, then “Allow” the requested permissions (Note: Email is now a part of this OAuth scope)

Screen Shot 2016-04-07 at 3.50.32 PM (1)

4. One additional click for creating a Discourse account


  1. Connect Dwolla

Screen Shot 2016-04-07 at 3.55.04 PM

2. Log in by Providing your Dwolla email address and password, and “Allow” the requested permissions.

Screen Shot 2016-04-07 at 3.55.18 PM

3. Your email address is pre-filled into the form required to sign up for a Shift card.

Screen Shot 2016-04-07 at 4.17.56 PM

For developers, requesting an email address to help users more quickly sign up / sign into a service requires a simple request of the email scope in the initial OAuth authorization request.

As a user, you can always revoke authorization permissions to any platform that you’ve granted access to your information. Just log into your Dwolla account and changing your App Permissions settings.

If you’re looking to build bank transfers into your platform or application, check out our developer portal or contact an integration specialist by filling out the form below.

View Developer doc

Programmatically transition customers to a white label application

Our white label services have been an ever increasing focus for us as businesses continue to find more and more ways to innovate with it.

As more white label partners come online we’ve heard two things loud and clear:migration-tool-icon-for-blog

  1. Businesses that built their customer base/partner base using Dwolla’s branded solutions and upgraded to white label want to make the transition easy.
  2. Businesses building white label services who want to make it incredibly easy for existing Dwolla users to create accounts on their white label application.

The migration tool solves for this problem in an incredibly straightforward way. As a white label partner, you request access from the Dwolla account holder and an OAuth token is generated. You then create a customer in your white label application with that token. Here is an example:

POST /customers HTTP/1.1
Host: api-uat.dwolla.com
Accept: application/vnd.dwolla.v1.hal+json
Content-Type: application/vnd.dwolla.v1.hal+json
Authorization: Bearer pBA9fVDBEyYZCEsLf/wKehyh1RTpzjUj5KzIRfDi0wKTii7DqY

  "accessToken": "xOWs8wRvsDEylKglN8Mr6FuhABYpssvME5pL9FTFKeEBBEmhtP"

Easy as that. With the account holder’s permission they will be migrated to your white label application as a customer and with a few clicks, they’ll be enjoying the experience you create.

The migration tool is a free addition to any new white label package. If you’d like documentation or would like to get started with the migration, send us a contact below:

Reach out now:

We’ll help you understand how to get going with White Label.


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.

The value of #opensouce, a JotForm and Dwolla integration

Posted in Blog, For Developers, Use Cases on March 16th, 2016

One reason we love having an open API is it encourages unique, new integrations and innovation that we may not have the bandwidth to do ourselves. A great example of this is the latest integration from JotForm—an incredibly popular form building tool.

JotForm is an online form builder that allows you to create registrations, applications, surveys or contact forms and embed them right in your web page. This is an ideal tool for the non-technically gifted, no coding know-how needed—possibly even the easiest online form building tool out there. Better yet, it’s free to use.

Screen Shot 2016-03-08 at 10.32.15 AM

Since first launching nearly 10 years ago, JotForm has beefed up its form builder, adding new functionality and options for users. One of its latest additions is integrating Dwolla.

Using Dwolla with JotForm allows for easy collection of payments via the ACH network. Use the integration to collect a payment right from your online form—great for order forms, payments for clubs or donations—all with no fee per transaction.

About the integration


If you’re considering integrating Dwolla, JotForm is a great example of putting the API to work. Its developer team tapped into the UAT sandbox environment to first build in a test environment, and any questions they had were preemptively answered just by visiting the discuss board. A quick and smooth turnaround, here’s what their integration timeline looked like:

Day 1-3: Learning the API, researching capabilities relevant to our needs
Day 3-4: Write classes, perform initial API tests and prep for launch

Essentially, JotForm launched their integration in just a handful of days, and it’s live now!

JotForm is incredibly versatile, it has users ranging from Fortune 500 companies, including the likes of Uber and Chevron, as well as famous nonprofits and major universities, like the University of Cincinnati and Harvard.

Integrate your own form or get started with a Dwolla integration all your own by visiting the developer documentation.

View the documentation gray

Reduce sign in friction: Adding email to the OAuth scope

Authorizing your Dwolla account to pay for a product or service was the original intent of Dwolla’s v1 API. OAuth made it incredibly smooth, and over the years it’s continually been improved upon.

One of the features we’ve had requests for is giving developers the ability to request an email address as part of the OAuth authorization request. This gives existing Dwolla account holders the ability to easily sign in and sign up for new services, while also reducing the amount of information you have to re-enter—all within a simple and secure API.

Adding email to the OAuth scope with Dwolla

For developers, requesting an email address to help users more quickly sign up/sign into your service requires you to request the email scope in the initial OAuth authorization request.

Remember, if you can grant an application access to your Dwolla information, you can revoke that permission at any time by logging into your account and changing your App Permissions settings.

This change makes it easy for developers to leverage Dwolla’s OAuth integration to sign up or login existing users, allowing them to uniquely identify the user on their platform. It’s a simplified experience, reducing the number of times Dwolla members have to re-enter information.

Explore the API.

Dwolla’s Open Sourced Developer Documentation Portal

Dwolla’s developer docs have gotten pretty darn good. We’ve discovered some really cool things that are working well and wanted to make these best practices available to anyone who might find them useful.

We’ve open sourced three repositories on GitHub today that we hope are helpful to developers building on top of Dwolla’s APIs and make it easier to suggest changes to the docs.

Our Developer Portal

Screen Shot 2016-02-16 at 2.36.53 PM

One of the challenges we’ve had in the past is producing an intuitive experience that isn’t only developer documentation for code. There needed to be a section for getting started guides, how-to’s, SDKs, and more.

The technical documentation typically needs to function a bit differently than other content, so we made that a supporting element to the primary portal.

You can see the live docs here – https://developers.dwolla.com/
You can find the Github repo here –https://github.com/Dwolla/open-source-developer-portal

v1 Documentation

Screen Shot 2016-02-16 at 2.45.12 PM

Powered by Slate, we’ve made a great deal of changes. The v1 documentation is largely focused on our OAuth API for developers building on Dwolla.com’s platform and applications.

You can see the live docs here – https://docs.dwolla.com/
You can find the Github repo here – https://github.com/Dwolla/v1-payment-api

v2 Documentation

Screen Shot 2016-02-16 at 2.46.12 PM

Powered by Slate, we’ve made even more changes to this one to live inside of the primary developer portal. Currently, the v2 documentation is largely focused on white label ACH integrations.

You can see the live docs here – https://docsv2.dwolla.com/
You can find the Github repo here –  https://github.com/Dwolla/v2-ach-api-docs

Have any changes you’d like to see made? Go to our GitHub profile and submit your feedback or pull requests.

For those of you interested in learning more about our ACH API for implementing custom white label integrations, contact an integration specialist or get started in our sandbox environment.

reach out now

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

©2018 TransSwipe


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