5 ms·
We use Braintree's "Vault" for card storage and have a custom-built set of methods for handling the rebilling. Like jpallen, I'd like to release our logic as a
by charliepark 16y ago
We use Braintree's "Vault" for card storage and have a custom-built set of methods for handling the rebilling. Like jpallen, I'd like to release our logic as a gem, as it took us longer than it should to hack it together. They offer a rebilling service, but I really want to know how my billing system is working, so that if it breaks somehow, I know what's going on with it.
- steveklabnik 16y ago> I'd like to release our logic as a gem, Good! Do it! It's really easy: http://timeless.judofyr.net/making-ruby-gems http://timeless.judofyr.net/making-ruby-gems Is your stuff built on top of braintree's gem, or did you re-implement all of the actual calls to the API? You might want to check that out, it could simplify your code...
- charliepark 16y agoSorry. Just saw this now. Our code is built on top of their gem. We focused on the rebilling logic, which replicates some of their own vault / rebilling code, which most people here would say was a waste of time / money. (Probably was?) When it comes to billing stuff, though, I really want to know what's going on behind the scenes ... hence ... rolling our own. As we work out the bugs, I'll try to get a gem together. Would love to have people dig into it and make it better.