> 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/payment-gateway/overview.md). # Overview Finpay Payment Gateway is a digital payment solution by **PT Finnet Indonesia**, designed to help businesses accept payments from customers securely and efficiently — across multiple payment channels in a single platform. Finpay supports a wide range of payment channels to ensure flexibility and convenience for your customers: * **Bank Virtual Accounts (VA)** — support for major Indonesian banks, including BPD in various region * **QRIS (Static & Dynamic)** — pay using any QRIS-enabled & selected Cross Border QR application * **Credit & Debit Cards** — support for Visa and Mastercard with secured 3DS or recurring method * **E-Money**— such as OVO, DANA, LinkAja, and ShopeePay. * **Retail Outlets & Convenience Stores** — pay via Indomaret, Alfamart, and partner networks. * **PayLater** — enable flexible payment options for customers, such as Indodana, Kredivo, and ShopeePay Later --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.finpay.id/payment-gateway/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.