| Age | Commit message (Collapse) | Author |
|---|
|
Also renamed help to support so it's harder to confuse it with documentation
|
|
authorize_admin -> require_admin
also add require_token which will ensure token has been used for auth.
|
|
Conflicts:
billing/config/locales/en.yml
|
|
|
|
subscription's balance.
|
|
pastdue subscription, as then admins won't be able to search for them.
|
|
should prevent one from adding a new subscription.
|
|
customer in any way.
|
|
|
|
There might not have been any transactions. Fixes the functional test
|
|
|
|
|
|
|
|
user variable, due to complication that an admin might be accessing data for another user.
|
|
edit for other users.
|
|
|
|
customer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Based on:
https://github.com/bvsatyaram/braintree_ruby_examples/commit/00f4852af60f0b1aae188fb11a9d5d06780d1539
|
|
|
|
|
|
of their transactions.
|
|
all the user's subscriptions.
|
|
|
|
|
|
for customers.
|
|
|
|
|
|
|
|
|
|
have multiple subscriptions at a time or not.
|
|
http://stackoverflow.com/questions/15910980/retrieving-a-braintree-customers-subscriptions
|
|
slow. Posted stackoverflow question as not clear if there is more efficient way to get this information via braintree API.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
change for admins.)
|
|
payments from authenticated users will be as a Braintree Customer stored in the braintree vault.
|
|
|
|
redirect API based from https://github.com/braintree/braintree_ruby_examples/tree/master/rails3_tr_checkout (very little changes were required)
|
