Idempotency

A request method is considered "idempotent" if the intended effect on the server of multiple identical requests with that method is the same as the effect for a single such request.

Moneris Cloud API supports idempotency for safely retrying requests without performing the same operation twice on the authorization host. This is useful when your API call get disrupted and you don’t receive a response message.

For example, if request for a “purchase” transaction does not get a response due to a network connection error, you can retry the request with the same idempotency key to guarantee that cardholder won’t be charged more than once.

  • Pre-Authorization

  • Pre-Authorization Completion

  • Activate/Load

  • Deactivate

  • Get Track Data

  • Get Hash

  • Card Verification

Idempotency is only supported for the following transactions:

  • Sync

  • Scan

  • Purchase

  • Card-on-file Refund

  • Card Present Refund

  • Void

  • Void Last

  • Balance Inquiry

Idempotent Response Code Scenarios

In all of the following use cases, the assumption is that the incoming new request has an idempotent key, identical to one of the one hundred previously processed commands.