> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/journeys-and-pages/pages/add-payment-page-links-to-zuora-email-templates.md).

# Add Payment Page Links to Zuora Email Templates

You can embed a link to a PeakCommerce **payment page** in Zuora's email templates (for example invoice or dunning emails) so customers can pay directly from the email.

## 1. Get the payment page URL

In **Content → Pages**, open the **Payment**-type page you want customers to land on and copy its public URL (its `/s/…` link). That's the address you'll link to from Zuora.

> To pre-fill the page for a specific customer or invoice, use the page's prefill URL parameters (see the journey's **Cart prefill URL parameters**). Confirm the exact parameters your payment page accepts before building the link.

## 2. Edit the Zuora email template

In Zuora, go to **Settings → Billing → Setup Profiles, Notifications, and Email Templates**, find the template you want, and click **Edit**.

## 3. Insert the link

In the template editor, add an HTML anchor pointing at the payment page URL:

```html
<a href="https://your-domain/s/your-payment-page">Click here to make a payment</a>
```

You can style it with inline CSS, and you can pass **Zuora merge fields** as URL parameters so the link is specific to each recipient:

| Merge field                          | Value          |
| ------------------------------------ | -------------- |
| `<DataSource.Account.AccountNumber>` | Account number |
| `<DataSource.Account.Id>`            | Account ID     |
| `<DataSource.Account.CrmId>`         | CRM account ID |
| `<DataSource.Invoice.InvoiceNumber>` | Invoice number |

## 4. Preview, test, and save

Use Zuora's **Preview** to check the link, test how it renders across email clients (Gmail, Outlook, etc.), then **Save** the template.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/journeys-and-pages/pages/add-payment-page-links-to-zuora-email-templates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.