#rena7ssance_webhooks
analog breachBOT
👋 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/1503508247737401375
📝 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.
- renaissance_mandate-update, 4 days ago, 34 messages
small mural
hey @zenith fox , sorry to trouble you. (1) in our system we have a monthly charge on user for payment code pi_3TRbP7FXfYQzZWMa2iCbi1ZX or payment method "pm_1TGMdlFXfYQzZWMaiEBT3cra"; (2) per my discussed with stripe eng last week, currently our system passes wrong payload to stripe when calling payment_intents/create and should receive a mandate.udpated event #dev-help message; (3) but when i check the monthly charge case, i did not see any mandate.updated event
can you help understand how the charge integration behavior looks like between Airbnb<>Stripe here? thank you
zenith fox
👋 taking a look over your previous thread with my team to get caught up on the context.
small mural
thank you!
zenith fox
Do you have an example mandate, that you know was updated but for which you never received the webhook?
small mural
this one. evt_1TUVdtFXfYQzZWMaD78KnVPB (it's said that we received this because we explicitly passes the mandate in the payload to payment_intents/create endpoint.
^ so far, i think our charging endpoints <> stripe are with this mandate explicitly setup (wrongly), which means we should receive the mandate.updated as for one-time use.
for 1) in our system we have a monthly charge on user for payment code pi_3TRbP7FXfYQzZWMa2iCbi1ZX or payment method "pm_1TGMdlFXfYQzZWMaiEBT3cra", i did not see any mandate.updated webhook event. so wanna check with your side what happened here
zenith fox
I'm seeing the following event for the mandate on that PI evt_1TTiMGFXfYQzZWMaBm9h7cyf
small mural
if possible could you share me the mandate.updated event?
zenith fox
the account acct_1MhFVJFXfYQzZWMa associated with that event does not seem to have any Webhook endpoints listening for mandate.updated events so it was never sent to a webhook endpoint.
evt_1TTiMGFXfYQzZWMaBm9h7cyf is the mandate.updated event. for the mandate on pi_3TRbP7FXfYQzZWMa2iCbi1ZX
or are you asking for the contents of the event not it's ID?
small mural
thanks for the sharing. i found it here
regards to the thread, "the account acct_1MhFVJFXfYQzZWMa associated with that event does not seem to have any Webhook endpoints listening for mandate.updated events so it was never sent to a webhook endpoint." can you help me better understand what does it mean by the account has no webhook endpoint listening for mandate.updated events ? is this something Airbnb side (client side setup?)
zenith fox
Webhook Endpoints only listen for events that they are are configured for. acct_1MhFVJFXfYQzZWMa, is not listening for mandate.updated events on their webhook endpoints, so while they still show up in logs they don't get sent to the end point.
This is configured in the Dashboard or via API on the account.
small mural
🫡 thanks for the information.
two small questions (not sure whether this channel can help). (1) for pi_3TRbP7FXfYQzZWMa2iCbi1ZX, i think Airbnb call Stripe on Apr 29th for the charge and we received success response on Apr 29th and May 5th. could you help me understand why we have two success responses here; (2) for the potential charge on Apr 29th, could you confirm Airbnb is calling payment_intents/create endpoint?
thank you!
zenith fox
are you able to share the success responses here?
analog breachBOT
zenith fox
It looks like this was ACH (Bank) so the intial response was likely that it was processing and the one one the 5th was when the transaction succeeded. ACH/Bank payments usually have a several day processing delay.
small mural
i did not find it on stripe dashboard while i have our system payment code 0MG0aXX7wO5djK3cYzTrPYPzrDl and externalReferenceToken 0MG0aXX7wO5djK3cYzTrPYPzrDl (not sure what they stand in Stripe system)
royal chasm
Hi there. I'll be taking over for my colleague here, who needs to step away
small mural
thank you @zenith fox for all the help and glad to meet you @royal chasm
i think my only question is to confirm for the potential charge on Apr 29th, could you confirm Airbnb is calling payment_intents/create endpoint? context: payment code 0MG0aXX7wO5djK3cYzTrPYPzrDl and externalReferenceToken 0MG0aXX7wO5djK3cYzTrPYPzrDl (not sure what they stand in Stripe system)
royal chasm
What's your relationship to AirBnB? Are you a connected account?
small mural
I am an Airbnb payment engineer
royal chasm
Great! Unfortunately I can't do anything with those tokens - we would need something in Stripe. A Customer, a PaymentIntent, or a PaymentMethod. Some id to investigate
small mural
ok. for payment method id "pm_1TGMdlFXfYQzZWMaiEBT3cra"
royal chasm
Yes, it looks like there was a payment on that date. Here's the request log: https://dashboard.stripe.com/logs/req_8CLhbarsuCKm0R
small mural
great! thanks for the information! appreciated for the confirmation.
royal chasm
Yep!
small mural
a very quick question: since the webhood event mandate.updated was emitted for this payment method https://dashboard.stripe.com/acct_1MhFVJFXfYQzZWMa/workbench/events?search=evt_1TTiMGFXfYQzZWMaBm9h7cyf, do you know what's error code Stripe will return if we post /v1/payment_intents on this payment method?
^^ or will the answer be different when Airbnb post v1/payment_intents with mandate v.s. /v1/payment_intents without mandate
royal chasm
I think it should be a 402 with payment_intent_mandate_invalid - https://docs.stripe.com/error-codes
I would make sure you're listening for that event type too, because a lot of people who take bank debit payments, especially in the US, don't and then they get confused when an ACH mandate gets revoked/invalidated
small mural
"you're listening for that event type too" do you mean mandate.updated event type?
royal chasm
yes
small mural
(1) we are not listening at this moment (2) but we plan to listen it for internal consumption that avoids unnecessary charge request to Stripe.
royal chasm
Also, the remedy is to bring your Customer on-session and recollect their bank details and generate a new mandate, so it tells you that is necessary too
small mural
thanks for the suggestion.
a weird thing i notice is for "pm_1TGMdlFXfYQzZWMaiEBT3cra": I saw we had the charged on this payment method on Mar 29th and Apr 29th. since currently Airbnb is calling Stripe v1/payment_intents endpoint with mandate field explictly defined, i think Stripe will treat Airbnb create one-time use mandate and update it into inactive . But i only found on mandate.udpated event https://dashboard.stripe.com/acct_1MhFVJFXfYQzZWMa/workbench/events?resource=pm_1TGMdlFXfYQzZWMaiEBT3cra&search=evt_1TTiMGFXfYQzZWMaBm9h7cyf
(1) did i miss another mandate.updated event (i think it was expected to happen on around Apr 5th? (2) if i miss it, then another problem i think is that the Apr 29th charge should fail right?
royal chasm
Yeah, there was an event evt_1THn7aFXfYQzZWMa8peSWnlZ on 4/2/26
You should be able to view it in your dashboard still
It is already out of retention on our end so I can't see what the event body was
small mural
ok. yes thanks for the referring https://dashboard.stripe.com/acct_1MhFVJFXfYQzZWMa/workbench/events?search=evt_1THn7aFXfYQzZWMa8peSWnlZ i found it too.
but i saw the status is inactive , then why the charge happen on Apr 29t successfully?
royal chasm
Could you maybe paste the full event body in here so I can see what you're referring to?
small mural
{
"object": {
"id": "mandate_1TGMdsFXfYQzZWMavfix7ST5",
"object": "mandate",
"status": "inactive",
"type": "single_use"
},
"previous_attributes": {
"status": "active"
}
}
royal chasm
You passed new mandate data in req_8CLhbarsuCKm0R on 4/29, which I guess has the effect of causing us to create a new, single-use mandate
small mural
ic. thanks for the clarification! that makes sense!
really appreciated your help and investigation (sorry a lot of annoy questions)
royal chasm
that's alright! we are here to help
analog breachBOT