public class LoyaltyReceivedEvent

When loyalty offers and IDs are added by applications in response to the com.verifone.commerce.triggers.LoyaltyRequest Trigger, the list is returned in this event. This allows the POS application to keep track of changes and provides the opportunity to filter which offers and loyalty accounts are applied to the final transaction.



public static final String TYPE

Loyalty received event type



public LoyaltyReceivedEventResponse generateLoyaltyReceivedEventResponse()

Generates a LoyaltyReceivedResponse object for return to the service.


public String getEventId()

Returns the event ID associated with this event. Useful for matching the event received by the listener to the original status returned when issuing the call, for example, calling com.verifone.commerce.payment.TransactionManager.reprintReceipt(Payment) returns a CommerceEvent containing an event ID, which will match the event ID received by the CommerceListener when the receipt reprint is complete.


public String getInvoiceId()

The invoice ID for the transaction as a reference.


public ArrayList<LoyaltyAdjustment> getLoyaltyAdjustments()

Get the list of adjustments that have been added by various other applications.


public String getLoyaltyId()

The ID for loyalty record


public ArrayList<Offer> getLoyaltyOffersList()

Gets all of the offers aggregated into one list, making it easier to apply all.


public String getMessage()

A user-readable message. This message may not be localized, in which case the type field should be used for determining a localized message.


public Payment getPayment()

Get the appropriate payment object that led to this adjustment.


public String getSessionId()

Get the session ID for the session which triggered this event.


public int getStatus()

Get the status for this particular event. A status of 0 means success, any other status is a failure.


public Transaction getTransaction()

The transaction associated with this event.


public String getType()

The type of status. This will generally be SUCCESS for a status of 0, and contain a different type for other errors. For example, in a refund or void, it is possible to receive type TRANSACTION_NOT_FOUND. This may be used for localizing the specific messages as needed