Integrate online payment with event registration

 

Applies To: Dynamics Marketing

Microsoft Dynamics Marketing (MDM) lets marketeers integrate external payment and fulfillment systems for event registration. This feature uses landing pages for event marketing and registration. A web application hosted on the external payment or fulfillment site can request relevant context data about the event registration on demand through an authorized SDK communication channel. That site can obtain payment from the contact, and then complete event registration through the MDM SDK API. The external site could also cancel the registration, or perform some other required operation.

System_CAPS_noteNote

This feature requires Microsoft Dynamics Marketing 2016 Update 0.3 or later.

For detailed information about setting up MDM and the external payment or fulfillment system refer to the documentation provided below.

The event registration configuration includes a registration link URL for the external system that is redirected to when the user (contact) submits the event registration landing page. A token parameter is appended to that URL that allows access to the event registration data in MDM from the destination web application page on the external system. The external system uses the provided single-use token and the MDM SDK API to obtain event registration contextual information and then perform the desired MDM actions.

Online payment  with event registration process flow in Dynamics Marketing

For more information about this feature see Set up registration items for events.

The following sections provide information about how to obtain the token, access MDM context data for the event registration, and perform actions in MDM.

  

The token is passed to the web application page of the external payment or fulfillment system as an added parameter on its URL This is done after the user submits the landing page. For example, given the following event registration link value:

www.contoso.com/payhere/

The token is appended to that URL as a parameter.

http://www.contoso.com/payhere/?token=37079543-d6a8-47cb-be4a-e883f9879855

The web application can parse the token from the URL and use it to access MDM context data about the event registration. The token is for a single use only and has a lifetime of 24 hours. Another token can only be obtained by the user re-submitting the landing page.

Once your web application has the token it can use the MDM SDK API to obtain all event registration information provided in the landing page. This is done by using RetrieveSubmissionRequest and providing the token value from the registration link in the Token property.

Event registration submission request class diagram in Dynamics Marketing

Once your web application has obtained the data context, it can then perform whatever operations are required. For example the service can display (for verification) the details of the event registration to the user before allowing the user to enter payment info and pay for the event. After payment is received, create the event registration by using CreateOrUpdateEventRegistrationRequest. The page could also allow the user to cancel the registration and then cancel the registration in MDM using CancelEventRegistrationRequest.

Event registration in MDM defines the URL to access the external payment or fulfillment system and provides the end user event registration experience through a landing page.

Event registration and landing page in Dynamics CRM

When you fill out the event registration form in MDM, be sure to provide the link to your external payment or fulfillment application page in the Registration link field. If the registration link is not provided, the external web application for payment or fulfillment is not accessed.

The landing page is for registration of a ticket. The landing page is what the end user—the contact who is registering for the event—sees. This page is created interactively in MDM. When presented to the user as part of the event registration process, the user does not see the external registration link on the landing page. When the user submits the landing page, MDM redirects to the external web application page defined by the registration link to complete the event registration payment or fulfillment.

For information about creating landing pages, see Create and customize landing pages.

You can use marketing automation to register contacts for events. Use RetrieveSubmissionRequest to get the landing page submission, and then use RetrieveEventRegistrationsRequest based on the information provided in the submission. Finally, you would process each event registration as described previously in this topic to complete the registration.

For more information refer to Set up registration items for events in the section named "Register contacts with Dynamics Marketing campaign automation".

Show: