#altszommmmme_best-practices

1 messages ¡ Page 1 of 1 (latest)

burnt dragonBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1292767194484310017

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

obtuse remnant
#

hello! what is your question?

latent forge
obtuse remnant
#

and what is your question?

latent forge
obtuse remnant
#

why would you need to convert a Source that's not attached to a customer?

#

if it's not attached to a Customer you can only charge it once, so there's no reason it needs to be converted.

latent forge
#

for off_session

#

as payment_intents api accepts sources but setup intent does not I believe

obtuse remnant
#

why don't you just change the code that creates the Source to create a PaymentMethod instead?

latent forge
obtuse remnant
#

so what's the problem?

#

also you said "migration for card", there is no migration for cards, Source type:"card" is not being actively removed, it's Sources for other payment methods that is being removed. But you should still migrate to PaymentMethods and Intents.

latent forge
#

yes, is there any way I can create a payment method directly using the source

obtuse remnant
#

you shouldn't have a Source in the first place. You'd just change the code that is currently creating and giving you a Source to create a PaymentMethod instead

latent forge
#

we are using the latest confirmation tokens

#

but we want to convert the old sources of type card to payment methods

obtuse remnant
#

you can't, that's not something we provide today

#

but it doesn't matter since you can pass old sources and they always work

latent forge
#

cant we make a confirmation token using a source to make it a payment method?

#

just like confirmation token created using a payment method

obtuse remnant
#

don't think so (the token thing is because certain flows like Apple Pay always create tokens so those needs to be converted)

#

like it really doesn't matter. If you have an existing saved Source on a Customer you can just pass payment_method:"src_xxx" when creating a PaymentIntent and it works, no need for ConfirmationTokens

latent forge
#

I think confirmation tokens should accept source param
just like this

curl https://api.stripe.com/v1/confirmation_tokens \
  -u "uk_xxx:" \
  -d payment_method=pm_card_visa

curl https://api.stripe.com/v1/confirmation_tokens \
  -u "uk_xxx:" \
  -d source=old_src

-> would convert the source to a payment method object in next payment

obtuse remnant
#

sure, that might be nice if it existed

latent forge
#

any way to suggest that as a feature?

obtuse remnant
#

you just did. Overall we don't have active plans for what do do with type:"card" Sources, as mentioned they 'just work' when you use them. Maybe in future we'll provide avenues to convert them to PMs in the same manner that the current non-card migration is doing, but that will be planned in the future

#

but anyway, what are you actually currently blocked on? what are you trying to do that you can't do?

latent forge
#

not stuck on anything, just for a bit consistency in legacy subscriptions ( own integration) to use the payment_method

I was just thinking if there is any way to convert the old_sources to payment method without collecting the card details from the customer again

obtuse remnant
#

there is not

latent forge
#

will payment method creation be blocked in near future (like sources) as we have confirmation tokens now?

obtuse remnant
#

no plans for that no

#

and Source creation for type:card is not blocked, it's just non-card methods that are being actively migrated

#

if we block something like type:card in future, you'd imagine it will be done in the same way where there will be tooling provided to convert old Source to PaymentMethod, but none of this is planned out yet

latent forge
#

alright have a nice day

#

is there any formal way I can suggest the team to implement the source in ctokens?

#

or payment_method_data[card][source] just like payment_method_data[card][token]

obtuse remnant
latent forge
obtuse remnant
#

not sure what you mean by that

latent forge
obtuse remnant
#

be civil please

latent forge
#

I never get a proper response from them

#

they just pass onto like "a team member will help you"

#

and then "we will escalate this to the related team"

#

then few days it continues and I don't get a proper response from them

obtuse remnant
#

yep, and as a member of one of those 'escalated teams' I can tell you we do get those cases and help with them. But no process is perfect, I'm sorry you didn't have a good experience and I appreciate the feedback

latent forge
obtuse remnant
#

that could work, not sure if the team who might eventually build this is represented there

burnt dragonBOT
obtuse remnant
#

I'm just being realistic with you, specific feature requests like that one are unlikely to really go anywhere, since if we're going to support converting Source->PaymentMethod it will be part of a larger project and the teams that will work on it haven't even started planning yet, so the actual shape of the solution could be anything. Like I said, if we block card Sources, as part of that we'll design some migration solution.

Sounds like you're not blocked, so that's all good! happy to have helped.

latent forge
#

all good

#

have a great day