Age | Commit message (Collapse) | Author | |
---|---|---|---|
2013-07-17 | Display of subscription information on a customer's edit page. It is *super* ↵ | jessib | |
slow. Posted stackoverflow question as not clear if there is more efficient way to get this information via braintree API. | |||
2013-07-17 | Some tweaks to optimize number of requests to braintree API. | jessib | |
2013-07-17 | Some refactoring | jessib | |
2013-07-17 | Let users select amount for payments. | jessib | |
2013-07-17 | More working subscriptions. | jessib | |
2013-07-17 | Adding some links, which will be removed. | jessib | |
2013-07-17 | Needs much work, but basic start to recurring payments. | jessib | |
2013-07-17 | One Braintree customer per user, and some permissions checks (will need to ↵ | jessib | |
change for admins.) | |||
2013-07-17 | Unauthenticated users can make single payments (like donations), but ↵ | jessib | |
payments from authenticated users will be as a Braintree Customer stored in the braintree vault. | |||
2013-07-17 | Start to adding customers to braintree vault. | jessib | |
2013-07-17 | Basic functionality for one time transactions using Braintree's transparent ↵ | jessib | |
redirect API based from https://github.com/braintree/braintree_ruby_examples/tree/master/rails3_tr_checkout (very little changes were required) |