#khadim-yaseen_api
inland hearthBOT
👋 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/1284050348117463050
📝 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.
- khadim-yaseen_code, 3 days ago, 24 messages
fiery storm
Create SetupIntent:
$intent = $stripe->setupIntents->create(
[
'customer' => $customer->id,
'automatic_payment_methods' => ['enabled' => true],
'usage' => 'off_session',
'metadata' => [
'from' => 'paymentElement',
'passbackconversiontrackingid' => $data['rtid'],
]
]
);
Confirm SetupIntent
const {error} = await stripe.confirmSetup({
elements,
clientSecret,
confirmParams: {
return_url: window.location.origin+'/success.html',
payment_method_data: {
billing_details: {
address: {
postal_code: postcode,
}
}
},
},
})
fierce prairie
Can you share the request ID (req_xxx) of the error? Here’s how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
fiery storm
Sure
fierce prairie
The above two requests didn't have the error you described
fiery storm
Can you please check
I don't see an error in logs for this particular customer.
But events have the failed setup event
fierce prairie
The Setup Intent failed was due to the Radar rule:
Block if :email: INCLUDES '+'
It had nothing to do with 3DS, but your own Radar rule blocked customer email address that contains "+"
fiery storm
That was one of the tests
Do you think this case was also blocked by the radar?
fierce prairie
Have you checked the email address of this customer? Could you share the Setup Intent ID (seti_xxx) in the screenshot, so that I can take a look?
fierce prairie
seti_1PyAUzED5xkfDv2cmRzo3B6L was blocked due to https://dashboard.stripe.com/radar/rule-details?ruleId=ssr_1KRYUPED5xkfDv2c6npI5tPf&startDate=2024-03-17&endDate=2024-09-13
Block if :is_disposable_email:
Yes I guess this makes sense
But there was was some cards that Did go through, confirm intent was success.
I have webhook to create subscription upon success setupIntent.
This subscription is on trial period.
When trial periods ends and first invoice asks for 3DS auth.
I am sorry I will have to go right now.
If you can keep this thread open, please do
or I will create a new thread later.
my apologizies
inland hearthBOT