| Age | Commit message (Collapse) | Author |
|---|
|
pastdue subscription, as then admins won't be able to search for them.
|
|
should prevent one from adding a new subscription.
|
|
|
|
|
|
|
|
|
|
|
|
user variable, due to complication that an admin might be accessing data for another user.
|
|
edit for other users.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
of their transactions.
|
|
all the user's subscriptions.
|
|
|
|
for customers.
|
|
|
|
|
|
|
|
have multiple subscriptions at a time or not.
|
|
slow. Posted stackoverflow question as not clear if there is more efficient way to get this information via braintree API.
|
|
|
|
|
|
|
|
|
|
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)
|
