# Commercial Event Notifications source: https://developer.mastercard.com/commercial-event-notifications/documentation/index.md ## Overview {#overview} The Commercial Event Notifications service generates and delivers notifications for events of interest to subscribers in the area of commercial payments using virtual card numbers (VCNs). Subscribers can be issuers, companies, or agents who create VCNs using [In Control for Commercial Payments](https://developer.mastercard.com/product/in-control-for-commercial-payments/) (ICCP) or [Business Payment Controls](https://developer.mastercard.com/product/business-payment-controls), and who use those VCNs to make business payments. The API delivers notifications of token events for VCNs generated by [In Control for Mobile Payments](https://developer.mastercard.com/product/in-control-for-mobile-payments) (ICMP) and payment events for VCNs generated by In Control for Commercial Payments (ICCP) or Business Payment Controls. Notifications are triggered by the presentation of a VCN for a payment, either by entering the details on a point of sale terminal or by making a payment using Mastercard [Straight Through Processing](https://developer.mastercard.com/product/straight-through-processing-stp/) (STP) or [Mastercard Payment Gateway Services](https://developer.mastercard.com/product/payment-gateway-services-mpgs) (MPGS). By subscribing to notifications, payment details are available to you as soon as the transaction takes place, allowing you to take rapid follow-on action in accordance with your business processes. **The Commercial Event Notifications service currently supports the following events:** * Authorization and Clearing event for virtual cards generated by ICCP. * Authorization and Clearing event for virtual cards generated by Business Payment Controls. * ICMP Token events (Token Lifecycle event and Token Provisioning event) for virtual cards tokenized by MDES. ## How it works {#how-it-works} ### Onboarding {#onboarding} To subscribe to event notifications, you must first be enrolled to either ICCP or Business Payment Controls as an issuer, company, or partner, to create VCNs for which notifications will be raised. You can then enroll for and onboard to the Commercial Event Notifications service. As part of the onboarding process, you must provide a URL to which Mastercard will deliver notifications and you must establish a service at that URL to receive the notifications. Mastercard then sends the notifications for all your active subscriptions to that endpoint. ### Next Steps {#next-steps} See the Commercial Event Notifications [use cases](https://developer.mastercard.com/commercial-event-notifications/documentation/use_cases/index.md). ## Subscribing to and Receiving Notifications {#subscribing-to-and-receiving-notifications} Your API client interacts with the Commercial Event Notifications service to begin receiving notifications as follows. The flow outlined below represents the payment authorization event; a similar process exists for other payment events. Diagram eventseq The flow is as follows: 1. As a preliminary step, request the **fieldmappings** that you can use to specify filter criteria for your subscriptions. 2. The Event Notifications service responds with the list of fieldmappings supported, which you can inspect to identify the fields you will use in your filters. 3. Create a **subscription**, specifying the criteria under which you want to receive notifications, using the fieldmappings that you retrieved earlier. 4. The service confirms the creation of the subscription and returns its unique ID and other details. 5. As VCNs are presented, the Mastercard Network passes the supported event messages to the Event Notifications service. 6. The Event Notifications service generates notifications for those authorizations and delivers those notifications to subscribers that have registered an interest. ## API Resources {#api-resources} The Commercial Event Notifications API exposes several resources, as referred to in the above flow, that you can interact with to manage your notifications. #### Subscribers {#subscribers} Subscribers are API clients that wish to receive notifications. Subscribers are configured in the Event Notifications system during onboarding. As a subscriber, you can create one or more subscriptions to receive notifications and as notifications are generated, the service pushes those notifications to a URL registered during onboarding. #### Subscriptions {#subscriptions} You create a [subscription](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/subscriptions/index.md) to register for notifications and to specify the criteria for generating those notifications. #### Field Mappings and Specifications {#field-mappings-and-specifications} [Field mappings](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/fieldmappings/index.md) identify fields from the originating event that can be used to filter criteria for specifications. The subscriber creates specifications to define the conditions under which notifications will be generated, by specifying matching criteria for the fields. For example, a subscriber can specify that they want to receive notifications for all authorizations funded by a specific real card. #### Notifications {#notifications} [Notifications](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/notifications/notifications/index.md) contain details of events being notified, enriched with additional details. For example, payment authorization notifications for VCNs generated by ICCP contain key authorization message information and purchase request information obtained from ICCP. A notification is generated for a subscriber only when the subscriber has created an active subscription, and a [supported event](https://developer.mastercard.com/commercial-event-notifications/documentation/index.md#Overview) subsequently occurs that matches the subscription. Notifications are not generated for payments that have already occurred.