> 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/no-integration-payment-link.md).

# No Integration (Payment Link)

## Overview

**Payment Link (Finpay Link)** is a shareable URL for collecting a payment.

You create the link for a specific invoice or transaction. Customers open the link and pay on a Finpay-hosted page.

Use this when you want to accept payments without building checkout UI.

## When to use Payment Link

Payment Link is a good fit when you:

* Sell via chat, social, or manual invoicing.
* Need a fast way to collect one-off payments.
* Do not want to integrate checkout into your site or app yet.

Consider alternatives when you need tighter checkout control:

* Use [Hosted Payment](/documentation/payment-gateway/integration-method/hosted-payment.md) for a redirect checkout from your app/site.
* Use [Core API (Host-to-Host)](/documentation/payment-gateway/integration-method/core-api-host-to-host.md) for a fully native checkout UI.

## Customer experience

1. You generate a payment link for an invoice or order.
2. You share the link with the customer.
3. Customer opens the link and chooses a payment method.
4. Customer completes the payment on the Finpay page.
5. You confirm the final result using transaction status.

{% hint style="info" %}
Treat the link page as a **payment UI**. Use transaction status as the source of truth.
{% endhint %}

## Workflow

![Payment Link workflow](https://hub.finpay.id/assets/images/workflow_invoice-5dc9fb1e4cbb78b7da728e585620495c.webp)

## Common use cases

* Invoice payment links.
* Payment reminders via email, SMS, or WhatsApp.
* Collecting deposits and down payments.
* Offline-to-online payments (store staff shares a link).


---

# 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/no-integration-payment-link.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.