3 ms·

+1 The few days you spend on this will save you many thousands of dollars in fees in the years to come. Great ROI. Having said that, I found Authorize.net to

by DougN7 10y ago

+1 The few days you spend on this will save you many thousands of dollars in fees in the years to come. Great ROI. Having said that, I found Authorize.net to be a good way to go. No affiliation, just a happy customer.

dangrossman 10y ago
> I found Authorize.net to be a good way to go Authorize.net is just a payment gateway, an API between you and a merchant account provider. Since just about every API has existing client libraries you can use, they're no better or worse than each other. What makes Authorize.net a bad choice is that you don't own any of the data you store with them. If you keep your customers' billing info in their CIM vault, it's never coming out. They won't give it to you, and they won't transfer it to another account. That means if you ever want to change merchant account providers, or your account gets frozen, you're stuck. You need to re-collect every customer's billing info to continue their subscriptions on another platform, and that usually means a big chunk of your customer base will churn out all at once. This is what using an independent payment vault solves.
- DougN7 10y ago
  That's true. One thing I like about CIM is it's trivially easy for me to be PCI compliant, because that particular sensitive data doesn't hit my server. But you're right - I can't export it.
  - dangrossman 10y ago
    Have they come out with a new integration method? Last time I looked at Authorize.net, all the sensitive data hit your server before you stored it in CIM via an API. You'd need quarterly vulnerability scans, SAQ-C or worse, all that onerous stuff.
    - DougN7 10y ago
      I don't remember what they call it, but basically you pop-up a form that is loaded from their website that gets credit card info, etc, and then posts back to their site. So a credit card number never touches my server. It's very nice.

by DougN7 10y ago

dangrossman 10y ago

> I found Authorize.net to be a good way to go Authorize.net is just a payment gateway, an API between you and a merchant account provider. Since just about every API has existing client libraries you can use, they're no better or worse than each other. What makes Authorize.net a bad choice is that you don't own any of the data you store with them. If you keep your customers' billing info in their CIM vault, it's never coming out. They won't give it to you, and they won't transfer it to another account. That means if you ever want to change merchant account providers, or your account gets frozen, you're stuck. You need to re-collect every customer's billing info to continue their subscriptions on another platform, and that usually means a big chunk of your customer base will churn out all at once. This is what using an independent payment vault solves.

DougN7 10y ago
That's true. One thing I like about CIM is it's trivially easy for me to be PCI compliant, because that particular sensitive data doesn't hit my server. But you're right - I can't export it.
- dangrossman 10y ago
  Have they come out with a new integration method? Last time I looked at Authorize.net, all the sensitive data hit your server before you stored it in CIM via an API. You'd need quarterly vulnerability scans, SAQ-C or worse, all that onerous stuff.
  - DougN7 10y ago
    I don't remember what they call it, but basically you pop-up a form that is loaded from their website that gets credit card info, etc, and then posts back to their site. So a credit card number never touches my server. It's very nice.