Configure payment profiles
Important
Power Virtual Agents capabilities and features are now part of Microsoft Copilot Studio following significant investments in generative AI and enhanced integrations across Microsoft Copilot.
Some articles and screenshots might refer to Power Virtual Agents while we update documentation and training content.
Applies to: Dynamics 365 Contact Center—embedded, Dynamics 365 Contact Center—standalone, and Dynamics 365 Customer Service
You can create payment profiles to enable conversational commerce for supported channels. Once configured, your agents can help customers complete secure transactions without having to leave the messaging experience.
After you create a payment profile record, you must add it to a channel instance within a workstream's channel setup to make it work. Conversational commerce is supported for Apple Messages for Business.
Create an Apple Messages for Business payment profile for Apple Pay
Prerequisites
Verify that you have permissions on the secure columns. More information: Configure permissions to access secure columns
Before adding an Apple Pay payment profile, make sure to complete the Apple Pay integration steps documented by Apple. More information: Apple Pay - Apple Messages for Business
Create an Apple Pay payment profile
In the site map of Customer Service admin center or Contact Center admin center app, select Customer settings, and then select Manage for Payment profiles. A list of existing records is shown.
Select Add at the top of the page to create a new record.
In the Create new payment profile pages, provide the following details:
- On the Channel type page, enter a name and select Apple Messages for Business as the channel type. By default, the only channel type currently supported is Apple Messages for Business.
- On the Channel type page, enter a name and select Apple Messages for Business as the channel type. By default, the only channel type currently supported is Apple Messages for Business.
On the Details page, provide the following information:
Merchant friendly name: The customer-facing name of your business. This name is what your customer sees within the Apple Pay request. This name shouldn't be localized.
Merchant ID: Your unique identifier assigned to your business when registering as a merchant for Apple Pay.
Merchant certificate: A certificate associated with your merchant ID, used to secure transaction data. Apple Pay servers use the certificate’s public key to encrypt payment data.
Certificate password: The private key used to generate secure Apple Pay sessions.
Payment gateway URL: The endpoint where payment information and requested contact information and sent to be processed.
Merchant domain URL: The website domain associated with your Apple Pay Merchant Account.
Merchant two-letter country code: Country codes are formatted by their ISO 3166-1 alpha-2 code. Use the country code for where payments are processed.
On the Payment options page, provide the following information:
Merchant capabilities: The payment types you can accept. 3D Secure is required for channel support.
Supported Networks: The networks that support transactions between your Apple Pay merchant account and card issuers.
On the Rich messages page, select Add, and then select one or more Apple Pay rich messages to associate with this authentication setting.
An Apple Pay-type rich message may be associated to more than one payment profile. This association is because each channel instance may only support one payment profile.Review the Summary page, and then select Finish. The authentication setting is configured.
Add a payment profile to an Apple Messages for Business channel
Open the workstream containing the channel instance for which you want to enable Apple Pay.
On the User features page of the channel settings, navigate to Apple Pay, enable the capability, and select the correct setting from the dropdown. More information: Configure an Apple Messages for Business channel instance
Save your changes.
Review or update the Apple Pay settings for any channel instance by selecting Edit.
Limitations
Description | Limitation |
---|---|
Country code: The two-letter ISO 3166-1 alpha-2 code that denotes which country payments are processed in. | China isn't currently a supported country, as payments must go through a separate payment endpoint. |
Merchant capabilities: Capabilities for processing payments | - It isn't currently possible to enable support for China UnionPay. - You can build an adaptive card by adding a skill through Copilot Studio. More information: Use Microsoft Bot Framework Skills in Copilot Studio - Adaptive card styling isn't supported. |
Supported networks: This property constrains the payment methods that the user can select to fund the payment. | - Supported networks are currently limited to American Express, Visa, Discover, and Mastercard. - Some locally issued cards may not work even when the Merchant two-letter country code is correct. The following countries/regions may be impacted: Saudi Arabia and China. |
Related information
Configure Apple Messages for Business
Understand and create workstreams
Configure automated messages
Configure a post-conversation survey
Skill-based routing
Create message templates
Templates
Delete a configured channel
Support for live chat and asynchronous channels