#Samwise - Migration

1 messages · Page 1 of 1 (latest)

fresh tulip
wintry cedar
#

"The Stripe migration team can only import or export customer details if accompanied by the payment details. For importing or exporting customer data that does not include payment details, the Customers API can be used. You can also export customer data without the payment details via the Dashboard."

fresh tulip
#

Yeah, if you want to do that you need to use the API.

wintry cedar
#

For context, I am looking to export

stripe_payment_method_id, exp_year, exp_month, name_on_card

As I am trying to integrate multi-cards

#

yeah so back to original question

#

about speed

fresh tulip
#

What does "integrate multi-cards" mean?

wintry cedar
#

sorry, I am currently using a single billing source for all customers ( default source ).

My users have multiple subscriptions, I want allow different cards per subscription.

I need to pull down what payment method information for existing payment methods, so I can then integrate allowing users specify a new card for a subscription

fresh tulip
#

So your goal is to have a single Customer associated with multiple methods of payment?

wintry cedar
#

I wanted to manage what subscription is associated with what payment method without having to query stripe every time I display that data.

#

yeah correct. So a single customer could have 4 subscriptions using 4 different cards.

fresh tulip
#

Okay, and you're using our older APIs and default_source, not Payment Methods?

wintry cedar
#

Defo on an older API - 2018-10-31

Might need some direction here.
But I thought I would have to update the default source on a subscription to a payment_method ?

#

In the newer API, can you just set a subscription to a payment_method ?

#

"You can further specify a subscription’s default_payment_method, or the older default_source, to prioritize which payment method is attempted."

fresh tulip
#

The newer APIs, like Payment Methods, can be used on any API version, so that doesn't matter.

wintry cedar
#

Yes I am 😮

#

I am passing in the stripe card token for source when I setup the customer.

fresh tulip
#

Okay, so you can add multiple Cards to a Customer in Stripe, with a single one set as the default at the Customer level, but you want different defaults for different Subscriptions belonging to the same Customer?

wintry cedar
#

Yeah correct.
Basically all my clients have a single source ( but many subscriptions),.

I am now trying integrate the ability for them to add additional cards to their account, and set that as the payment method to one or many subscriptions.

fresh tulip
wintry cedar
#

yes correct, that is the plan.

What I am trying to do, is bulk download some existing data, so that I can display the current payment source info ( eg name on card, expiry date, last4, ). So I can show this to clients ( without a stripe request) when I list their cards, then also use the payment ID when changing what card is on what subscription ( as I haven't stored the payment_id in the past )

fresh tulip
wintry cedar
#

I will be when I expose the adding card ability. Ideally I wanted to track the subscription & associated payment method on my end after successful updates to stripe.

fresh tulip
#

So that's the API giving you the delay?

wintry cedar
#

yeah correct

#

I had been more concerned about the request speed limit, but now I realise that is not even close to the problem.

#

I was hoping there was an api where I could do a bulk request based on specific fields, passing in specific customer ids or something

fresh tulip
#

No, there's nothing like that.