> For the complete documentation index, see [llms.txt](https://apidocs.paygateway.paytota.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.paygateway.paytota.com/hosted-checkout-card-payment.md).

# Hosted Checkout Card Payment

A **hosted card checkout payment** is a payment transaction in which your customer has authorized you to take money from their card using their full card details. However, the **`Card`** details are provided by the customer when they are making payment during the final checkout process from the web browser.

Posting a hosted card checkout request is the same as posting a card payment however the **`request_type`** parameter will have to be specified as `HPP`. By providing this field, Paytota Paygateway will know that the transaction is a hosted card checkout payment.

## Providing `request_type`

#### **1. Create JSON of the Card details**

{% tabs %}
{% tab title="Data" %}

```javascript
{
    ...,
    "request_type": "HPP",
    ...
}
```

{% endtab %}

{% tab title="Description" %}

| Parameter     | Type | Description                                                                                | Required |
| ------------- | ---- | ------------------------------------------------------------------------------------------ | -------- |
| request\_type | ENUM | One of these Values: `DIRECT_S2S`, `HPP`. It must be set to `HPP` for hosted page checkout | YES      |

#### Set request\_type parameter

{% tabs %}
{% tab title="Sample Request Body" %}

```javascript
{
  ...
  "request_type": "HPP"
  ...
}
```

{% endtab %}
{% endtabs %}
{% endtab %}
{% endtabs %}


---

# 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://apidocs.paygateway.paytota.com/hosted-checkout-card-payment.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.