Works out to about $1,450 in savings if you process $50,000. I hope people don't impulsively go with them just to take advantage of this offer. In fact, you probably don't want this offer to have anything to do with your decision-making on the best processor for your needs. That decision is not easy to undo - and will easily cost you more than the savings.
There's no commitment if you code against Spreedly instead of against Braintree's API. Then, once you save your $1450, you can switch processors if you're so inclined by changing just one token in your code.
Spreedly is a unified API for 58 payment gateways, a gateway-agnostic billing info vault so your customer info isn't trapped in whatever processor you chose at the time they signed up, and can alleviate much of the PCIDSS compliance burden if you choose to point your payment forms to them instead of your own server.
I've been using them for a few years now. If you have a lot of recurring billing, knowing that you own that customer data instead of your processor, and your processor cutting you off without notice (which ALL of them can and have done to customers) won't interrupt your business, is peace of mind Spreedly sells very cheaply.
I'm also a happy user of Spreedly (via their subscriptions product which is now owned by Pin Payments, IIRC) and can verify that Dan's exactly right about how easy swapping out a gateway was. When I moved from Paypal (their I-can't-believe-it-isn't-a-gateway product) to Stripe it was literally 30 seconds of data entry in their admin screen and zero lines of code changed.
Have you ever had to change gateways? They charge 2 cents on top of gateway fees - would it be substantial for you if you went direct to the gateway? I imagine less sales at higher prices it's worth it. Many lower price sales it would be worth it to gateway hop manually cost wise.
Several times. And have lost customers in the process, since any customer info stored at the gateway is lost and getting hundreds of people to re-type their billing info in is a big undertaking and a big pain.
The cost of "hopping gateways" for any SaaS has little to do with the cost of the gateway or the cost of development. It's all about customer retention.
When I left one merchant account provider which had ratcheted up its rates every month for years to the point that continuing with them was absurd, the gateway refused to provide my customer info to me or transfer it to a new provider. It simply wasn't mine to have, in their view. That will never happen again; even if I leave Spreedly, they will give me the info to take with me.
> They charge 2 cents on top of gateway fees
Whether it's a $29/month customer or a $2000/month customer, 2 pennies just doesn't register. Let's say I have 500 customers that get charged each month. That's $10/month in transaction fees from Spreedly. That would buy me... 2 more ad clicks from Google. Or the peace of mind that my business's billing info and cash flow can't disappear overnight.
It says they'll accept a public key from the merchant, which is you; you don't need to find a provider that'll work with the data in whatever format it's in.
Anyone with a merchant account to accept credit cards online already has a relationship with at least a QSA, and is already getting a quarterly attestation of compliance after completing a questionnaire and security scan of their server environment; it's required by PCIDSS and merchant account providers enforce it, typically providing an account with a QSA for a non-optional annual fee and imposing another fee if you fail to remain compliant.
It's just a formality having them forward that attestation to Braintree before they hand you the data dump.
The monthly fee makes it unappealing for small volume customers, and the per-transaction fee makes it unappealing for large volume customers. I'm guessing there's some intermediate range, when you are negotiating the final deal, where it's comforting to have that "flexibility".
Justin from Spreedly here. Dan, thanks for the kind mention! Dan's use case is one of the main driver's we see. We also see most interest from businesses/services that need their own vault as they work across multiple payment gateways. Either a SaaS billing/booking platform or someone working with 3 or 4 different gateway's globally. Single API/Single Vault/No PCI headache. Many of our customers are weighing up PCI L1 for card storage and/or integration to multiple gateways or Spreedly.
In terms of Dan's scenario we had a customer whose primary gateway was unresponsive early Sunday morning which happened to be their biggest day of the week. They brought a Stripe account up in around 5 - 10 minutes and processed 6 figures that day. Not sure how you ROI that against our fees but they were happy!
The 110 number is a truism in payments (in which I work) but I don't actually have a citation! Interesting question I'm going to find where that comes from.
I assume he's referring to the fact that you have to write Braintree-specific code (if you choose not to use Spreedly). And if you later decide to switch gateways, you have to do that again. So unless you're convinced Braintree is viable in the long term, you might lose out on the savings you get now with the time wasted doing a rewrite.
