> 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/core-api-host-to-host.md).

# Core API (Host-to-Host)

## Overview

**Core API (Host-to-Host)** lets your system talk directly to Finpay Payment Gateway via API.

You keep the payment UI and data input inside your website or app. You do not redirect customers to a Finpay-hosted checkout page.

This model does not require you to store cardholder data. Card data should never be stored on your servers.

## When to use Core API

Use Core API when you need:

* Full control over checkout UI and UX.
* A single API integration across multiple payment channels.
* Deeper control over retries, reconciliation, and custom business logic.

Use [Hosted Payment](/documentation/payment-gateway/integration-method/hosted-payment.md) when you want the fastest go-live.

## Key integration concepts

### Authentication and access

Core API access depends on your merchant configuration.

Review the [Security](/documentation/security/overview.md) requirements early.

### Idempotency and retries

Network retries happen.

Design your integration to avoid duplicate charges and duplicate order creation.

{% hint style="warning" %}
If you are unsure how idempotency is implemented in your environment, align with Finpay before go-live.
{% endhint %}

## Supported payment channels

Channel availability depends on your merchant profile and configuration.

See [Payment Channels](/documentation/payment-gateway/payment-channels.md) for the current list and limits.


---

# 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/core-api-host-to-host.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.