Handling card present reversals with Elavon
Reversal operations with Elavon
In the context of payment processing with Elavon, a reversal (sometimes also referred to as a void) is an operation used to cancel or undo a previously authorized transaction before it has been fully settled. Reversals are a critical mechanism to ensure accuracy in transaction flows, allowing merchants to correct errors, prevent duplicate charges, or handle customer requests in real time.
There are two main categories of reversal operations:
Card Present Reversals – Require the physical presence of the payment card.
Standard (Non-Card Present) Reversals – Do not require the card to be present and can be initiated digitally.
Understanding the difference between these two approaches is essential for implementing compliant and functional payment solutions.
When working with Elavon, reversals are Card Present.
Card present vs standard reversals
Card Present Reversals
In Elavon, void operations are considered card present. This means that, in order to execute the reversal, the customer must physically insert, swipe, or tap their card into the payment reader. This requirement ensures an additional layer of security and validation, as the card itself is used to confirm the operation.Standard Reversals
These are processed without requiring the customer to present their card. A standard reversal can be performed purely through a system request, making it more convenient in scenarios such as online transactions, back-office adjustments, or when the customer is no longer physically present at the point of sale.
The choice between these two modes depends on the context of the transaction and the security requirements. In the case of Elavon, they require reversals to be Card Present.
Feature | Card Present Reversal | Standard Reversal |
|---|---|---|
Requires card? | ✅ Yes (insert/swipe/tap at reader) | ❌ No |
Typical usage | In-store corrections | Online refunds or admin adjustments |
Security level | Higher (physical validation) | Lower, but still secure via system checks |
Trigger parameter |
|
|
How to trigger Card Present reversals
To instruct Elavon that a reversal must be handled as a Card Present Reversal, the request payload needs to explicitly specify this intention.
This is achieved through the use of an optional boolean parameter within the <cardPresent> tag.
If
<cardPresent>true</cardPresent>is included:
The system will process the operation as a Card Present Reversal. In practice, this means the customer will be required to insert or present their card during the operation.If
<cardPresent>false</cardPresent>is included or if the tag is omitted entirely:
The reversal will be processed as a standard non-card-present reversal, meaning the transaction can be voided without requiring the card to be physically present.
Example Request (Illustrative)
<reversalRequest>
<transactionId>123456789</transactionId>
<amount>100.00</amount>
<currency>USD</currency>
<cardPresent>true</cardPresent>
</reversalRequest>
In this example:
The reversal request applies to transaction
123456789.The amount to be reversed is
100.00 USD.The
<cardPresent>flag is set totrue, instructing Elavon to treat this as a card present reversal.
These would be some possible use cases
Card Present Reversal:
A customer notices an error immediately after paying in-store (e.g., wrong amount entered).
Merchant wants to void the transaction before settlement while the customer and card are still present.
Standard Reversal:
An online order is canceled before shipment.
A duplicate transaction is detected during reconciliation, and the customer is no longer present.
Administrative reversal during batch processing.