#flyingace68_docs
clever spadeBOT
đ 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/1281691745104564330
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
vapid sun
Hi, what does 'altered' mean here? The end customer cannot make changes on the amount rendered for instance, however, I do not fully understand whay you mean by this.
In general, after you created the Checkout Session, the end customer adds their payment details. You can set where they are redirected after the Session is completed by providing the URL: https://docs.stripe.com/billing/quickstart#urls.
dusk portal
The Session object can possibly contain a metadata object. Is that metadata included in any response following successful checkout?
vapid sun
Yes, that metadata will be in the Checkout Session Object
dusk portal
Is the Checkout Session Object different from the Session object that I was talking about in the first place?
The thinking here was that we would want to be able to update our own records when a user had completed purchase of a subscription. So we could include the userId we have in our records for that user in the metadata object. What I'm trying to understand is if there is some response that would then contain that same metadata so that we could use that as confirmation of a successful checkout.
vapid sun
I assume we're talking about the same object. We have multiple Session objects so I always like to specificy here: https://docs.stripe.com/api/checkout/sessions/object.
dusk portal
Okay, so if this is true:
Once payment is successful, the Checkout Session will contain a reference to the Customer, and either the successful PaymentIntent or an active Subscription.
then the record is altered in as much as it is updated to include the reference to the Customer.
vapid sun
You can set up webhooks, https://docs.stripe.com/webhooks and listen for checkout.session.completed events. On thay event, you would see the metadata given that you passed that metadata when you created the Checkout Session.
We talk more about it here: https://docs.stripe.com/checkout/fulfillment
dusk portal
Okay, thanks for your help and your patience.