#ambi_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ 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/1281622152260358144
๐ 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.
- ambi_invoice-uncollectible, 15 hours ago, 11 messages
Hello
Yes that email should be set as the customer.email
But you also should be able to test Google Pay and Apple Pay just fine here
As long as you have a live card in your Google or Apple Wallet
(We will swap that live card out for a test card when you are in test mode)
ohhh I see, I need to add it.
but thanks for the confirmation.
๐
my alternative was setting the client_reference_id (and set it to an internal userId from my db) when creating the session, then when the 'customer.subscription.created' event arrives, get the session and use that Id instead of the email to connect the user to the subscription in the database
would you say it is unnecessary then? I can go on with using the email (I will test it)
Yeah up to you really. Email is fine as long as you ensure you don't duplicate emails (we won't prevent this duplication for you)
I see, thanks for the help! have a great day