Transaction Examples: Void

Void

Void transactions can reverse transactions that have been previously authorized or approved by the card issuer and are pending settlement. Merchants can void both Authorizations as well as Sales, with slightly different effects: voiding an Authorization causes a reversal to be sent to the issuer, and the Authorization is no longer available to be Captured and settled by the merchant. Voiding a Sale or Captured transaction, which is in an open batch (pending settlement), will remove the transaction from the batch and send a reversal to the issuer. Transactions in closed batches cannot be voided.

Void Approved

A Void is a linked transaction. Like a Matched Refund, it is linked to a purchase by requiring a previous (original) Gateway-assigned Transaction ID.

Void Approved Request

XML

JSON

PHP (JSON)

https://github.com/Clearent-Gateway/API-Examples/tree/php

Python (JSON)

https://github.com/Clearent-Gateway/API-Examples/tree/python

Go (XML)

https://github.com/Clearent-Gateway/API-Examples/tree/go

C# (JSON)

https://github.com/Clearent-Gateway/API-Examples/tree/C#

Java (JSON)

https://github.com/Clearent-Gateway/API-Examples/tree/java

VB.net (JSON)

https://github.com/Clearent-Gateway/API-Examples/tree/vbnet

Void Approved Response

XML

JSON