josha_api

[dry sonnet]

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

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

[cedar maple]

Hello! You can set up a Payment Method created with Apple Pay for future use and reuse it, but there are some caveats. See here for details: https://docs.stripe.com/apple-pay/apple-pay-recurring

[grand osprey]

We will always want to use Apple Pay in an on-session way. Would the best practice here, then, be to, each time a payment needs to be made:

1. Create a new Payment Request
2. Create a new Payment Method (via Apple Pay)
3. Confirm the PR from #1 with the new PM from #2
   ?

[cedar maple]

Yep.

If you're always using Apple Pay on-session that's the right way to do it.

[grand osprey]

Specifically, there would not be any ability or requirement to associate an Apple Pay-based PM with a user account, charge it from there, etc?

[cedar maple]

Yeah, if you don't need to do that there's no reason to set the Payment Method up for future use or attach it to a Customer.

[grand osprey]

gotcha. ok.. thank you!