#linups_code

1 messages · Page 1 of 1 (latest)

crystal badgeBOT
#

👋 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/1420790570091155566

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

dreamy arch
#

Hey there, customer_creation is a concept that only applies to checkout sessions, you're correct this is not supported on payment intents

#

You need to manage customer creation manually and when appropriate pass that to the payment intent as customer: 'cus_123'

upbeat ore
#

Thanks, so i can create a customer at first only with email, and then with ApplePay request create paymentIntent and pass that customer id ?

dreamy arch
#

yep, set the customer on the payment intent

upbeat ore
#

thanks, give me 5 mins to try...

#

if, later i want to charge same customer, is it better to use : 'confirmation_method' => 'automatic', OR 'automatic_payment_methods' => ['enabled' => true], ?

#

i dont think, i understand main difference between it

dreamy arch
#

These are very different things mostly completely independent of one another, and also not particularly related to apple pay. What a are you trying to do?

upbeat ore
#

i local.ERROR: You may only specify one of these parameters: automatic_payment_methods, confirmation_method. {"exception":"[object] (Stripe\Exception\InvalidRequestException(code: 0): You may only specify one of these parameters: automatic_payment_methods, confirmation_method.

#

i want to be sure, that later i will be able to charge user, if he made previous payment with apple pay.

dreamy arch
#

unless you have a specific reason to change the confirmation method, you should not use that parameter

#

This is only relevant in rare cases for specific flows

#

And if you're on a recent API version, automatic payment methods is enabled by default

#

most likely you should omit both of these

#

What doc suggested these parameters as having anything to do with future payments?

upbeat ore
#

probably i just added by myself..

#

if i understand correctly, when i create intent and return client secret back: return response()->json(['clientSecret' => $intent->client_secret]); At this time payment was not fulfilled yet ?

#

thinking, how to save succeded payment data.

dreamy arch
#

Payment must be confirmed to attempt payment, either client side with new payment details or server side with previously collected payment details

crystal badgeBOT
dreamy arch
#

(and used for payment)

upbeat ore
#

yes, i used that. trying to test the upsell.

still tinsel
#

Hi, it's been some time since we've heard back. Just wanted to ensure you've had all your questions addressed.

upbeat ore
#

yes, at least now 😄 thanks for help.