#buderscotch_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ 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/1339384584491634789
๐ 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.
- buderscotch_api, 2 days ago, 18 messages
Hi there! I've been receiving a large amount of payment declines, causing churn. I implemented the creation of payment intents (using the doc https://docs.stripe.com/api/payment_intents/object?lang=curl), but I was wondering if I need to fill up all the parameters?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Right now, the only parameters I fill up is amount, currency, description, and confirm (as true)
Is it safe to think that the high risk scores/fraudulent errors and consequent failed payments are due to less paremters being sent?
Hi! I wouldn't assume anything.
Or is it just the customers' end that is the issue?
I can't answer that, but Stripe Support can look into specific charges for you / answer those questions.
What are you using for collecting payment method details?
But in terms of best practices, to implement the API /payment_intents, what is the recommended parameters?
or is amoutn, currency, description, and confirm all that is necessary
Not using the collection of payment method details, actually, but I saw that there is an option for it
read about Stripe evaluation and Stripe radar, and right now I have a threshhold of 75 for my risk score
How are you getting a payment method for these Payment Intents then?
ah okay, you mean /payment_method
yeah,im calling the endpoint /payment_method first
giving the values for the card (number, exp_month, exp_year, and cvc)
Where are you getting those values?
from the customer
How?
using the stripe element
Oh ok. Cool.
then sending the form value over via ajax
POST data -> to my controller
then my controller calls the /payment_method endpoint
sends those data
however, i see a large number of charges cause declines
specifically generic_decline and fraudulent error codes
with messages like Stripe blocked this payment as too risky
Yup, payment works most times
It's just I'm trying to see why are there customers that are risky
and is their riskyness due to our implementation,or theirs?
because if we can confirm that our implementation is already good and best practice, then we can assume it really is just risky customers
Yes, followed the guide. Implementation is working
I'd suggest you reach out to Support and they can dig into the details of those charges for you.
We wish we could help, but you need to talk to Stripe support
We can only help on Discord if all of the following are true:
- ๐งโ๐ป You must be a developer
- ๐ ๏ธ Your question must be about building a Stripe integration
- โ๏ธ Your question must be technical/developer focused
- โฑ๏ธ You must be available to respond in realtime
- ๐ฅ You must be comfortable receiving help in public (this is a public server)
If any of those aren't true please contact Stripe support.
If all of those are true we may have misunderstood your question; please provide more details below.
Note that using an inappropriate button or submitting inappropriate information is a violation of our rules. You will be removed from this server if you repeatedly create invalid threads.
But can you, as a developer, confirm that there isnt a "hard requirement" on the parameters being passed in the API?
That is the main question of this topic
If you make an API call and it was succesful, you passed sufficient and correct parameters.