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

TransSwipe - Merchant Services and Credit Card Processing

Archive for the ‘New Stuff’ 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

Facilitator fees are now free to use

Facilitator Fee

In June 2015 Dwolla rolled out new pricing. We removed transaction fees and started offering value added features and controls to our business clients.

In these new packages we focus on making the banking system, and largely ach transfers, easier for developers and businesses to use.

When our new pricing was introduced we bucketed some older functionality and some new functionality. As a company, we made 1 decision in that process that we’d like to apologize for and make a change to.

The facilitator fee was moved into the $1500+ package as a paid feature and today we’re making it free again. While I could go into the rationale behind the original decision, it doesn’t matter and it just needs to change.

What matters now is making a fix and making sure budding developers, who are getting companies off the ground, can make use of the feature.

The facilitator fee does a few things well:

  • It allows developers to build fees into their applications.
  • It allows developers to charge a fixed fee or a percentage fee for any transaction passing through their application.
  • It allows developers to build software that leverages ACH transfers, Dwolla balance transfers, credit transfers, and anything else someone could use on the Dwolla platform to move money and charge an appropriate fee.

Fees might sound bad but a tremendous number of non-payment companies charge small fees to cover operational costs or as a part of the service they provide. Many times it’s not charged to the end user.

Here are a few places we’ve seen facilitator fees used successfully:

  • Some organizations have small service charges as a part of transactions. $2 for example on each transaction keeps their technical team staffed and kids getting lunch cards loaded on time.
  • Software developers building software for third-party companies can actually build their fee into each transaction rather than charging upfront. This helps more companies get to market without loaded up-front costs.
  • Software marketplaces where the marketplace may take 10% of the original purchase price for a service ordered. This has become more and more common. We help the marketplace split the payment as the money moves.

There are some other key benefits for businesses operationally with this structure:

  • When your software application takes a facilitator fee, your company account only receives the fee and you can route the rest of the money to the person receiving the transaction. This happens regardless of whether or not it’s a bank transfer, balance transfer or credit transfer.
  • When you only receive the fee and the other party gets the rest of the money directly, that means you’re never holding your customer’s money for the purpose of transmitting it to another party. That’s a positive thing!

In closing, we put Facilitator Fees into a package when it shouldn’t have been. This is a feature that wants to be free—you want it to be free and we’ve heard you loud and clear.

Go build something great with Facilitator Fees.

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

 

Easily export and upload transaction history into QuickBooks

About nine months ago I made a move from managing the Community Experience team over to the product side of the house. My regular engagement with customers in Community Experience has provided perspective in my new role—I have a better sense of what our users want.

One frequent request we’d receive from our business customers was for Dwolla to implement some type of QuickBooks integration. Today I’m happy to announce that we took a major step forward, allowing users to get Dwolla transactions into QuickBooks more easily. Now, a Dwolla user can download a transaction summary as an .iif file which can be uploaded directly into the QuickBooks software.  

While we were at it, the team also made improvements to how customers retrieve historical transaction data. Customers can now sort transactions for any 90-day date range and based on activity type, instead of being limited to a given month.

Need to look back several months or account for mass payments? Easy—just alter the input fields to your specification.

Dwolla Transaction Summary

Our help article can answer more in-depth questions about the actual download process.

We hope that these changes make it that much easier to get insight into transaction history. However, we understand improvements can always be made, so please send any feedback to me at ian@dwolla.com on these specific changes—or any others you would like to see in the future.

Explore Dwolla other features

 

Now pay friends with Dwolla Credit

Comenity Capital Bank has expanded Dwolla Credit to allow users to instantly send money to friends

credit-blog-post-img

As a Credit user, paying merchants was easy. By applying for a line of Credit with Comenity Capital Bank, you could get instant access to funds to pay for the things that you wanted from the merchants you loved.

Now, you can leverage Credit to pay friends and family. Simply type in an email address, phone number, or eligible business and choose Credit as your funding source.

Credit allows individuals instant access to funds, bypassing the traditional 3 to 4 business day wait time associated with bank-funded transfers into your Dwolla account. Simply use what you need, and pay off your balance by the payment due date on your monthly billing statement.

There are no activation or transaction fee associated with using Credit to pay friends and family. Send up to $500 in a single transfer to another Dwolla user or email address, with a $3,000 monthly limit. Simply pay for your Credit transactions by your payment due date to avoid interest and fees.

Pure and simple it’s card-less, interchange-less credit the way that you want it. Forget leaving behind card data, it’s just the internet and payments working the way they should.

Apply for credit now

How do I utilize Credit as a business account?

At this time, businesses cannot send Credit funded payments. To know if your business is able to accept Credit, inquire at support@dwolla.com.

Businesses wanting to access faster transaction clearing times can contact sales@dwolla.com to get started with a package that fits their needs.

Introducing Dwolla white label (for payouts)

Dwolla White Label DescriptionComplex regulations, banking relationships, compliance requirements, and security precautions are just a few of the 1,000 cuts facing businesses and platforms attempting to build an infrastructure to access the U.S. payment system.

So we thought, why not use our infrastructure?

We’ve moved billions under our brand, now it’s your turn.

white-label-icon-orange-150x150The new white label APIs will leverage Dwolla’s existing infrastructure—our fraud analysis, bank partnerships, real-time fraud analysis, communication protocols and more—while maintaining your brand’s look, feel, and name on end-user interactions. This functionality will provide platforms a powerful, flexible, and custom ACH infrastructure at a fraction of the cost and time.

Four endpoints, one powerful ACH payout solution

Today’s release allows platforms to send ACH payments without requiring the collection of new information from existing customers—simply use the data you already have. It’s a perfect solution for payouts.

1. Create a customer record 

2. Attach a funding source to a customer record

3. Create a transaction to the customer record above

4. Check transfer status

Dwolla offers a range of webhook subscriptions, allowing you to check the status of an individual payment and initiate automated actions, like custom email notifications

How to get it

As part of our Custom Package, there are no individual transaction fees or percentages—regardless of how many times you, your business, or your application transfers money. If you’re a developer and want to see how it works in a test environment, or if you’re a business looking to learn more, click on the button below.

Learn more about white label

 

Inside the Mind of Dwolla’s Lead Visual Designer

ben-frank-600x300

On June 2, 2015, we removed our 25¢ transaction fee. Also on that date, we showcased a brand new look and feel to the Dwolla site, one that complimented our focus on providing businesses and financial institutions with a powerful platform and API that they could use to power their payments infrastructure.

I chatted with Jeremiah Wingett, Dwolla’s Lead Visual Designer, on the inspiration behind the choices he made during the redesign.

Can you first describe your role at Dwolla?

My job is to maintain the look and feel of the Dwolla brand while ensuring the company’s visual standards are carried across all properties to the highest quality. I work alongside our user experience designer, developers, copywriters, and product managers to design and develop our web and mobile applications, as well as collaborate with the marketing team to design both digital and printed materials.

What were some of the biggest challenges you faced while redesigning Dwolla.com?

As long as I’ve been at Dwolla, it’s been a challenge to visually represent our technical products and features. Features like MassPay, OAuth, and Facilitator Fees are difficult to translate into imagery. Photos don’t typically work well. Simple icons are usually too abstract and don’t draw a literal enough connection. Product screenshots get outdated quickly. I’ve found that illustrations are best to represent complex concepts like these. I did a lot of experimentation and ultimately ended up with an illustration style that is minimal yet has distinct detail and is also flexible enough to work well on light and dark backgrounds.

What aspect of the new design do you enjoy most? 

The gradients applied over the greenback imagery is a treatment that I think works really well. The combination of intricate dollar bills along with clean typography and simple icons creates this old school meets new school effect. I really like the idea of this physical meets digital concept. Overall, the new color palette and imagery establish a more rich, lush, bold experience and modern vibe.

Can you talk us through the typography and your choices?

The typefaces were selected for their subtle distinctiveness and legibility. Roboto Slab and Open Sans pair really well together. They have similar letter shapes and proportions, yet you can distinguish between their slab and sans-serifs.

Roboto Slab is used minimally and primarily reserved for headlines. Open Sans is mainly used for running body copy and subheads. They are Google fonts, so they are free and easily accessible to anybody in the company, which was also a big factor in my decision.

What key differences are there between Dwolla’s home page then and now?

We’ve pivoted our design focus from individuals and small businesses to be more inclusive of and even focus more on financial institutions and platforms that utilize our API. It not only changes the way that we communicate, but also influences the imagery.

With the removal of the 25¢ transaction fee, we’ve packaged up the powerful payments features and tools we’ve been building over the years for specific companies. These features are now available in simply priced packages—allowing you to pay for what you need (such as white label payments and next day ACH transfers) without having to worry about per transaction fees.

Jeremiah has taken this focus and translated it into impactful design. Check out Jeremiah’s work on dribbble.com.

Introducing Two-Factor Authentication for Dwolla

Security is always top of mind at Dwolla, and it’s something we’ll never stop improving and iterating upon. While Dwolla has always required multiple elements for user sessions, such as email address, password and PIN, we’ve continued to work toward empowering our users with additional security measures.

Today, we’ve released the ability for full Dwolla account holders to enable two-factor authentication (2FA) on their accounts. By enabling 2FA, Dwolla members equip themselves with an additional layer of security in account protection.

How do I enable two-factor authentication?

Visit your account settings page within the Dwolla dashboard. You can navigate to this page by clicking on your avatar in the top right hand corner of your dashboard. From your account settings page, choose Security from the menu on the left.

Account Settings Page

You’ll notice the option to enable 2FA on your account security page. Choose to enable and re-enter your password.

Password on Security

When enabling 2FA, you will need to download and open an authenticator app, such as: Google Authenticator (iOS, Android), Duo Mobile (iOS, Android), Amazon Virtual MFA (Android), or Authenticator (Windows Phone).

Open your authenticator app of choice, and manually enter the key code or scan the QR code you’ll see on your Dwolla dashboard to generate a six-digit security code within the app.

iphone 2fa screenshot
Enter this six-digit code in step three to enable two-factor authentication on your Dwolla account.

Two Factor Enable

Next time you login to your Dwolla account from any device, you will be prompted to supply a six-digit security code from your authenticator app after you enter your email and password. You can choose to supply this code every time you log in from that device or every 30 days.

Security Code Screen

Why is two-factor authentication important?

Two-factor authentication helps protect your Dwolla account from the loss of credentials (e.g., your password being stolen). With 2FA enabled, a valid session requires something you know (your userID/Password) and something you have (your 2FA Time-based One Time Password). In short, it helps prevent online identity theft as a victim’s password is not enough for a fraudster to compromise an account.

Why use an authenticator app?

Dwolla chose Time-based One Time Password (TOTP) as our method of two-factor authentication given customer feedback and the high security level provided via the TOTP protocol. TOTP is also extremely strong as no transmission of the passcode is ever made as opposed to SMS (text) which, although unlikely, may be intercepted.

Have questions or feedback on this release? Please respond in the comments below, or on the Dwolla discussion board.

A glimpse into what was built at Dwolla’s most recent internal hackathon

At Dwolla, about every quarter, we kick off an internal hackathon where our team of developers build and iterate upon what they find intriguing and interesting. Basically they get a little free time and free reign to dig into something they’re passionate about, be it it a new integration, an improved tool for customer service, or a small bugfix.

Below we’ve outlined a few of the projects that grew from our most recent hackathon this past week. You’re getting a look at projects and hacks Dwolla team members explored on their own—not yet released in the wild, not yet live.

Which are you most intrigued by? Input is encouraged.

Hackathon Winner: Updating the Dwolla Button

Screen Shot 2015-07-30 at 1.32.28 PMCurrently, the Dwolla Button launches users into an offside gateway checkout session. With an updated and improved button, developers are empowered to customize the integration more deeply. This hack provides a more tailored experience, keeping users on the website where they initiate the payment. The button can even be customized to suit the look and feel of the website in which it’s embedded—no longer is it an orange button for all.

Take a look at the button and the improved gateway (keep in mind, these are just prototypes):

Screen Shot 2015-07-30 at 1.27.55 PM

Check out the current Dwolla Button

Smart Dwolla

Send money with Smart Dwolla—an integration that recognizes simple commands like “Send 5 dollars to Darren” and runs them as a payment. This hack creates an intuitive and user-friendly e option for sending funds using Dwolla, and all transactions report right on your usual transaction history. Pretty slick.

Connect your Dwolla account:

Screen Shot 2015-07-30 at 1.53.38 PM

Then enter your payment command:

Screen Shot 2015-07-30 at 1.54.34 PM

Detailed Transaction Statement Summaries

This hack focused on extending our current transaction summaries to include more detailed information for Dwolla users. For example, if you were interested in understanding how much you spent at a specific location for a specific month, the summary would include that (as pictured below). There is a debit and credit summary, with totaled amounts and transaction frequencies.

Take a look:

Screen Shot 2015-07-27 at 4.34.09 PM

Check out the current payment history statement

Updated Hub Pages

We have recently updated the request funds flow to take advantage of our seamless offsite gateway checkout flow. One developer applied the offsite gateway experience to the current Hub page so that users could take advantage of the additional functionality—like Direct Account creation and more.

The updated Hub page:

Screen Shot 2015-07-30 at 1.45.29 PM

Check out the current Hub page

One of our core values at Dwolla is: we are all inventors, creators and believers—something that resonates in the spirit of the hackathon. It’s why it’s part of our culture and development cycle, the freedom to create, invent and share has continuously helped us refine our current internal tools and business payment feature set.

©2017 TransSwipe

 


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