#jennifer-payments-idempotency

1 messages · Page 1 of 1 (latest)

primal carbon
#

The documentation indicates they are not needed when using intents, but I don't see much of an explanation for why they are not needed
because in the typical integration, where you create a PaymentIntent server-side but confirm it client-side, it can only ever allow a maximum of 1 successful Charge on it, a single PaymentIntent can never double Charge.

However, for your recurring payments, you'll be creating and confirming the PaymentIntent server-side, in which case yes you can leverage idempotency keys then, as that is one request that creates and confirms a payment in one go as opposed to 2 distinct requests (one from server and one from client)