3 ms·

You can still delegate PCI to your payment provider (via tokenization). SafeKiddo[0] just launched using Kill Bill + Braintree. [0] https://www.safekiddo.com/

You can still delegate PCI to your payment provider (via tokenization). SafeKiddo[0] just launched using Kill Bill + Braintree. [0] https://www.safekiddo.com/ https://www.safekiddo.com/

tegansnyder 12y ago
PCI DSS 3.0 will change that
- zrail 12y ago
  Not substantially. You'll need to do minimal, common-sense things on your servers (firewalls, IDS, etc) and certify that you're not storing anything interesting.
jusben1369 12y ago
What did SafeKiddo see in the Kill Bill API's that was lacking in Braintree's own recurring/subscription API's?
- piggity 12y ago
  There are small things - e.g. you can't do weekly / fortnightly billing. Once I discovered that I stopped investigating BT for our primary subscription engine. We just hold the card tokens and use BT to charge the card. It's not ideal, but it does give us more flexibility.
  - jusben1369 12y ago
    Got it. Thanks very much.
- slgeorge 12y ago
  I can see the value of having an OSS solution as an API layer for any start-up that has complex billing needs. A lot of start-ups make the "mistake" [1] of locking themselves into fundamental business services at the start: whether that's a payment provider, finance or CRM system. In my experience it's fine for a while, but you really feel the problems as you start to scale the business. Everything creaks and groans as you grow, and then you have to go back and fix the underlying business processes. Issues in some of these areas are actual company killers. Billing is a classic. Lots of companies fail due to running out of cash, and poor management of subscriptions and billing is often the underlying issue. There's a lot to be said for not getting tied in early on, and making sure the fundamental architecture is right! [1] You can argue it's not a "mistake" as the primary goal is to relentlessly focus on shipping product that customers want.

You can still delegate PCI to your payment provider (via tokenization). SafeKiddo[0] just launched using Kill Bill + Braintree. [0] https://www.safekiddo.com/ https://www.safekiddo.com/

tegansnyder 12y ago

PCI DSS 3.0 will change that

zrail 12y ago
Not substantially. You'll need to do minimal, common-sense things on your servers (firewalls, IDS, etc) and certify that you're not storing anything interesting.

jusben1369 12y ago

What did SafeKiddo see in the Kill Bill API's that was lacking in Braintree's own recurring/subscription API's?

piggity 12y ago
There are small things - e.g. you can't do weekly / fortnightly billing. Once I discovered that I stopped investigating BT for our primary subscription engine. We just hold the card tokens and use BT to charge the card. It's not ideal, but it does give us more flexibility.
- jusben1369 12y ago
  Got it. Thanks very much.
slgeorge 12y ago
I can see the value of having an OSS solution as an API layer for any start-up that has complex billing needs. A lot of start-ups make the "mistake" [1] of locking themselves into fundamental business services at the start: whether that's a payment provider, finance or CRM system. In my experience it's fine for a while, but you really feel the problems as you start to scale the business. Everything creaks and groans as you grow, and then you have to go back and fix the underlying business processes. Issues in some of these areas are actual company killers. Billing is a classic. Lots of companies fail due to running out of cash, and poor management of subscriptions and billing is often the underlying issue. There's a lot to be said for not getting tied in early on, and making sure the fundamental architecture is right! [1] You can argue it's not a "mistake" as the primary goal is to relentlessly focus on shipping product that customers want.