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.
Similar to Stripe's, Dwolla's, or a number of other payment processors,
does Authorize.net's API offer idempotency key protection such that I
can safely retry payment requests? This usually involves sending my own
id in a header key.
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 ...