#Nelsonct7
frank urchin
dusk tapir
default_source: 'card_1MZvAiCaG9pz7GtYhLNFt9XP',
delinquent: false,
description: null,
discount: null,
invoice_prefix: '1032AD85',
invoice_settings: {
custom_fields: null,
default_payment_method: 'card_1MZvflCaG9pz7GtYKf5QBm6v',
footer: null,
rendering_options: null
},
unreal frigate
default_payment_method. default_source is legacy and please avoid using it if you started use Stripe
dusk tapir
not that, here the default_source is having one card id, and default_payment_method is having another card id
unreal frigate
Okie so probably it's from some legacy flow. We prioritize default_payment_method over default_source
dusk tapir
ok, so while in subscription renewal you will be using default_payment_method
not default source
wheat dagger
Hey, taking over here. Let me know if there's any follow-up Qs I can answer!
wheat dagger
It depends on the workflow you did on that customer, could you provide more details?
dusk tapir
editing the card details was done by me, while subscription purchase was done by anther developer,
when he purchases subscription the default_option is set,
when the customer edits the default payment method through the customer portal, the default_payment_method is set, why
wheat dagger
when he purchases subscription the default_option is set,
How does the subscription is created? via API, isn't your integration setting the default_source then ?
dusk tapir
ya, through api. the default_source is setting at that time
but the default_payment_method is not setting up
wheat dagger
Between, for the same card we can have multiple card Id.
sleek valve
Hey, taking over here. Let me know if there's any follow-up Qs I can answer!
dusk tapir
same card have multiple ID ?
sleek valve
No, object IDs are globally unique