When it comes to a marriage between a service provider and its customers, proposing on the first date is not flattering. Getting to know each other requires short term patience to avoid frozen accounts and terminated relationships.
This is a best practice approach for higher risk companies operating in regulatory intensive (banking) environments. Online gaming, fantasy sports, music, events and other entertainment platforms must have answers to even the most basic questions:
While these questions seem basic to any product manager or CTO, finding the answer can be difficult when in some states a certain activity may be regulated differently, and require different commitments to the users transacting on your platform. Singular regulations exist in some states that can be so nuanced it will require submitting a legal opinion explaining the regulatory status.
As your company considers different service providers, a red warning light should go off if your payment provider hasn’t asked these questions. We call this high risk payment processing, because the platform can be at risk of having accounts frozen or shut down completely if they violate the payment company’s terms of service.
Rather than rush into a marriage with a quick onboarding—try consulting with your service providers. Use this as your playbook to prepare for those conversations about operating in regulatory intensive environments.
High risk payment processing will always apply to certain sectors of the entertainment industry. High risk payment processing is especially prevalent in activities where payments are collected for a service or product which are delivered months later and require a business to demonstrate there’s enough capital to cover losses.
Working with the credit card brands, online gambling and lottery tickets, is prohibited to minimize the risk of running up credit card debt with increasing interest rates. The ACH Network considers these activities to be “high risk” but because the funds are attached to a bank account, there are ways to mitigate against ACH returns—specifically RO1, Insufficient funds.
Whether Dwolla is the payment API you ultimately choose to work with or not, here are a few other best practices to have in place to avoid high risk payment processing.
The caveat is there’s such a fine line between risk and sales—the business needs to protect itself from potential negative events while also growing revenue. It is important to truly understand your business model, ensure illegal activity is not occurring on your platform—whether intentionally by bad actors or unintentionally by not knowing state regulations—and know what issues a BSA AML check could unearth.
Much like with credit cards, ACH bank transfers have the risk of a return (this is a chargeback in the credit card space). If the transaction is claimed as unauthorized, what is your platform doing to make sure the transaction is valid initially?
When the music industry revolved around CDs and vinyl records, payments to artists were much simpler. When the sales stopped, so did the revenue.
With the introduction of streaming services, artists are now paid in perpetuity for their work—even after the artist has passed away. As record labels and music distributors started tracking how much each song is paid per-stream, single line items were tenths of a penny.
RSDL.io acts as a digital wallet for these creative agencies or individual artists, automating the accounting of royalty and residual payments. The platform helps track songs and the percentages of each payment, totally automating the accounting process.
“We bring the accounting piece and more transparency into the splits and recoupments each month and as part of that, a logical step is being able to then do the payments piece—and that’s where we use Dwolla—to provide a cashless capability,” CEO Mike Holmes says. “We’re enabling the user to input the instructions for payments and Dwolla does the rest. We use the same system to validate the distributor as we do with the artist. Then they add the digital wallet as their revenue source to get paid.”
The company made the decision to not be in the flow of funds and not becoming a payment facilitator. Dwolla is the payment facilitator handling the regulated requirements that come from being part of the flow of funds. By embedding the Dwolla API, RSDL.io enables its customers to transact with each other.
The orchestration of these transactions happens within the Dwolla API.
“We didn’t design our app to be a bank,” Holmes says. “We looked at banks that offered APIs into their banking system, but their offerings didn’t have all the features we needed. That’s what made Dwolla attractive.”
We’re transparent about our willingness to help companies change the status quo.
Whether that’s geotracking, enhanced CIP protocols or a combination of what’s been mentioned above, money can move safely and securely if it’s treated as data, protected at all costs and permissioned for use by the consumer.