A white label payment API is an option that more businesses continue to build into their strategies as the volume of cardless, electronic and alternative payment transactions are drastically increasing.

Dwolla’s platform is designed to be API-driven and tailored to allow a business to add additional payment rails—like ACH, Real-Time Payments and Push-to-Debit—to their payment stack while maintaining their own branding and style. Instead of sending users to PayPal or another third-party payment gateway to complete a cardless transaction, a business can use a white label payment API to integrate new payment methods into an application or operation.

One of the primary benefits of “buying” versus “building” a payment solution is that you can get up and running in a fraction of the time.

With Dwolla’s technology, tailor a payment API to help your business navigate the ACH and RTP® networks without having to start from scratch. Integrating with a white label API is ideal for businesses looking to get their solution to market quickly without having to batch Nacha files!

Other advantages of integrating a white label payment API include:

  • Domain Expertise – Your payment services provider is immersed in the payments space that you are looking to enter, and you’ll be able to rely on them for solutions to the most commonly encountered challenges.
  • Reduced Expenses – Building from scratch requires time, talent and infrastructure, as well as a development roadmap. Integrating a rock-solid payment solution can take as little as 30 days!
  • Access the Financial System — A single payment API integration can access different payment networks and transfer speeds—without having to develop relationships with multiple financial institutions.

Before you start building in our sandbox testing environment, read through some questions about the implementation period for a payment API.

View the Dwolla Integration Roadmap

Common Questions About Payment APIs

  • If our platform is facilitating payments between users, who would be responsible for sending payment notifications to my customers?

Dwolla requires you, the Client, to send notifications to your users in regard to their payment status. For users that are verifying their financial institutions using our micro-deposit software, as well as those sending funds in your system, we require you to put in place email communications.

Sending these emails is an essential part of providing quality customer service and establishing valuable touch-points with your customer. We encourage our clients to use the Operational Notifications feature as the default setting for sending these communications.

Start by creating a client access token and use the credentials provided. This concept article includes developer documentation for Operational Notifications.

  • What kind of reporting could we expect?

We have an extensive series of real-time webhooks that you can utilize to pull your own custom reports and a dashboard to display customer or transaction activity. You can also export transaction data to CSV files.

  • What kind of information do I need to collect from end users?

For customers 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.

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

  • What options would we have for bank verification software?

Dwolla’s 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 that meets the requirements of the ACH Network, you can utilize that service to verify bank accounts with approval from Dwolla. However, we will ask to see evidence that this software is in place and being utilized appropriately.

Integrate our white label payment solution into your own platform’s user experience and start facilitating account-to-account payments to, from, or between your users.

 

Contact Us

 
 

Stay Updated