> For the complete documentation index, see [llms.txt](https://guides.clickatell.com/release-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.clickatell.com/release-notes/release-notes-archive/2022-release-notes/q2-2022/payments/chat-2-pay-enhancements.md).

# Chat 2 Pay enhancements

## Release Summary

The focus of this release was to allow merchants to customize and uplift the payment experience for their customers. We also addressed some bugs and completed important work with regard to data and reporting requirements.

## Release Details

### Payment page order details <a href="#order-detail-pass-through" id="order-detail-pass-through"></a>

The [Chat 2 Pay API](https://docs.clickatell.com/products/chat-2-pay/api-reference/) was updated to pass additional order information to the payment gateway's APIs. This additional order data that gets passed to Cybersource is displayed to your end-user on the payment page, providing more detailed information to your end-user.&#x20;

When a customer pays for their order, they will see a list of their order items displayed on the payment page. The order details can contain details like Product ID, Product Name, Quantity, Price, and Tax.

An example of what this might look like is shown below.  <br>

<figure><img src="/files/C8cIwZ6htIx0Wa38iajq" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
Clickatell does **not** manage a catalog system. The order details are passed to Clickatell via [APIs](https://docs.clickatell.com/products/chat-2-pay/api-reference/). The **tax** amount is handled by you and is passed through the [API ](https://docs.clickatell.com/products/chat-2-pay/api-reference/)to Clickatell.
{% endhint %}

## Custom branding

You can now upload your logo so that it shows on the payment page when your customers are checking out. You can do this on the [Payment Settings](https://clickatell.gitbook.io/chat-2-pay-user-guide/cybersource-and-salesforce/configuration-details/step-3-configure-the-extension) page.

<figure><img src="/files/Bp76Cl8l5L7m9vfIlGOQ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/RVofxhLw6KxJ9nLxIU0y" alt=""><figcaption></figcaption></figure>

Once a merchant completes the steps detailed above, the logo will be displayed on the order summary and payment confirmation page<br>

<figure><img src="/files/VFvT1rWdVIpUlx7lGeMD" alt="" width="300"><figcaption></figcaption></figure>

### Partial billing

*Billing Type* is a setting on the[ Chat 2 Pay Payment Settings configuration screen ](https://clickatell.gitbook.io/chat-2-pay-user-guide/cybersource-and-salesforce/configuration-details/step-3-configure-the-extension)that lets you decide if your customer should type in their billing details as part of the checkout experience. This applies to our current Cybersource integration.

Any customer-supplied billing information will be shown on both the Order Confirmation & Payment Summary Page.

<figure><img src="/files/VtaYKptvPQoKlL60PSLY" alt="" width="542"><figcaption></figcaption></figure>

## Merchant Descriptor

A merchant descriptor field was added to the [Payment Settings configuration screen](https://clickatell.gitbook.io/chat-2-pay-user-guide/cybersource-and-salesforce/configuration-details/step-3-configure-the-extension). This is the name that appears on both a merchant's and a customer's bank or credit card statement when a customer makes a purchase from the merchant.

<figure><img src="/files/yA6Hrq8JrDAvGdOd2MmE" alt=""><figcaption></figcaption></figure>


---

# 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://guides.clickatell.com/release-notes/release-notes-archive/2022-release-notes/q2-2022/payments/chat-2-pay-enhancements.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.