Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

retire stripe #173

Closed
chadwhitacre opened this issue Jul 21, 2012 · 9 comments · Fixed by #2482
Closed

retire stripe #173

chadwhitacre opened this issue Jul 21, 2012 · 9 comments · Fixed by #2482

Comments

@chadwhitacre
Copy link
Contributor

Once all data is moved over to Balanced, we can retire Stripe.

  • remove stripe_customer_id from participants table
  • take stripe_customer_id out of authentication.py
  • unset STRIPE_*_API_KEY from heroku config

Let's keep the account itself around for a while for historical data?

@joonas
Copy link
Contributor

joonas commented Jan 18, 2013

How's the progress going on this migration?

I assume this is dependent on #174 and #238? I would love to do some pruning :)

@chadwhitacre
Copy link
Contributor Author

One of the stragglers in #238 is not failing, which means that every few weeks we pull $10 in from Stripe. This is annoying and inconvenient and kind of funny. I'd rather leave these tickets open until a) we get around to migrating that user, or b) his credit card expires, than the alternative, c) shut off stripe and lose that $10 every few weeks.

@joonas
Copy link
Contributor

joonas commented Jan 19, 2013

Oh sure, I'm not saying we should shut anyone down necessarily, just thought I'd see what's the status of this since it's been open a while. It's kind of funny, that it's still happening.

I guess there's no harm in keeping this open until something changes.

@olivierlacan
Copy link

@whit537 Unrelated to this issue, but what has been your experience with Stripe in general?

@chadwhitacre
Copy link
Contributor Author

@olivierlacan We used Stripe as our main processor for about three weeks, over a year ago. They asked us to leave because we were violating their terms of service by running a marketplace, though since then they've made progress supporting the marketplace features Gittip needs. In general I've got a high view of their product.

@patcon
Copy link
Contributor

patcon commented Apr 24, 2014

+1

@chadwhitacre
Copy link
Contributor Author

@aljosa Turns out that you're the participant in question here. Due to a mixup when migrating from Stripe to Balanced two years ago, we still have your credit card info vaulted with Stripe instead of at Balanced. You're the only one! Would you be willing to re-enter your credit card info for Gittip? That would enable us to finally retire our Stripe integration.

@aljosa
Copy link
Contributor

aljosa commented Jun 1, 2014

@whit537 it should be ok now.
i've tried to click "Disconnect My Credit Card" before entering data again but that didn't do anything.
Then I've added my card info and it was saved w/o errors.
Let me know if there is anything else I should do.

@chadwhitacre
Copy link
Contributor Author

Thanks @aljosa, you rock! I've confirmed that you're switched over to Balanced now. This ticket is cleared for take-off. Labeling "Ready to Start."

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

Successfully merging a pull request may close this issue.

5 participants