Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subscription::PaymentProfile #143

Open
blakeprudhomme opened this issue Sep 13, 2016 · 0 comments
Open

Subscription::PaymentProfile #143

blakeprudhomme opened this issue Sep 13, 2016 · 0 comments

Comments

@blakeprudhomme
Copy link
Contributor

blakeprudhomme commented Sep 13, 2016

I have some use cases where one customer has many subscriptions and wants to replace the existing credit cards with one card. We'd like to be able to handle this internally so the customer does not have to enter new card info 30 times.

I received these instructions from support:

Below I have listed the steps for the best method of updating the payment profile information across multiple subscriptions, as well as attached the relevant API documentation:

  1. Create a new payment profile for each of the subscriptions, using the vault_token​ information of the newly updated card. https://docs.chargify.com/api-payment-profiles#create.
  2. Change the payment profiles, as to make the newly created payment profile the active one on each subscription. https://docs.chargify.com/api-subscriptions#change-default-payment-profile.

Ideally I would like to be able to:

  • Look up the PaymentProfile by the customer_id with the new card
  • Then create a new payment_profile for each subscription based on that result
  • Then make that newly created payment_profile the default payment_profile for the subscription
  • Related to Deleting Chargify::Subscription::PaymentProfile #124, Deleting the old payment_profile would also be useful here

If any of this is supported in the gem now or there is a better way to do this, please point me in the right direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant