cancel
Showing results for 
Search instead for 
Did you mean: 

Best practices for handling retries with the Cybersource REST Payments API?

Hi everyone,

I'm integrating the Cybersource REST Payments API into a web application and would like to understand the recommended approach for handling temporary API failures.

Specifically:

  • What retry strategy do you use for transient errors (timeouts, 5xx responses, etc.)?
  • How do you prevent duplicate payment authorizations when retrying requests?
  • Are there recommended idempotency patterns or request identifiers that work well with Cybersource?
  • Do you log every request/response for troubleshooting, and if so, what information do you avoid storing for security reasons?

I'd appreciate any examples or best practices from developers who have implemented this in production.

https://subwaysurferdl.com/

Thanks!

finallen1231
Member
0 REPLIES 0