philton_docs

[grim kettle]

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

📝 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.

• philton_docs, 21 hours ago, 14 messages

[stray stirrup]

hi! do you have an example like the PaymentIntent ID pi_xxxx of the 'subsequent payment' that didn't work?

[lunar dock]

We didn't have Apple Pay before; users were paying with a card.

[stray stirrup]

hmm, as a guess, are you maybe expecting that a payment gets automatically processed only as a result of setting the recurringPaymentStartDate fields? AFAIK that is not how it works, these fields are just for providing information to the cardholder/Apple, you still need to actually process the payments(via off_session PaymentIntents or our Subscriptions API) normally.

[lunar dock]

You're welcome! Feel free to reach out if any questions come up. Good luck!

[stray stirrup]

I'm quite confused 😅

[lunar dock]

I'm add setupFutureUsage: 'on_session' in stripe.elements and I get an error when paying

The provided setup_future_usage (null) does not match the expected setup_future_usage (on_session). Try confirming with a Payment Intent that is configured to use the same parameters as Stripe Elements.

[stray stirrup]

yes you need to make sure that when you create the PaymentIntent on the backend, it needs to also pass setup_future_usage, the values need to match.

[lunar dock]

here it is, what else should I indicate?

[stray stirrup]

"setup_future_usage" => "on_session", , like I said, right?

[lunar dock]

Great! I'm glad the payment went through without errors after adding the parameter to the PaymentIntent. Let's see if the next payment processes after 10 minutes as expected. Let me know how it goes!

[stray stirrup]

I'm so confused, are you using ChatGPT for these messages?

[lunar dock]

Yes, I use it as a translator.

[lunar dock]

Now, after this payment, can I use the API to add a subscription for the customer that will be automatically charged through Apple Pay?

[tame lava]

Hey! Taking over for my colleague. Let me catch up.

[lunar dock]

ok but why is it created as Guest Client gcus_***

[tame lava]

Sorry, could you please summarize what you want to achieve exactly ? collect a payment and use its PaymentMethod later in order to create a Subscription ?

[lunar dock]

I want the user to pay for a paid trial version of the subscription through Apple Pay or Google Pay (for example, $10 for 10 days), and after this period ends, the full subscription for a month should automatically start, with the payment being charged through Apple Pay or Google Pay as well.