#matteo-paymentintent
outer tree
{
"error": {
"message": "Keys for idempotent requests can only be used with the same parameters they were first used with. Try using a key other than '1234568' if you meant to execute a different request.",
"type": "idempotency_error"
}
}
req_3XYbjBi9sBIbR6
umbral notch
yep, as the error says. You used that key for a request with different parameters in the past(you used it for https://dashboard.stripe.com/test/logs/req_9Mb2heP0YswK5v which was an entirely different payment_method)
you don't really understand the point of our idempotency support, sorry.
you use it to retry a request when there's a networking error, like you send a request and you never got a response, and you're not sure if Stripe processed the request. So you want to retry that exact same request safely. It makes no sense to use it the way you're trying to there.
outer tree
it makes sense because I have double payment issues due to an ineffective sfcc Link cartridge.
since there are two calls, one to carry out the payment_intent and one to update with the metadata, the risk that the customer blocks the flow is lift as already happened
so at least if the payment method is the same and there is already a paid order I see not to place the double payment
umbral notch
can't understand you through the language barrier, again like I said yesterday we can't help with SFCC here.
outer tree
in fact my question was about an API