Event Class: Transactions

Transactions Push Notifications proactively inform you about key transaction processing events. Receipt of near real time transaction results assist you in making timely decisions such as setting up Subscribe to notify your customer-facing applications of desired Transaction events —this can extend your retention/dunning activity. The Transactions Class currently includes the following events:

Event	Trigger
Transaction Succeeded (attempt succeeded)	One-time or Recurring Transaction captured. Message Content: transaction object Note: For Push 2.0, the transaction object can return the Payment Provider Response, Merchant Advice Codes, and Network Response Codes, if available.
Transaction Failed (attempt failed)	One-time or Recurring Transaction failed (canceled). Message Content: transaction object Note: For Push 2.0, the transaction object can return the Payment Provider Response, Merchant Advice Codes, and Network Response Codes, if available.
Renewal Transaction Succeeded (renewal succeeded)	Recurring renewal Transaction captured (active subscription billed beyond initial transaction). Message Content: transaction object Note: For Push 2.0, the transaction object can return the Payment Provider Response, Merchant Advice Codes, and Network Response Codes, if available.
Final Transaction Failed (final attempt failed)	The ultimate Transaction attempting to collect for a given invoice/billing has failed (cancelled). Message Content: transaction object Note: For Push 2.0, the transaction object can return the Payment Provider Response, Merchant Advice Codes, and Network Response Codes, if available.
Capture Reversed	Transaction Status changed from Captured to Cancelled, or to any status other than Refunded. Message Content: transaction object
Parent topic:Push Event Classes and Events

Home

Guides

APIs