3 ms·
I heard about this from the team a few weeks ago, and am excited to take it for a test drive with BCC sometime after my development schedule gets less nuts. Ba
by patio11 16y ago
I heard about this from the team a few weeks ago, and am excited to take it for a test drive with BCC sometime after my development schedule gets less nuts.
Basically, instead of doing the traditional "send people off to Paypal to pay" routine, you have a form on your site which posts to a Spreedly server. Spreedly then redirects the user to you. You validate the token (similar to catching someone from an OpenID provider) and, if successful, do whatever was required to effect your purchase.
From the user's experience, it sure looks like they were on your site the entire time, but their payment details only ever touch Spreedly's servers. You interface with Spreedly on the backend to do any sort of charging logic that you want -- subscriptions, one-off charges, weird business logic specific to your application, whatever. (This is the main value add over the regular Spreedly subscriptions thing, which works very well if your subscriptions work exactly like Spreedly subscriptions and, apparently, less well otherwise.)
Since the data never touches your servers, you never need to go through PCI compliance work.
The big win I perceive for my business is that my checkout forms will only ask for name, credit card number, and CCV, hopefully increasing conversions versus Google Checkout / Paypal.
- qeorge 16y agoFriendly reminder: You'll still need your own SSL for your checkout page, even though you're posting to https://spreedly.com https://spreedly.com
- lionheart 16y agoThat's what I thought. I really hope that they make sure and point this out in bold font in all the docs. Right now I don't see a mention of it anywhere and if people start to use this without SSL on their checkout page, there's going to be big trouble.
- ntalbott 16y agoTotally correct, and we need to re-iterate the SSL requirement in a few places. Thanks for pointing that out.
- Poiesis 16y agoCan't you do some degree of enforcement--even a reminder--by checking the referer header? Might not want to rely on it by refusing to process if it's not there, but perhaps making another hoop to jump through to try to make it easier to do it the right way. Like, a different API call for backend transactions that doesn't require a referer. You still have the odd user cloaking it, though.
- bobzimuta 16y agoWhat Spreedly is offering (transparent post to payment processor, redirect back to retailer) is the same as what Braintree is already offering with PCI compliance built in. That said, we're not happy with Braintree since they messed up an account transfer of ours. The biggest point I'd like to make is that it sucks once you've got your customers in a recurring plan (Spreedly, Braintree, PayPal, etc). If you're not storing their card numbers, the attrition rate should you choose to change processors is unknown and possibly greatly damaging.
- ntalbott 16y agoOur philosophy is one of "you own the data". We've done dumps for customers of our Subscriptions product, and we'll gladly do them for Core customers as well. We see this as one of the significant value adds of Core - avoiding lock-in, including lock-in to Core itself.
- jmd 16y agoMake this an option, escrow if requested.
- storborg 16y ago> Since the data never touches your servers, you never need to go through PCI compliance work. Is that actually true? My understanding is that since the HTML form is still served up by your site, you'll still need to go through PCI compliance (although it will be easier with no data stored), since a compromise of your server would compromise card data.
- bradleyjoyce 16y agoFrom the email they sent out to current spreedly customers: "while you can already do this with our Subscriptions Payments API, doing so places the burden of PCI compliance on your shoulders. Core keeps the PCI burden on our side and allows you to focus on growing your business." not sure exactly how the specifics of this will work...
- ntalbott 16y agoOur understanding after talking to multiple QSA's about the transparent redirect is that it allows the merchant to legitimately claim that they do not "store, process, or transmit" credit card data, which means they only have to fill out SAQ-A. And trust me, you definitely want to fill out SAQ-A.