Closed VitaminTussle closed 4 months ago
@VitaminTussle This is a feature request for the API and is better directed at our support team who tracks all those requests instead. Please contact them here: https://support.stripe.com/contact for 1:1 help.
Thanks @remi-stripe. Appreciate the redirect. Here's hoping they're as responsive.
Is your feature request related to a problem? Please describe.
My company applies Charges to saved Cards/PaymentMethods well after accepting payment information. Currently, we set those PaymentMethods up using SetupIntents, and while the Stripe dashboard shows the risk score and risk level under the "Risk evaluation" label as shown below, that information is not currently exposed to the API at the time of SetupIntent creation. We would like to internally notify our fraud team depending on the potential risk level at the time of PaymentMethod creation, but are currently unable to access that information in code.
Describe the solution you'd like
This is a request URL I found via the Network tab of the devtools window while on the Stripe dashboard page shown in the problem section:
https://dashboard.stripe.com/v1/setup_intents/seti_[ID_SANITIZED]?expand%5B%5D=customer&expand%5B%5D=payment_method&expand%5B%5D=latest_attempt&expand%5B%5D=mandate
Within the resulting expanded
latest_attempt
object in the response, the following property is included:I cannot currently expand the
latest_attempt
property via the SetupIntent API beyond getting its ID, and even when the SetupAttempt object is fetched separately, theradar_results
data is not included, even when targeted with theexpand
prop. I would like to see theradar_results
information included on either the response from the creation of the SetupIntent, or on the fetch of the SetupAttempt.Describe alternatives you've considered
The only alternatives I've been able to find are to either completely shift our payment cycle to be able to charge customers immediately with Charge objects, which isn't very feasible at our scale, or to scrape the Stripe dashboard, which just seems excessive.
Additional context
No response