You are here:
To ensure smooth operation, get notified of Payments platform events as a transaction goes through its lifecycle. Events can include payment authorizations, captures, and refunds.
| View supported editions. |
Salesforce Payments uses a high-scale asynchronous architecture, so events focus on client-side activity at the end user’s browser. Examples of asynchronous events are payment authorizations, captures, and refunds.
To get notified of these platform events, incorporate them into flows or Apex triggers. Use any notification mechanism that flows or triggers support, such as Slack, SMS, or email, or a Lightning notification app.
Payments platform events are generated automatically and represented by these objects:
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.