barrycarlyon_webhooks

[verbal sparrow]

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

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

[river kindle]

What are you using to accept payments?

Checkout?

Payment Element?

[onyx hedge]

Checkout

I think the issues been going for a while but only affects transactions using amazon pay.
It was just noticed today by my client.

I was about to write some code to go back thru history and see. But got as far as coming here to go fishing.

[river kindle]

Checkout won't propagate metadata down to the Charge object. The closest thing you could do would be to add it to the corresponding Payment Intent via payment_intent_data.metadata on the Checkot Session object (https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-metadata), which will add it to the Payment Intent. From there you can listen for payment_intent.succeeded instead of charge.succeeded (https://docs.stripe.com/api/events/types#event_types-payment_intent.succeeded)

[onyx hedge]

but it does for every other payment type that isn't amazon pay.

So now I'm just confused

Oh I do that

so I do this

                const stripe_session = await stripe.checkout.sessions.create({
                    mode: 'payment',
                    success_url: `https://${process.env.SERVER_DOMAIN}/tip/${req.params.slug}/success/`,
                    cancel_url: `https://${process.env.SERVER_DOMAIN}/tip/${req.params.slug}/cancel/`,

                    customer_creation: 'if_required',
                    client_reference_id: ref_id,

                    line_items: [
                        {
                            price_data: {
                                currency: 'USD',
                                unit_amount: amount,
                                product_data: {
                                    name: 'REMOVED'
                                },
                            },
                            quantity: 1
                        }
                    ],

                    payment_intent_data: {
                        transfer_group: 'mods123',
                        metadata: {
                            reference_id: ref_id
                        }
                    }
                });

But for anything that goes via amazon pay charge.succeeded is dropping the metadata.

But I should be listening to payment_intent.succeeded instead/as well?

[river kindle]

I didn't think that metadata was propogated from the Payment Intent to the Charge, but I could be wrong. In any case, payment_intent.succeeded is better here anyway, as it contains the Charge object if needed, but the Payment Intent object itself should contain everything you need.

[onyx hedge]

yeah it's weird as it does for "regular card payments" in that case.

We just had some peeps transact with amazon pay and it's weirded.

I'll swap topics.

here the left being a amazon pay and the right being a mastercard.

Both charge.succeeded

But I'll work on switching over and see how we go! Thanks.

[river kindle]

Huh, that's odd. Yeah, switching over should fix the issue all the same.

[onyx hedge]

Yeah I'll have a look over all my transactions and see if it effected anything else.

All four amazon pays didn't notify to me properly

[onyx hedge]

Having checked I tuned on amazon pay august 2nd so it's a new "hiccup" so thankfully I didn't miss too many paymets on my current setup

As a side note I'm currentl on API version 2022-08-01 I should probably kick it to newer too.

[tawdry marsh]

Good to hear it hasn't effected too many of them. Anything we can help you with with the API upgrade?