> For the complete documentation index, see [llms.txt](https://docs.finpay.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finpay.id/documentation/payment-gateway/integration-method/hosted-payment.md).

# Hosted Payment

## Overview

**Hosted Payment** is a Finpay-hosted checkout page. You redirect the customer to Finpay to choose a payment method and complete payment. Use this when you want a fast integration with minimal checkout UI work.

## When to use Hosted Payment

Hosted Payment is a good fit when you:

* Want to go live quickly.
* Prefer a Finpay-managed payment UI.
* Need one flow for multiple payment channels.
* Want Finpay to handle channel-specific payment channel instructions.

{% hint style="info" %}
Consider **Core API (Host-to-Host)** when you need full control of the checkout UI.
{% endhint %}

## Customer experience

1. Customer starts checkout in your app or website.
2. You redirect the customer to the Finpay hosted payment page (URL).
3. Customer selects a payment method on the Finpay page.
4. Customer completes payment using the chosen channel.
5. Finpay returns the customer to your site/app (redirect).
6. You confirm the final result using the transaction status.

{% hint style="info" %}
Always treat the redirect as a **customer navigation event**, not a final payment confirmation. Use transaction status for reconciliation.
{% endhint %}

## Supported payment methods

Payment methods depend on your merchant profile and configuration.

See the full list in [Payment Channels](/documentation/payment-gateway/payment-channels.md).

## Common pitfalls

* **Assuming redirect = paid**. Redirect is not a final confirmation.
* **Not handling pending states**. Some channels confirm instantly, others can take time.
* **Not handling expiry**. Unpaid transactions can expire based on channel rules.
* **Not showing a clear “payment in progress” state** after redirect back to your site/app.

{% hint style="warning" %}
If you need exact redirect parameters, expiry behavior, or status mapping, align with Finpay for your environment configuration.
{% endhint %}


---

# 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.finpay.id/documentation/payment-gateway/integration-method/hosted-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.