> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/guides/javascript/format-payment-page.md).

# Format payment page

To format the payment page using the style attributes:

{% stepper %}
{% step %}
Add the `ClearentSDK.init()` method.

{% code overflow="wrap" lineNumbers="true" %}

```js
<script type="text/javascript">
    ClearentSDK.init({
        "baseUrl": "https://gateway-int.clearent.net",
        "pk": "YOUR PUBLIC KEY GOES HERE",
        "styles": ".form-control{color: blue;}.form-control:focus{color: purple;}"
    });
</script>
```

{% endcode %}

The payment form displays the blue text for input fields, and the text changes to purple when the field is selected for input

<figure><img src="https://content.gitbook.com/content/yN9CLsR8tlS8G8avRMB5/blobs/vJWKLjaMC2guXGLb37kg/image.png" alt=""><figcaption><p>Payment form fields</p></figcaption></figure>
{% endstep %}

{% step %}
Access the element classes, IDs, and structure from the browser’s Developer toolbar to build any override styles for your payment page.

<figure><img src="https://content.gitbook.com/content/yN9CLsR8tlS8G8avRMB5/blobs/T0r9Nmz93QN2gjLfsmft/image.png" alt=""><figcaption><p>Browser's developer toolbar</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The following error will be displayed when you set an external resource or data/blob content in the style attributes during formatting the content.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/yN9CLsR8tlS8G8avRMB5/blobs/3mhDyOKTxwgWU7yB5gT6/image.png" alt=""><figcaption><p>Error from the browser's developer toolbar</p></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 by asking a question.

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

```
GET https://docs.xplorpay.com/guides/javascript/format-payment-page.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.