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

TransSwipe - Merchant Services and Credit Card Processing

Archive for the ‘Integrations’ Category

On-demand Bank Transfers, made easy

on-demand-bank-transfer

In 2011 we released an OAuth API that made it easy for developers to request transfer permissions from their customers with our Dwolla-branded platform.

Today we’re making the ability to bill your customer later available for our Dwolla White Label customers in our v2 API.

It’s called On-Demand Bank Transfers.

Developers using our white label APIs can enable their payers to authorize transfers for variable amounts from their bank account using ACH at a later point in time for products or services delivered. It’s one simple additional step—a quick authorization from the customer when they instantly verify a bank account. This is great for companies like:

  • Cloud computing services. Fees can be different every month, requiring ongoing authorization so a customer can easily pay for a service, and the company can easily bill for the service.
  • Utilities. A water company bill is rarely the same each month. Same with electrical, and gas. The amount collected at the end of each month is usage-based, or metered.
  • Ride sharing or asset sharing platforms. The amount a customer is charged for a ride across town depends on a variety of factors. We make it easy for sharing companies to bill their customers, while reducing the hassle for the end customer on each trip.
  • B2B services that bill on a variable basis. Some orders may require a bank transfer on NET terms and others may be fulfilled once the goods are delivered. Either way, both should be possible.

The instant bank verification and on-demand authorization occur with Dwolla.js to make it incredibly easy to add to your software. It adds an extra step to the bank transfer process when verifying the bank to acquire the permission for the account holder.

On-demand payments from Dwolla

Once you have collected all of the authorizations required for a bank transfer, including the additional authorization from the end user for on-demand bank transfers, your software application kicks off a transaction that looks like this whenever the customer needs to be billed:

{
    "_links": {
        "source": {
            "href": "https://api-uat.dwolla.com/funding-sources/5cfcdc41-10f6-4a45-b11d-7ac89893d985"
        },
        "destination": {
            "href": "https://api-uat.dwolla.com/customers/C7F300C0-F1EF-4151-9BBE-005005AC3747"
        }
    },
    "amount": {
        "currency": "USD",
        "value": "225.00"
    },
    "metadata": {
        "customerId": "8675309",
        "notes": "Payment for January 2016"
    }
}

As usual, there are no per transaction fees for either party in the transaction, and with our white label services your brand is front and center. If you’re a developer and have more questions, head to our API Support discussion board and post your questions. Our engineering team regularly reads and responds on the board.

The cost and complexity to make bank transfers better isn’t unknown and it affects new fintech companies, large established business, and even big VC’s… We all have the same problem.

We didn’t either and that’s why our team has spent the last 5 years focused on bank transfers. It’s why we feel on demand bank transfers are so incredibly valuable for our customers.

There is a better way and we’re excited to be a part of building the future making bank transfers easier for businesses and developers.

Contact us to enable for your application

5 Things you may not know about Dwolla’s ACH API

5 things blog post

As we develop our partnerships, we’re seeing exciting new ways that our ACH API is being put to use. With that, we wanted to share some items that may not seem obvious—read on to learn 5 things you may not know about Dwolla.

Did you know…You can build account-to-account transfers into your consumer application with Dwolla

The fintech revolution is here, look left and right and you’ll see new applications and platforms enabling smarter use of money, be it for investment, savings or simply paying back friends. When Dwolla was first developed we focused on putting our mobile app in the hands of users to pay their favorite businesses. Things have changed.

Today, we’ve realized the value of our API is in what others can build with Dwolla powering ACH transfers.

For example, fintech startup, Sweep needed a solution to allow its application users to move money between two bank accounts. They integrated Dwolla into their application. Now, whether a user wants to move funds from Bank of America to Wells Fargo or from Wells Fargo to a Chase bank account, they can. Better yet, Sweep will let you do this as often as possible since there are no per-transaction fees.

Summary: If you’re building an application, Dwolla’s API can enable a peer-to-peer funds transfer function between various bank accounts.

Did you know…Dwolla plays well with other payments technologies and APIs

If there’s one thing Dwolla does well, it’s bank (ACH) transfers. Programmatically or electronically bringing traditional ACH processing into the 21st century is our jam. Where do bank transfers perform best? Often times in investment platforms  or paying out vendors or contractors that fuel your marketplace or on-demand service model.

We don’t mind if you use other payment vendors to accept credit or debit card payments. We’ve partnered with a number of large marketplaces that use Dwolla exclusively for paying out their vendors, while using other payments APIs on the front end to process credit cards.

Did you know…Dwolla offers a  highly customizable White Label integration

Another value-add to partners is the extent to which you can customize a White Label payments integration. Dwolla can help you facilitate bank transfers via the ACH network for your customer through your own platform. Imagine a payments experience that feels and looks just like your website or portal—we’ve got that.

With our customizable stylesheet, one partner’s integration can look vastly different from the next. Change the fonts, alter the button colors, it’s all up to you.  We’ve built a demo of our dynamic bank verification experience so you can play around with it.

Did you know…We are compatible with mobile apps and interfaces

Mobile apps appear to be taking over the world. Sure you build a website, but the number of users accessing your application while on their phones is on the rise. Dwolla plays well here, too. Our API works with mobile seamlessly.

Sweep, who we mentioned above, built a fintech mobile application and easily integrated Dwolla to provide a bank transfer functionality. More and more, we’re seeing partners with similar needs, and Dwolla has proven a good fit for their payments.

And for our developers:
Did you know…We have RESTful API which implements the HATEOAS constraint

I repeat, we have a RESTful API which implements the HATEOAS constraint.

What does this mean? We use hypermedia, basically links & link relations, to tell you about all the actions that can be performed on the current resource, allowing you to traverse the API from a single entry point.

The entire API is discoverable starting from the root URI, documentation is not needed!

If you’ve learned something new about Dwolla’s API for bank transfers and want to learn more, reach out to one of our knowledgeable integration specialists.

Send a harmless email

Get to market faster with Dwolla’s bank transfer API

Invest in an integrated payment solution for your platform that allows you to maintain control of the customer experience, while reducing your compliance and processing headaches.

Screen Shot 2015-12-21 at 1.06.22 PM

Retail marketplace Jane and mobile fintech app Sweep.co were faced with a number options when selecting a solution that addressed their unique ACH processing needs. Ultimately each elected to go with Dwolla’s feature rich, easy to integrate API for one overriding reason: time to market. In addition, each placed a premium on controlling the payments experience through Dwolla’s white label service and valued Dwolla’s guidance in managing the compliance requirements. Both Jane and Sweep are able to achieve funds transfers via a trusted partner, allowing them to focus on their core business.

The same rationale applies to anyone who is looking to transfer funds electronically.  Whether you’re looking for a straightforward disbursements solution or a more holistic, end-to-end payments experience—including instant bank verification and managing compliance requirements—Dwolla’s robust payments platform allows you to facilitate payments from, to, or between your customers.

Phase 1 – Funds transfer wrapped inside of 4 endpoints

We took a phased approach to the latest version of our API. The first phase allowed platforms to process bank sourced transfers in a white label capacity, and in many cases, not requiring re-collection of the customer data already on file. It’s a perfect solution for payouts, an integration consisting of only 4 endpoints.

“We’ve seen exponential growth, and Dwolla has handled disbursements for our platform every step of the way.”

Mike McEwan, CEO of Jane

Phase 2 – Customer verification

At the completion of phase 1, moving money was limited to the receipt of funds by a customer—a perfect use case for disbursements. The second phase extended the current, phase 1 customer onboarding flow. Now, with the same #customers endpoint, we were able to provide our partner with an automated identity verification solution, accounting for the CIP data elements required for both customers sending funds and allowing a customer to hold funds.

“Dwolla was able to offer the exact service our customers wanted whereas traditional financial institutions either didn’t understand how to do this or couldn’t move fast enough.” 

Jackson Gates, CEO of Sweep

Phase 3 – Bank verification

The third phase focused on bank account verification. We released Dwolla.js—a powerfully simple integration that partners can leverage to embed an instant account verification process within their platform, or securely collect account and routing numbers. With Dwolla.js, sensitive customer financial data never touches a partner’s servers. All this, in a few lines of code.

We are never done. While we continue to migrate additional functionality over to the white label experience, such as an improved mass payment flow, we ask that you provide feedback and suggestions on the v2 Dwolla API.

Is navigating the complex world of building your own payment platform pushing your launch date back? Let Dwolla help you get off the runway.

Get started now.

Contact and integration specialist

Building tools out of blocks (at Dwolla)

This blog post comes from Devangelist, David Stancu. Check out his work on GitHub or hit him up at Awesome IT

building tools, blocks

Here at Dwolla we are building an innovative way to move money. However, thinking differently poses a challenge: we need to also create unique solutions that are best suited to our mission critical objectives. How can we do this in a time effective manner while still reaching all of our goals? The answer lies in open source software.

API V2 and SDK Support

The API team took a very data-centric approach in their decision to use the Swagger ecosystem. This let our internal engineering team focus on the API’s data and behavior first before forcing them to make considerations with regards to implementation. After they were finished, the Developer Relations team was handed the task of designing end-user SDKs for this version of the API (aka ‘V2’).

Exploring

As the Developer Relations’ engineering lead, I researched the Swagger ecosystem and quickly came across the swagger-codegen project, which would use templates to generate end user SDKs in over 10 languages for any API modeled in accordance to the Swagger Spec. I immediately cloned the project and attempted to generate some SDKs for a few languages popular with Dwolla developers; namely, Ruby, Python, PHP, and Java.

There were a variety of problems with generating SDKs using swagger-codegen. To highlight a few:

  • Generated code often included syntax errors
  • Data in nested containers could not be or was improperly serialized
  • HTTP 201 requests displayed no data to the user
  • Requests that replied with an HTTP 200 and no data would throw exceptions even if the request would complete
  • No implemented OAuth stubs for Ruby or Python

Problems Shouldn’t Discourage

It is easy to see why it may have been more simple for me to just say, “well, this is going to be hell to fix, I’ll just write the SDKs individually myself.” I thought this same thing, but after taking a step back, there was no good reason as to why I couldn’t use the building blocks available to me. The strategy was to review, fix, and improve more than it was to reinvent.

Developers often feel intimidated when they read another person’s code—and even more so when they have to use that code for their own production purposes.

Even very good changes can be scary at first.

Doing two good things at once

As a developer, your problem may feel unique unto yourself, but that does not mean that the problem doesn’t share components with solutions being attempted by others. Simply put, if something is useful for you it may be useful for many. By submitting fixes to the swagger-codegen project I’ve helped not only Dwolla, but the other organizations using this software.

Swagger-CodeGen Quote

For example, OAuth is one of the most popular authorization standards for RESTful services. By adding support to this project for OAuth to certain languages, I enabled that software to help more people than it did before—it’s about community

It’s an interesting time for programmers in the workplace. The ‘open source movement’ has produced a smarter developer; one that is not afraid to look around, ask questions, and share their knowledge. This “intellectual crowdsourcing” is essential to writing robust, stable and well-audited software—and this is what we do at Dwolla every day.

Excited by what we’re talking about? Head over to our developer portal and play around.

Go to the developer portal now

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.

wodtogether-whitebg

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

Bank account verification and transfers in just a few lines of code

dwolla.js-final

By dropping in a few lines of code, you can now power bank account verification and transfers on your platform as a user of Dwolla’s White Label service.

<head>
  <!-- Include dwolla.js on your page -->
  <script src="https://cdn.dwolla.com/1/dwolla.js"></script>
</head>

 

Within seconds, your White Label integration can access Dwolla’s Instant Account Verification process through dwolla.js. Your customers simply select their bank, log in with their bank credentials, link the bank account they’d like to use and they are on their way to quick and easy payments inside your application.

<script type="text/javascript">
$('#start').click(function() {
  var iavToken = '4adF858jPeQ9RnojMHdqSD2KwsvmhO7Ti7cI5woOiBGCpH5krY';
  dwolla.configure('uat');
  //Call function to start/render IAV in the container specified
  dwolla.iav.start('iavContainer', iavToken, function(err, res) {
    console.log('Error: ' + JSON.stringify(err) + ' -- Response: ' + JSON.stringify(res));
  });
});
</script>

 

Not a Dwolla White Label partner? With the release of dwolla.js, you still have the option to securely pass your customer’s account number and routing number to our Funding Sources endpoint without them ever hitting your server. This provides you the peace of mind that your customers’ information is safe while getting set up on your application, and allows you to send payments to that customer.

<script type="text/javascript">
$('form').on('submit', function() {
  dwolla.configure('uat');
  var token = 'Z9BvpNuSrsI7Ke1mcGmTT0EpwW34GSmDaYP09frCpeWdq46JUg';
  var bankInfo = {
    routingNumber: $('routingNumber').val(),
    accountNumber: $('accountNumber').val(),
    type: $('type').val(),
    name: $('name').val()
  }
  //Call function to attach bank account using form values
  dwolla.fundingSources.create(token, bankInfo, callbackHandler);
  return false
})

function callbackHandler(err, res) {
  $div = $('<div />')
  var logValue = {
    error: err,
    response: res
  }
  $div.text(JSON.stringify(logValue))
  console.log(logValue)
  $('#logs').append($div)
}

 

This is a breakthrough for making bank transfers accessible and flexible for businesses and developers everywhere.

Go use it

Interested in building with our Dwolla white label solution? Chat with an integration specialist.

BlueZebra Sports: delivering payouts for college officials

BlueZebra Sports logoIn a single college football game there can be up to eight referees on the field—and that’s just the refs. This number doesn’t account for the other officials and staff that help keep the game running. Now consider college game-day, every Saturday in the fall hundreds of referees, umpires and other officials don their black and white stripes and head to the field.

Managing and coordinating the officials in sports is no easy feat, but software company BlueZebra Sports has built a platform that major collegiate conferences consider their go-to for everything from scheduling to paying employees.

About BlueZebra Sports

If you’re watching a game, most people don’t think about the referees unless a call doesn’t go their way. Refs just show up and do their job, but ensuring this happens is no small task.

BlueZebra has been in the game for over thirteen years, empowering schools of all sizes—from your hometown high school to division 1 universities—to take hold of all things related to managing officials. Its user-friendly platform boasts easy-to-use technology for officials and administrators alike.

With over 4,000 college officials in the system, BlueZebra provides its clients with a holistic solution for managing and paying a less-than-traditional lineup of staff.

The problem they faced:

BlueZebra needed a cost-effective payment integration to ensure referees were paid in a timely, secure and efficient manner. Since collegiate athletic conferences are generally non-profit, BlueZebra needed to find an easy-to-use solution for staff payouts that would land funds directly in their bank account.

Sports officials are independent contractors, and are typically paid directly by the schools or by the conference. We were looking for a way to make payments as easy as possible for officials and for school/conference personnel.”

Bradley Batt, Founder and CEO

Brad BlueZebra Sports headshot

When looking for a payouts provider, BlueZebra needed a partner that could be as flexible and customizable as its software was. Additionally, it needed to offer quick payouts and display information about transactions. Since the platform is often tailored for each client, the payout integration needed to cooperate.

Their solution for payouts:

BlueZebra found an ideal payment partner in Dwolla. With a flexible, open API backed by top-notch developer support, BlueZebra was sending payments through Dwolla within two weeks.

Today, BlueZebra facilitates millions in payouts annually to thousands of college officials using Dwolla’s powerful ACH-based bank transfers.

review-games-screenshot

The process is as follows:

  1. A conference manager logs in to BlueZebra’s customized portal for their given athletic conference.
  2. They head over to the ‘Pay officials’ tab and select a date range.
  3. Based on the date range, they can select the officials they would like to pay.
  4. Payment is processed by Dwolla and the funds are routed to the officials connected banking account.

“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. Finally, Dwolla’s support has been fantastic, both for our officials and for our administrators who manage the payments.“

Jeff Wigal, Founder and CTO

Jeff Wigal head shot blue zebra

BlueZebra’s slick integration makes payouts to staff members simple to follow and painless to get up and running. Now conferences are able to make payments as frequently as needed without concerns of timing or excessive cost, and see information conveniently in one place.

To integrate your own solution for better payouts, let’s get started!

Read out to Learn more, blue

Leveraging bank transfers to power your subscription service

Business 101: it’s more efficient to retain a customer than to work to earn a new one. Give them a seamless payments experience, so they’re excited to stay.

Subscription Blog HEader

Subscription services are becoming the norm. You pay for your music, office tools, movies, clothes, and even food and wine on a monthly basis. Providing subscription services is a wonderful business model—building a loyal and active customer base with each new shipment, feature or content that you release.

For the customer, subscriptions can provide a sense of delight. Every month there’s something new to look forward to—or even better, you’ve come to depend on. Take Netflix—can you imagine a month in which you’d be forced to halt your binge watching of Peaky Blinders, Parks and Rec, and Orange is the New Black?

After you’ve acquired some loyal customers, providing a seamless recurring payment experience is one of the most important things you can do for your subscription services business. You want customers to enter their payment information one time, and not require them to continue to update or re-enter it every month.

This is where Dwolla comes in. With our scheduled payments API, you can set up bank-sourced payments for a time and date in the future. The OAuth scope, Scheduled, allows your users to give your application permission to create, edit, and delete scheduled payments on their behalf.

Check out this example, where we schedule a transaction to send $9.95 to someMerchant@dwolla.com every other week on Mondays.

Screen Shot 2015-11-12 at 3.47.22 PM

Being able to set up a subscription payment with a bank account allows customers to skip the hassle of updating financial information every time a credit card expires or has to be replaced—and helps avoid the pain of having your HBO Go account cancelled when you’re in the middle of a Game of Thrones marathon (yeah, we watch a lot of TV).

What’s more, Dwolla takes security seriously. By utilizing tokenization, we’re able to replace high-value transaction data with a time-based, tokenized message.

Stop losing loyal customers to a fragmented subscription payment experience. Start using Dwolla’s API for ACH payments.

Reach out to get started.

See scheduled payments in action, check out our demo Ruby on Rails app.

How We Did It: Inside Our Developer Portal Redesign

This post is an introduction to a longer piece co-written by Brent Baker, Dwolla’s VP of Product, and Melissa Cooper, Dwolla’s Director of UX. To learn more about the new Dwolla API and the developer portal redesign, read the full post on Medium.

Developer-portal

Last week, I mentioned that we are rolling out a complement to the latest version of the Dwolla API—a deeply integrated developer experience within the entire Dwolla website—and the relaunch of our developer portal is now live. Our new API is the foundation of a revised Dwolla narrative and we knew how important it was to bring the developer experience to the forefront.

The developer portal relaunch effort spanned nearly four months and required a herculean effort led by our Director of UX, Melissa Cooper. Our UX, Design, and Developer Relations teams played major roles in this relaunch, and we’ll peel back the curtain in this post to share our process.

With a redesign project, it can be tempting to throw out everything and start fresh. But when you do this, a lot of insight can be lost. Don’t start with the new—establish a baseline of the known.

Discovery

Our developer relations team constantly interacts with developers on the Dwolla platform, answering questions and gathering feedback. So we had plenty of information about what developers wanted, but our design team still had a lot of questions. Particularly, we wanted to speak with developers who were less familiar with Dwolla, especially those who weren’t actively reaching out. We developed our user research plan very early in our process, conducted in-person and remote interviews, then synthesized and shared our findings.

From this, we gained insight into the needs of less-experienced developers and the expectations of experienced developers. We observed friction points encountered by first-time visitors attempting to complete a lightweight integration from scratch. We also spotted similarities in the ways developers of all experience levels sought information.

In parallel to the user research, we performed an audit of content on our existing developer portal. The extensive audit allowed us to understand what content was applicable to the new version and how developers consumed existing content.

Our third piece of research was to look at best-in-class developer portals that have been rightly praised for their developer documentation like Twilio, Firebase, and Github. We familiarized ourselves with standards that have been set by the industry and reviewed around twenty portals to determine what resonates best with Dwolla’s brand and intent.

To learn more about the process behind the developer portal redesign, read the full post on Medium.

Visit the new developer portal now

 

Marketplace Jane.com uses Dwolla’s API to send payments to merchants

Jane.com Blog Header

Boutique marketplace Jane.com leverages Dwolla’s API to power ACH payments to its booming merchant base

Started only four years ago in founder and CEO Mike McEwan’s home, Jane.com quickly grew from a boutique daily deals marketplace offering just one deal per day, to 50+ team members managing and promoting over 200 deals a day. In the last three years, Jane.com has seen an explosive 18,787% sales growth. This fall, the company was ranked #11 on the Inc. 5000 list, as well as the #1 fastest-growing company in Utah and the #1 fastest-growing retail company in the country.

Built from the ground up, Jane.com is as much a technology company as it is a marketplace for boutique clothing and accessories. Jane.com keeps most business operations in-house, from feature and platform development to marketing campaign creation and execution. However, without the time to build its own payments infrastructure at a pace the market demanded, Jane.com partnered with Dwolla to help facilitate the disbursement process to its rapidly-growing merchant base. Jane.com tapped into Dwolla’s API to integrate a programmatic ACH payout solution that complimented its existing platform.

“We’ve seen exponential growth, from facilitating deals for our growing business customers to managing the increased consumer traffic to our site, and Dwolla has handled disbursements for our platform every step of the way. Not only was their API easy to integrate, but they’ve scaled and innovated alongside Jane.com to offer the powerful and flexible bank transfer solution we need.”


Mike McEwan, CEO of Jane.com

j

As customers purchase goods from the boutiques, payouts to the merchants are automatically queued on the backend, where they are then reviewed and approved by a controller on Jane.com’s team. This light-touch and streamlined disbursement process allows Jane to focus more resources elsewhere in the company.

This week, Jane.com launched a new registration and ACH payouts flow for some of its merchants, leveraging the Dwolla White Label integration. Jane.com can now brand the end-to-end experience, from account creation to payment notifications. This provides a seamless and customizable onboarding experience, and allows Jane.com to service larger partnerships that may have been road-blocked by the previous flow.  

“Dwolla White Label is essential for us to re-open and attract new conversations with larger clients who required a more seamless onboarding experience. With only three endpoints and a webhooks integration, Jane.com was able to build a lightweight ACH solution in 14 days that allowed us to control the experience for our merchants end to end.”

– Mike McEwan, CEO of Jane.com

Have questions about how Dwolla can work with you? Contact us.

reach out now

©2017 TransSwipe

 


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