-
Notifications
You must be signed in to change notification settings - Fork 308
migrate data from Stripe to Balanced #174
Comments
I've tokenized the cards for Gittip. I have a mapping of stripe ids to cards that have been tokenized but not associated to accounts. We'll (I can do this but you'll need to run it since I don't have your prod DB) need to create a script to run through the list and create an account (or GET it if it exists) and then PUT the card onto the account. After that's done we need to update the account within the gittip DB. I want to encrypt this so I can send it to you. Can you give me a pub key so I can encrypt it for you? |
|
Wrong format for the pub key, run this command (substitute path to private key as needed)
Let me know if I'm being a n00b and can use the key you've given me in some other way. |
Nope, I'm the n00b. 🐭 Maybe this?
|
Thanks, I shot the files + instructions through to your email. |
I'm going to be on vacation this week. I'll be back on Friday, August 10 to run Gittip #10, and will pick up with development the week following. In an emergency please call my cell, +1-412-925-4220. Thanks! |
I have a mapping for this. Punting to next week as I spent my time this AM on #203. |
Here are some characteristics of the mapping:
Tasks:
|
The None last_bill_result is indeed a NULL result from the db. The user has entered credit card info but is not tipping anyone. Working as advertised. :-) |
Of the 5 with no value for balanced_card_uri:
I don't see a rhyme or reason why these five are missing from the mapping. In two cases we'd be leaving money on the table to not have a balanced_card_uri for them. Will take to private email to debug ... |
For billing failures we need to still bring over the new card info into Balanced. However, note that if the user already has a balanced_account_uri we don't want to overwrite that, as it means they have already manually reentered their credit card data with Balanced. |
All these cards are syntacticly valid (card numbers OK pass LUHN check, expiry in the future). The two that have billing failures, these cards aren't valid so I don't see why you'd bring them over. Balanced doesn't support tokenizing declined cards so you'll have to give me a really good reason to do that ;) For the other three, it's not Balanced declining the cards, it's the card processor. |
I've created balanced.Accounts for each of the card_uris and have stored these in the db for the 112 out of 117 records (96%) where we had a card_uri.
Why is the card processor declining the cards, especially for the two that worked last week? |
Here's the script I used for the migration: |
Hey Chad, Can you email me which github users were working last week and are not working this week? I'll check the exact reason on those. On 16/08/2012, at 6:33, Chad Whitacre [email protected] wrote:
|
Done. |
If nothing else happens the worst case scenario at this point is that those five continue to be run on Stripe, and if the three supposedly-working cards (including the never-billed one) fail the next time we bill them with Stripe then we'll know something happened since last time, and we can just abandon all five. |
I've reticketed monitoring the straggling five as #238. Woo-hoo! |
I've kicked this off in email. Target is Thursday, July 26. Once the data is migrated I will need balanced_account_uris to put in Gittip's db. I can probably get these through the Balanced web UI or API?
The text was updated successfully, but these errors were encountered: