Spreedly Core, PCI-DSS, Gateway Autonomy and commerce. A Guest Post on our blog • Hacker News Board

Re: Spreedly Core, PCI-DSS, Gateway Autonomy and commerce. A Guest Post on our blog

#11

Post by bcx » Thu, Jun 28, 2012, 4:22 PM UTC

ntalbott wrote: post #9

intel352 wrote: post #2

Cool article. Need screenshots :-)

Agreed, except... we actually don't have a UI to show. The transparent redirect approach that Core takes means that we'd just be showing you our customers' payment pages, which while spiffy, don't really tell you anything about the integration. Which is kind of the point - our goal is to be invisible.

Can we use this with normal spreedly :-) ? I have always been a little unsure of the differences between core and non-core?

(Ben from Olark)

Re: Spreedly Core, PCI-DSS, Gateway Autonomy and commerce. A Guest Post on our blog

#12

Post by ntalbott » Thu, Jun 28, 2012, 4:22 PM UTC

powertower wrote: post #8

My first reaction after going to the parent website ( http://spreedly.com/ ) was that I don't understand what spreedly does exactly or why I would use it (vs. my paypal or 2CO account). I'm guessing that Spreedly offers an API/front-end that 1) stores the credit card info for immediate (and future) billing + subscription purposes, then 2) sends the transaction to my paypal, and 3) offers some type of a billing/subscr…

The data is absolutely transferrable today - we've had multiple customers leverage that transferability to switch (or augment) their gateway with just a configuration change.

Of course, it's not just about data portability; API consistency is a big deal as well. If PayPal (for instance) decides to lock down your account and not let you transact any longer, you don't just have to worry about getting your data out, you are also looking at another whole implementation cycle around a new API. Even if it's just a day of work (and usually it takes longer), that's a day you could've spent on your product instead of mucking around with gateway API's.

There are of course libraries that help make gateway API's more consistent, but as a committer on what is in my opinion one of the best - ActiveMerchant - they only get you so far. For instance, Core gives you transparent redirect on top of any gateway we support. That means lowered PCI compliance requirements and a great experience for your customers, and there isn't a library out there that can do that for you.

Re: Spreedly Core, PCI-DSS, Gateway Autonomy and commerce. A Guest Post on our blog

#13

Post by ntalbott » Thu, Jun 28, 2012, 4:24 PM UTC

bcx wrote: post #11

ntalbott wrote: post #9

Earlier quoted context omitted.

Agreed, except... we actually don't have a UI to show. The transparent redirect approach that Core takes means that we'd just be showing you our customers' payment pages, which while spiffy, don't really tell you anything about the integration. Which is kind of the point - our goal is to be invisible.

Can we use this with normal spreedly :-) ? I have always been a little unsure of the differences between core and non-core? (Ben from Olark)

Today there isn't any integration between our classic Subscriptions product and Core (though we do have some customers using them side by side regardless). It's something we'd very much like to do, but it's not at the top of the list yet.