#lafafm-setup-intent-decline
1 messages ยท Page 1 of 1 (latest)
Hi ๐ was the decline returned for the Setup Intent, or was that associated with a Payment Intent that was used later?
Are there any additional details in the last_setup_error hash on the Setup Intent about the decline, or does that just show the generic decline information?
No, just generic one
As I remember generic errors may be triggered only by a bank OR Radar rule. Is it true?
If so - how can I determine was it blocked from Radar or not?
Can you share the ID of the Setup Intent? I'm not sure off-hand and would need to look at an example.
lafafm-setup-intent-decline
Yeah, sure
Sorry, stepped out for a bit
Here's a one of req_id
req_cl7xb0qzuygi93
seti_1M96BBJbrk1nz30Vu0cHNYKX
HI ๐ Sorry for the delay
looking now
This charge was not blocked by a Radar rule
This specific card had a previous decline that made it non-retryable.
Oh
How can I check it?
Or how can I find that previous decline?
That customer made around 15-20 requests, using different cards (credit / debit), all on his name
And all of them had declines
So really interested on investigation
This isn't something we surface
Yea, but you mentioned this
How can I get that information? E.g. that the decline was due to previous decline?
That's probably that customer's first attempt
seti_1M93W3Jbrk1nz30VXN5yPhce