Jump to: navigation, search

Creating an Apple Messages for Business Channel

Starting from the 9.0 release, Genesys Hub supports Apple Messages for Business and includes an API connector for Apple Messages for Business. This section describes how to create an Apple Messages for Business channel using Genesys Hub.

Preparing for Hub Integration

You must contact Apple and get your business ID before proceeding with channel creation in Hub. After registering with Apple and choosing Genesys as your Customer Service Provider, you are greeted with a Genesys welcome message. The welcome page shows your business ID and name.

Hub welcome page.png

You must go through a two-step process to set up your Apple Messages for Business channel in Hub. Click Continue to proceed.

  1. Hub account creation (You can skip this step if you already have a Hub account)
  2. Apple Messages for Business channel creation

1. Creating a Hub Account

The first step of deploying an Apple Messages for Business channel is to create an account within the Hub component of Social Engagement. Click Continue if you are a new user and you want to create a Hub account. Refer to the Create an Account section for instructions on how to set up an account.

You can also log in with your existing account if you are already a registered Hub user. In this case, enter your user name and password and click Login.

Hub account choices.png

2. Creating an Apple Messages for Business Service Channel

  1. The Create your Apple Messages for Business Channel screen appears after you log into Hub. By default, the channel type is selected as Apple Service Channel. The channel name and business ID are automatically populated. However, you can modify the values if required.
    Hub create ABC filled.png
  2. Click Create channel. The new channel is created and the channel update screen is displayed.
    Hub ABC Channel.png
  3. Enable Production mode.
  4. Enter your business ID in the Business IDs field.
  5. Enter a value ranging from 0 to 3600 seconds in the RPC cache timeout field. See RPC cache timeout for detailed explanation on this setting.
  6. Click Update.

After the channel is created, you can activate or suspend the channel using the Actions in the Channels screen. Inbound messages are fetched and outbound messages are sent as long as the service channel is active.

Configuring Payment Merchants for ApplePay

  1. Select Show Apple Pay Information on the channel update screen.
    HUB show merchant section.png
  2. Enter the merchant ID in the Merchant ID field. This value must be unique.
  3. Enter a merchant name in the Merchant Name field. This name must be unique.
  4. Enter the merchant domain in the Merchant Domain field.
  5. Select the business IDs that must be associated with this merchant account. You can only select business IDs that are already linked to the channel and you cannot reuse a business ID that is already associated with another merchant account.
    A merchant can be associated with multiple business IDs whereas a business ID can only be linked to one merchant.
    HUB merchant businessIDs.png
  6. Provide the PSP API key in the PSP API Key field.
  7. Enter a valid URL in the Fallback URL field. This URL is used to redirect users when there is an error in payment processing.
    HUB merchant create.png
  8. Click Create Merchant to add the merchant account. You can add multiple merchant accounts as long as Merchant ID and Merchant Name are unique to each merchant.
    HUB merchant list.png
  9. Click on the merchant ID to add verification and certification files.
    HUB merchant edit.png
  10. Upload the required certificate files using the Additional verification file and Certificate file fields. You can get the domain verification file and certificate file from https://developer.apple.com.
    HUB merchant edit addfiles.png
  11. Click Update Merchant Data.

You can delete the merchant accounts using the Delete Merchant action in the channel update screen.

This page was last edited on September 19, 2022, at 04:54.
Comments or questions about this documentation? Contact us for support!