topic Idempotency Protection for payment requests in Integration and Testing

Idempotency Protection for payment requests

DennisDang — Tue, 09 Nov 2021 20:39:13 GMT

Does Authorize.net's API offer idempotency protection in some form?

I've seen idempotency protection in the form of unique ids in headers (e.g. Stripe), or in the form of some behind-the-scenes heuristics (i.e. Repay).

Re: Idempotency Protection for payment requests

MansourH — Mon, 29 Nov 2021 16:10:21 GMT

Hi @DennisDang,

Authorize.net offer a duplicateWindow setting that can be set up to 8hours, this will prevent processing duplicate transactions within the set window. Read more on the Payment Transaction Developer Guide (Transaction Settings -> duplicateWindow), duplicate transactions requests will return error code 11.

Thanks

-Mansour

Re: Idempotency Protection for payment requests

DennisDang — Mon, 29 Nov 2021 17:20:52 GMT

Thank you @MansourH. I didn't realize I had double-posted. Sorry.

What data are you using to deduplicate? Is it a conglomerate of things? In addition to setting the duplicateWindow time, is there a unique constraint of sorts on txn refIds? If that's the case, I imagine duplicateWindow + unique refIds will serve me well enough.

Re: Idempotency Protection for payment requests

MansourH — Mon, 29 Nov 2021 17:52:13 GMT

There are a bunch of fields that are validated for duplicate requests, I've included a link to error code 11 that list these fields:

https://developer.authorize.net/api/reference/responseCodes.html?code=11

Thanks

-Mansour

Re: Idempotency Protection for payment requests

payment123 — Wed, 25 Oct 2023 18:00:26 GMT

Hey did you find out if refId could be use for the duplicate window?

I'm looking to use 1 of the fields in @MansourH 's link but it's not obvious wich of those fields can be a UUID generated by my application to ensure the idempotency of payments.