> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/business-services/zoom-virtual-agent/pci-pal-integration-for-zoom-virtual-agent.md).

# PCI Pal Integration for Zoom Virtual Agent

Configure PCI Pal Secure Payments for secure-payment-link workflows in Zoom Virtual Agent.

This guide explains how to configure PCI Pal Secure Payments with Zoom Virtual Agent. It covers setup, payment-link configuration, and a voice agent example.

### Overview

The **PCI Pal Secure Payments for Zoom Virtual Agent integration** introduces secure payment capabilities directly into Zoom Virtual Agent, enabling AI-driven payment workflows without human agent involvement.

When a customer interacts with a virtual voice or chat agent and needs to make a payment, Zoom Virtual Agent can invoke the PCI Pal tool to generate a secure payment link. This link is then delivered to customers via SMS or email, or as a link in chat, allowing them to complete the payment on PCI Pal's secure, hosted page.

{% hint style="warning" %}
**Warning**

This integration is designed to work by sending a payment link to the customer, where the customer completes payment via the link in their web browser. This integration doesn't allow the customer to verbally speak or enter their payment card information via Dual Tone Multi Frequency (DTMF) to Zoom Virtual Agent.
{% endhint %}

This allows organizations to automate end-to-end payment journeys within a virtual agent, reducing the need to transfer customers to live agents for payment collection. The virtual agent handles the conversational flow, identifying customers, confirming the amount, and collecting non-sensitive details, while PCI Pal handles the secure payment processing. At no point does the virtual agent receive, process, or store any payment card data.

### Prerequisites

To use this integration, you must have:

* Appropriate licenses for Zoom Virtual Agent (voice and chat).
* A user account with admin permissions to configure Zoom Virtual Agent.
* Access to AI Studio with permission to add integrations.

### Initial Setup

PCI Pal integration for Zoom Virtual Agent requires an integrated app available in **AI Studio**, under the **Integrations** menu. Setup steps follow below.

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/DSEtA0zgWKGaIhPUUxLu/5d_J6ou3QombLMxU%20Q6wFg" alt=""></div>

{% hint style="info" %}
**Note**

You'll find two Zoom Apps in the Zoom App Marketplace for PCI Pal integration. Each app has a different use case.
{% endhint %}

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/NF2vhRQZnxnKcms7dCvx/xTH87EPrRp%20vecX0JvOm8w" alt=""></div>

**Option 1:**

[**PCI Pal Secure Payment Solution Contact Centers**](https://marketplace.zoom.us/apps/MxNTkUxtQYSja9I-2YbMwQ): This version enables payment facilitation by human agents in Zoom Contact Center using the Zoom App integration method.

**Option 2:**

[**PCI Pal Secure Payments, Zoom Virtual Agents**](https://marketplace.zoom.us/apps/PlJfA-OkSvGTHAdt82ZF9g): This app enables payment facilitation via Zoom Virtual Agent.

You'll want to install the appropriate app according to the use cases unique to your deployment needs. **You do not need to install both apps unless both payment integrations are required.**

{% hint style="info" %}
**Note**

For the integrations explained in this guide, along with the example use case, you must connect the **PCI Pal Secure Payments, Zoom Virtual Agent** app in AI Studio under Integrations. You do not need to install the app directly from the Zoom App Marketplace.
{% endhint %}

#### Connecting the Integration to Zoom Virtual Agent

1. Browse to [zoom.com](https://www.zoom.com/) and sign in.
2. Navigate to **AI Studio > Integrations**.
3. Scroll to the bottom of the page and click the link to **View all marketplace tools integrations**.
4. Locate the **PCI Pal Secure Payments, Zoom Virtual Agents** app.

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/DSEtA0zgWKGaIhPUUxLu/5d_J6ou3QombLMxU%20Q6wFg" alt=""></div>

4. Click the **Connect** button. You will be asked to provide information about your PCI Pal account to complete the setup.

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/nQmdhDyVDhcrnZB71vj9/IFio5qZ6TlinicaaUVQhmQ" alt="" width="563"></div>

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/0VGRdYOvGSrQIF8p8N8s/fQw0eKinT02SIH5Hxm5LHg" alt="" width="563"></div>

{% hint style="info" %}
**Note**

PCI Pal can provide you with the configuration information required in the above screenshots.
{% endhint %}

5. Return to **AI Studio > Integrations**. You should see the integration is now connected and ready with an "Active" status.

<div data-with-frame="true"><img src="https://1175968039-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2FJ3ufvqF3vSzw2DoIGnXi%2FPCI-Pal_ZVA_integrations-active.png?alt=media&amp;token=c2287e9b-36e0-4cd6-80bc-9f7264e77bc7" alt=""></div>

The PCI Pal integration is now ready to be used by your voice and chat agents.

#### Adding the Tool to a Skill

Zoom Virtual Agent can provide a payment experience to the customer by invoking a tool from within a skill.

{% hint style="info" %}
**Note**

For more information on creating tools and skills for Zoom Virtual Agent, see the Zoom Support article [Creating Zoom Virtual Agent tools](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0081099).
{% endhint %}

To add the tool:

1. Create a new Virtual Agent or modify an existing one.
2. Create or modify a **Skill**.
3. Press the **/ (forward slash)** key to open the **variable, tool, and skill menu**.
4. Select **Tool**, then scroll down to locate the **PCI Pal marketplace entry**.
5. Select the **PCI\_Pal\_Create\_a\_Payment\_Link** tool from the menu.

<div data-with-frame="true"><img src="https://1175968039-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2FvE9VuAIQGsjHEMWMzWs9%2FPCI-Pal_ZVA_create-skill-newest.png?alt=media&amp;token=1969411a-4bc5-4927-98a8-d1f1b3d3e06f" alt=""></div>

6. Give the tool a name and description.
7. Configure the **Parameters and Responses** information.

You can use the information tables found in the following section to configure the tool.

**Parameters**

Parameters serve as inputs to the PCI Pal tool to generate a payment session. Some of these parameters are mandatory while others are optional. Much like other tools you may be using, these inputs can be either:

* Static values
* Mapped from variables
* Collected via LLM

The list of available fields in the following tables represent all potential information that may be required to facilitate payment. The customer must work with PCI Pal and their Payment Services Provider (PSP) to determine which fields are required for their unique scenario.

{% hint style="success" %}
**Tip**

If you're asking the customer to make a payment, it's safe to assume you've already identified who's calling, have checked their order status, and so on. Use additional skills and tools to store this information using global variables for reference within the PCI Pal tool.
{% endhint %}

| Variable Name  | Requirement | Description                                                                                                                                                                                                                                          |
| -------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `flowId`       | Mandatory   | <p>The unique <code>flowId</code> for your PCI Pal payment workflow. This number is supplied in your PCI Pal setup guide.</p><ul><li><strong>Note:</strong> You must work with PCI Pal to identify the correct ID for the payment journey.</li></ul> |
| `reference`    | Mandatory   | A field to apply a custom reference to the payment. This will be included in any payment webhooks in agreement with PCI Pal.                                                                                                                         |
| `amount`\*\*   | Mandatory   | <p>The amount to be paid. Supply it in the format specified in your PCI Pal setup guide.</p><ul><li><strong>Note:</strong> You only need to specify a value. No currency is needed.</li></ul>                                                        |
| `currency`     | Optional    | The currency formatted in ISO 4217 format (USD/GBP). This is an optional field. Check your PCI Pal setup guide for specifics or requirements.                                                                                                        |
| `firstName`    | Mandatory   | The customer's first name. You may be requested to send both first and last names of the cardholder in a single field. Check your PCI Pal setup guide.                                                                                               |
| `lastName`     | Mandatory   | The customer's last name. You may be requested to send both first and last names of the cardholder in a single field. Check your PCI Pal setup guide.                                                                                                |
| `addressLine1` | Mandatory   | The first line of the customer's address. Provide this in the format specified in your PCI Pal setup guide.                                                                                                                                          |
| `addressLine2` | Optional    | The second line of the customer's address. Provide this in the format specified in your PCI Pal setup guide.                                                                                                                                         |
| `city`         | Mandatory   | Customer address data. Provide this in the format specified in your PCI Pal setup guide.                                                                                                                                                             |
| `state`        | Optional    | Customer address data. Provide this in the format specified in your PCI Pal setup guide.                                                                                                                                                             |
| `zipcode`      | Mandatory   | Customer address data. Provide this in the format specified in your PCI Pal setup guide.                                                                                                                                                             |
| `country`      | Optional    | Customer address data. Provide this in the format specified in your PCI Pal setup guide.                                                                                                                                                             |
| `email`        | Optional    | The customer's email address. Optional. Provide only if required in your PCI Pal setup guide.                                                                                                                                                        |
| `phoneNumber`  | Optional    | The customer's telephone number. Optional. Provide only if required in your PCI Pal setup guide. The guide will also specify the required number format.                                                                                             |
| `customData1`  | Optional    | An optional, additional data field. Any data required will be specified in the PCI Pal setup guide alongside the required format.                                                                                                                    |
| `customData2`  | Optional    | An optional, additional data field. Any data required will be specified in the PCI Pal setup guide alongside the required format.                                                                                                                    |
| `customData3`  | Optional    | An optional, additional data field. Any data required will be specified in the PCI Pal setup guide alongside the required format.                                                                                                                    |
| `customData4`  | Optional    | An optional, additional data field. Any data required will be specified in the PCI Pal setup guide alongside the required format.                                                                                                                    |
| `customData5`  | Optional    | An optional, additional data field. Any data required will be specified in the PCI Pal setup guide alongside the required format.                                                                                                                    |

{% hint style="info" %}
**Note**

The `additionalField1`, `additionalField2`, and `additionalField3` fields are placeholders that allow custom values. For example, a customer's PSP may require bespoke flight information such as the origin airport, destination airport, and flight number. These fields offer a way to capture such bespoke information.
{% endhint %}

{% hint style="warning" %}
**\*\*Additional guidance for the `amount`** **field**:

The `amount` field **must** be populated with the amount that the customer will pay.

There are **two elements** to a payment amount that need to be considered: **Currency** and **Value**.

| Currency                                                                                                                                  | Value                                                                                                              |
| ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| <ul><li>The currency is based on ISO4217 format (GBP, USD, etc.) and will be configured by PCI Pal within the payment workflow.</li></ul> | <ul><li>The payment amount and the format is important and the format will be set by the customer's PSP.</li></ul> |
| <ul><li><strong>You do not need to include the currency</strong>.</li></ul>                                                               | <ul><li><strong>The value must be in the correct format</strong>.</li></ul>                                        |

The PSP may require the amount to be defined using the smallest possible unit of measurement, such as pennies, cents, and so on. This helps avoid the possibility of decimal math errors. For example:

* 100 = 100 pence = £1
* 1638 = 1638 cents = $16.38

**You must work with PCI Pal and your PSP to determine how the payment amount will be presented during the payment workflow**.
{% endhint %}

{% hint style="success" %}
**Tip**:

Capturing the customer's phone number and email address facilitates the delivery of the payment link. Combine the PCI Pal skill with the SMS and/or Email tool in to send the link to the customer (particularly useful for voice agent use cases).
{% endhint %}

**Responses**

| Variable Name        | Requirement | Description                                                                                                                                                          |
| -------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Id`                 | Optional    | The unique identifier (GUID) for the generated payment session. This is used primarily for logging and providing it to PCI Pal support for troubleshooting purposes. |
| `LinkId`             | Optional    | Not required for the current implementation, but included for possible future use.                                                                                   |
| `DigitalSessionLink` | Mandatory   | The payment session link                                                                                                                                             |

{% hint style="info" %}
**Note**

The `DigitalSessionLink` field contains the payment link the customer will require. Use the SMS or Email tool to send the link using a phone number or email address captured during the customer contact.
{% endhint %}

### Using the Voice Agent

This section will walk you through a hands-on example configuration of a payment workflow using a voice agent. This walkthrough also applies to Zoom Virtual Agent chat agents.

In this example, the customer is calling to find out where their order is, and the voice agent advises them that the order has been delayed because of an outstanding balance. The agent then provides the customer with the opportunity to settle their balance using PCI Pal's payment workflow.

For this example, you'll need:

* A working SMS configuration in Zoom Contact Center
* An email account attached to Zoom Virtual Agent
* An existing knowledge base repository

{% hint style="info" %}
**Note**

Configuring SMS for Zoom Contact Center, attaching an email account to Zoom Virtual Agent, and setting up a knowledge base are beyond the scope of this document. See [Zoom Support](https://support.zoom.com/hc/en) for more information.
{% endhint %}

#### Creating a Voice Agent

For this use case you'll create a simple voice agent:

1. Log in to the Zoom Admin Center.
2. On the left-hand side of the screen, select **Product configuration > AI Studio > Virtual Agents**.
3. Click the **Add Virtual Agent** drop-down button and select **Instruction based**.
4. Click **Start from blank** in the pop-up window that appears.
5. Create a new **Instruction Based** voice agent, starting from a blank template.
6. Enter the following details in the **Create agent** workflow window:
   1. Click the **Chat** modality to deselect it. Only the Voice modality is required in this example.
   2. In the **Agent name** text box, enter "Order Agent." Click **Next**.
   3. **Guidance**: "You're a friendly agent responsible for helping customers with their orders and payments. APIs will present outstanding balances in pence. When presenting these to a customer you must read them in pounds and pence (e.g., 1000 is £10) but do not modify the value returned by the API." Click **Next**.
   4. Select the primary voice and language for your agent from the available options. Click **Next**.
   5. Select a knowledge base from the **Use existing source** list. Click **Next**.
   6. (Optional) Choose one of the available Skills from the final step of the workflow.
   7. Click **Create**.

{% hint style="info" %}
**Note**

A production agent would include comprehensive guidance and guardrails. For this example, the focus is on creating the payment journey. This example agent doesn't include additional guardrails.
{% endhint %}

#### Configuring Global Variables

You'll require several variables to facilitate this use case. Configure these as follows:

1. Log in to the Zoom Admin Center.
2. Navigate to **AI Studio → Virtual Agents**.
3. Click the **Preferences** tab at the top of the screen.
4. Click the **Variables** icon.
5. Create a Custom Variable Group by clicking the **+Add custom group** link at the bottom of the column.
6. Name the custom variable group "**payment**."
7. Click **Add**.

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/DXq8qXjjaFBQFYvcGz74/u7rlhrq7QtST0ArDSeXs2A" alt="" width="563"></div>

8. Click on your newly created custom group, then click **+Add variable** in the top-right corner of the screen.
9. Create the following variables:

| Variable Name | Type   | Value     |
| ------------- | ------ | --------- |
| email         | String | Undefined |
| phone         | String | Undefined |
| link          | String | Undefined |

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/lUEIdN2SnrSuvxGVZ9OS/IZU9LAQ0Qte8Kop2zhMWLg" alt=""></div>

#### Editing the Existing Voice Agent

After configuring the variables, you'll need to return to the voice agent and create skills to facilitate order lookup and secure payments.

1. Navigate to **AI Studio → Virtual Agents → Agents**.
2. Modify the voice agent you created earlier.
3. Scroll down to the **Skills** section of the voice agent configuration.
4. Move on to the next sections to create two skills.

**Creating an Order Update Skill**

Next, create a skill to provide customers with information about their recent orders. You'll use static JavaScript code to simulate an API call to return fictitious order information.

1. Click **+Create skill** and create an **Instruction-based skill**.
2. Enter the following details:
   1. Name: Get order details
   2. Trigger: Use this skill to retrieve information about a recent order
3. In the Instructions window, press the **/ (forward slash)** key.
4. Select **Tool** and click **Create a new tool**.
5. Click **Custom script**.
6. Enter the following details:
   1. Name: `get_order_details`
   2. Description: To retrieve information about orders
   3. JavaScript: Use the code block below:

```javascript
async function main() {
  return {
    "firstName": "Ben",
    "lastName": "Williams",
    "deliveryAddress": "71 MidCity Place",
    "city": "London",
    "postcode": "WC1V 6EA",
    "orderStatus": "delayed",
    "statusReason": "balance outstanding",
    "outstandingBalance": "12557"
  }
}
```

This code will simulate an API call, providing details about a fictitious order with an outstanding balance. The information in this response will feed into the parameters configured as 'Collect via LLM' when you create the PCI Payment tool.

7. Click **Create**.
8. Complete the skill's instructions using the following text:

```plaintext
1. Ask the customer for their order number
2. Retrieve the order details
3. Provide information to the customer
```

9. Your skill configuration should look like the following image:

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/Zds5crLZ34meVO1AHwz0/x2MUvzTjR2CMfuQqHMMEmw" alt="" width="563"></div>

10. Click **Add**.

**Creating a Payment Skill**

Next, you'll create a skill that uses the pre-built PCI Pal Marketplace tool to generate a secure payment link. This sends the link to the customer, who can then provide payment information on the secure payment page.

{% hint style="success" %}
**Tip**

When the Order Update skill identifies an outstanding balance, the virtual agent can automatically invoke this skill.
{% endhint %}

1. Click **+Create skill** and select the option to create an **Instruction-based skill**.
2. Enter the following details:
   1. Name: Take payment
   2. Trigger: When the customer needs to pay for goods or services
3. In the Instructions window, press the **/ (forward slash)** key.
4. Select **Tool**, and then scroll down to locate the PCI Pal marketplace entry.
5. Select **PCI Pal - Create a Payment Link** tool from the menu.
6. Enter the following details:
   1. Name: `create_payment_link`
7. Scroll down to the **Parameters** section.
8. Delete all optional parameters except `addressLine2`, `state`, `email`, and `phoneNumber`, then configure the parameters as follows:

{% hint style="info" %}
**Note**

Any fields not listed in the following table should be deleted from the tool. Unlisted fields aren't required for this use case.
{% endhint %}

<table><thead><tr><th width="142">Name</th><th>Value Source</th><th width="104">Set Value</th><th width="90">Value</th><th>Map to Variable</th></tr></thead><tbody><tr><td><code>flowId</code></td><td>Set Manually</td><td>Static value</td><td>2213</td><td>N/A</td></tr><tr><td><code>reference</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td><code>amount</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td><code>firstName</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td><code>lastName</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td><code>addressLine1</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td><code>addressLine2</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td><code>city</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td><code>state</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td><code>zipcode</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td><code>email</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td><code>global_custom.payment.email</code></td></tr><tr><td><code>phoneNumber</code></td><td>Collected via LLM</td><td>N/A</td><td>N/A</td><td><code>global_custom.payment.phone</code></td></tr></tbody></table>

9. Scroll down to the **Response** section.
10. Delete all parameters apart from `DigitalSessionLink` which you should then configure as follows:
    1. Description: The unique payment link
    2. Map to variable: `global_custom.payment.link`
11. Click **Save and add**.
12. In the Instructions window, press the **/ (forward slash)** key again.
13. Add the **SMS** tool and configure as follows:
    1. Sender phone number: Select an appropriate number from the drop-down list.
    2. Recipient number: From variable
    3. Variable: `global_custom.payment.phone`
    4. Content: Please use this secure payment link
       1. Press the **/ (forward slash)** key at the end of this string and locate the `global_custom.payment.link` variable.
14. The SMS tool should look like similar to the following image:

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/w8KGYua82UYwmlLSemH5/wwn4xbqQTp2Y18mx8rFSng" alt=""></div>

15. Click **Save and add**.
16. In the Instructions window, press the **/ (forward slash)** key again.
17. Add the **Email** tool and configure as follows:
    1. Sender email account: Select one of your connected email accounts.
    2. Recipient email address: `global_custom.payment.email`
    3. Email template:
       1. Subject: Your secure payment link
       2. Body: Please use this secure payment link
          1. Press the **/ (forward slash)** key at the end of this string and locate the `global_custom.payment.link` variable.
18. The Email tool should look like the following image:

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/83kXiVtXnymyHAsV98i3/hvbg6qgmSwCScq3Jbn0qBQ" alt=""></div>

19. Click **Save and add**.
20. Complete the skill's instructions using the following text:

```plaintext
1. Ask the customer whether they would prefer to receive the payment link via email or SMS.
2. Confirm the amount that they will pay.
3. If they asked for SMS, ask them for their phone number. Otherwise ask for their email address.
4. Send either an SMS or email depending on their preference. Not both. 
```

21. Your skill configuration should look like the following image:

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/tIB4UaRKRvqn7ZFx1Nwm/7BLLVYiaQnWUYZRO0NoacQ" alt="" width="563"></div>

22. Click **Add**.

### Testing the Voice Agent

At this point you're ready to test the voice agent. In the Preview window, click the **Start test** button to begin a conversation with the voice agent.

<div data-with-frame="true"><img src="https://content.gitbook.com/content/ctBXUMeBy4rtLMmMkKRG/blobs/sXXyxa9OhWr1l9Tno87o/tDCyV7buQx69AyO1hQIh_A" alt=""></div>

{% hint style="info" %}
**Note**

You can use any number for the order number. The same order will be returned each time. The order number you enter will be used as the payment reference by the PCI Pal payment tool.
{% endhint %}

The following is an example of agent and customer dialogue for reference:

> **Agent:** Hi! Thanks for calling. I’m your virtual assistant. How can I assist you today?
>
> **Customer:** Hello, my order hasn't arrived, could you check it for me please?
>
> **Agent:** Sure, I can help with that. Could you please provide your order number?
>
> **Customer:** Yes, it's 1234.
>
> **Agent:** Thank you. Let me look into that for you.
>
> **Agent:** Your order is delayed because there is an outstanding balance of one hundred twenty-five pounds and fifty-seven pence.
>
> **Agent:** Would you like to pay this now to release your order?
>
> **Customer:** Yes please.
>
> **Agent:** Thank you. I'll help you get that sorted.
>
> **Agent:** Would you like to receive the payment link by email or text message?
>
> **Customer:** Email, please.
>
> **Agent:** Could you provide your email address so I can send the payment link?
>
> **Customer:** Yes, it's <example@example-email.com>.
>
> **Agent:** Thank you. Please confirm, you will pay one hundred twenty-five pounds and fifty-seven pence. Is that correct?
>
> **Customer:** Yes.
>
> **Agent:** Thank you for confirming. I also need your phone number to process the payment. Could you please provide it?
>
> **Customer:** Yes, it's 555-555-1234.
>
> **Agent:** Thank you for providing your phone number. The payment link will be sent to your email address. Please check your inbox and follow the link to pay one hundred twenty-five pounds and fifty-seven pence.

{% hint style="warning" %}
**Warning**

Notice how the voice agent identifies that the customer has an outstanding balance and automatically pivots to the payment skill.
{% endhint %}

To finish testing, check your test SMS or email account and click on the payment link. When prompted, you can use the following card details:

* **Card Number**: 1111 2222 3333 4444
* **Expiry**: Any 4-digit month/year in the future (e.g., 1228)
* **Security**: Any 3-digit number (e.g., 123)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.zoom.com/business-services/zoom-virtual-agent/pci-pal-integration-for-zoom-virtual-agent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
