April 30, 2024

Transaction Grouping Consistency Improvements

On May 14, 2024 (Tuesday), we will be standardizing the way certain return events are conveyed in the transaction object. The goal of this change is to create consistency in the way transaction lifecycle events are communicated. This change standardizes the handling of RETURN events to the sequence described in the Return section of our Transaction Flow documentation.

Previously, depending on how acquirers submitted a return-related message, a RETURN event could appear as either linked to a prior purchase authorization (see first example transaction in Multiple Completion section of our Transaction Flow documentation) or as a standalone event in a new transaction object. This resulted in two distinct models for an otherwise equivalent transaction.

After this change, all returns that are not preceded by a credit authorization event will be surfaced as their own transaction object.

Please reach out to [email protected] for any questions or concerns.