> For the complete documentation index, see [llms.txt](https://yokifinance.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yokifinance.gitbook.io/docs/subscription-payments/for-merchant/payment-plan-page.md).

# Payment plan page

[Demo page (dev version) ](https://yoki-rps-front-end-dev.qa.aspirity.com/innmind.com/test?with_unsubscribe=true)

The purpose of this page is to allow Customers to subscribe to a product on sale by the merchant.

1. A payment plan page is created by the Yoki team upon request from the Merchant. 
2. In case the merchant needs to automate the payment plan creation we could provide the API access.
3. The page will be available at [https://pay.yoki.finance/\*merchant-name\*/\*pricing-name\*](https://pay.yoki.finance/*merchantname*/*pricing-name*) 
4. The page will have the Merchant’s logo, website link, product description, pricing, and frequency.
5. The customer connects a Web3 wallet to proceed with the payment.


---

# 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://yokifinance.gitbook.io/docs/subscription-payments/for-merchant/payment-plan-page.md?ask=<question>&goal=<endgoal>
```

`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.