Ask for Payment action
Use the Ask for Payment action in digital bot flows to request payment from a customer who is purchasing goods and services through a digital messaging channel. For example, when a customer is interacting with a digital bot through the Apple Messages for Business channel, the customer can use Apple Pay to make the payment.
Field | Description |
---|---|
Name |
The label you enter here becomes the name of the action in the flow. |
Currency |
Select a currency code for the payment from the drop-down list. |
Country Code |
Select a country code for the payment from the drop-down list. |
Payment Platform |
Select the payment platform through which the transaction must occur. Note: As the Ask for Payment action is currently available for Apple Messages for Business only, the payment platform is also limited to Apply Pay. |
Line Items |
Optionally, you can split the total payment value into line items that explain payments and additional charges. For example, if you want to indicate any additional charges, discounts (negative value), or estimated tax amount as part of the total value. You can add up to 10 line items. In Literal mode, click Line Item to add a new line item. Then, customize each line item using the following fields:
|
Shipping Options |
Optionally, define a list of the available shipping methods. You can add up to four shipping options. In Literal mode, click Shipping Option to add a new shipping option. Then, customize each shipping option using the following fields:
Note: The Apple Pay payment message displays the first shipping option from the list as the default shipping method. |
Total Price |
Set the total amount for the customer to pay. Click Increase or Decrease to adjust the amount, or manually enter the amount. Note: Ensure that the total cost is the sum of all subtotals that you defined in the line items. |
Contact Information |
List the contact details that the customer must fill in before they can make the payment. Click String to add one of the following pre-defined fields:
|
Received Message |
Customize the message that the customer receives when the digital bot sends the payment request. To customize the received message, click the Received Message tile and perform the following steps:
Note: If no image is configured for the received message when using Apple Messages for Business, the default Apple Pay icon is used. |
Reply Message | Customize the title of the reply message that the bot receives after the customer interacts with the payment request. |
Payment Completion Timeout |
Set the timeout before which the customer must complete the payment. If this timeout expires, the flow triggers a No Input event. Click Increase or Decrease to adjust the timeout, or manually enter the timeout. |
No Match |
Enter the communication that the bot produces when the user’s input is not a valid match. Note: The bot returns the content from Settings > User Input > No Match Detected > No Match Apology, combined with the No Match communication. |
Customize No Match |
Enables the No Match Reprompts field. Use this option to create a list of no match prompts that incrementally occur when the bot receives No Match input events. |
No Match Reprompts |
When the bot receives a No Match input, the bot returns the communication in the No Match Reprompts collection that corresponds to the current number of No Match inputs received for that action. For example, the first No Match input triggers the bot to use the first No Match reprompt in the defined collection. The length of the No Match Reprompt collection overrides the maximum number of No Match retries that you define at Settings > User Input > No Match Detected > Maximum Number of No Match Retries for that particular action. For example, if you define two reprompts in the collection, the bot retries twice. An empty collection turns off No Match retries. Note: The bot returns the Settings > User Input > No Match Detected > No Match Apology combined with the corresponding No Match Reprompt communication. |
Default No Match |
Enables the default No Match field. Use this option to define a single No Match prompt that the bot produces when it receives No Match input events. |
Paths |
Note: If you disable this path, then the flows that you configure for the output path are hidden, not deleted. |
Define success and failure paths
Path | Description |
---|---|
Success |
This path indicates that the system successfully processed the payment. To follow the route you want the interaction to take, drag the appropriate action below the Success path. |
Failure |
This path indicates that the system was unable to process the payment. To direct the route you want the interaction to take, drag the appropriate action below the Failure path. |