#ketaaa - Payment Intent
1 messages · Page 1 of 1 (latest)
Could you please move the image to this thread? Also a request ID would be useful
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
req_YPAIcCNzgNs3gT
basically the magento module (not asking support about this module but to give you context) is checking is a payment intent is valid if we have the same data than the one saved in cache that the one we request. And off_session and confirm param are not in the api call response
basically all the field that I passed in the body request are returned in the response body except those 2 fields
it's not a blocker for me as i can dodge this verification but is there any reason?
Those are parameters of the Create Payment Intent function but they are not Properties of the Payment Intent object.
What we return is the Payment Intent object with it's properties :
https://stripe.com/docs/api/payment_intents/object
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
but this is stored somewhere on your side right?
It does change the properties of the Payment Intent you create and ensures the behavior you expect.
@urban sinew what error code do I have to send to ask stripe to retry it later ?
For a webhook?
Anything that is not 200 will trigger webhook retries
Because sometimes order création take a bit longer than the webhook
Sometimes my app returns 202 But it doesn’t seems to retry because I see success in the interface
Yeah anything in the 2xx range is considered success
Fair enough, in live mode in how long time it will trigger the first retry ?
First retry is immediate. Then delays increase after each failure.
You can use 3xx responses as we outline here: https://stripe.com/docs/webhooks#built-in-retries
if you wanted to differentiate between needing more time and actual issues with your code
thanks a lot
perfect
and my last question will be, is it easily possible to do this testing scenario :
" I create a payment all good, i'm doing one recurring payment with the same payment method, good aswell and on the third recurring, I have an insufficient funds error"
all with the same payment_method tokens
Not directly. We don't have test payment tokens that fail only after the 2nd attempt. The closest you could get is to use a successful payment method associated with the customer for the first two recurring payments but before the third you update the customer's PM to one that will fail with the insufficient funds error
Would work aswell
So we have some testing payment method string somewhere in the doc right ?
Oh yeah 😁 , start here and keep scrolling until you find what you're looking for
https://stripe.com/docs/testing#declined-payments
Happy to help 🙂 it's why we're here
Really cool solution, I will recommend stripe for my other clients aswell !
Cool to work with and nice support
Thanks! We try to be as helpful as we can.