> For the complete documentation index, see [llms.txt](https://docs.vodlix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vodlix.com/user-manual/admin-area/paid-subscriptions/linking-subscription-plans-with-payment-gateways.md).

# Linking Subscription plans with Payment Gateways

After successfully creating a new package, the admin has to link that package to the payment gateways.&#x20;

![](/files/-MVLxXgW8fP18h2pAcc6)

Admin can link that package to all the payment options or with any of the following.&#x20;

1\) PayPal\
2\) Stripe

![](/files/-MVLxllAsPnBBGG4IFed)

After submit, the create linked payment gateway would show in the list on the same page. These plans work with your payment gateway API for recursive payments.

Once a subscription plan is active users can subscribe to it from the frontend. After a user registers and login, they will have to subscribe to a plan to stream content.


---

# 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.vodlix.com/user-manual/admin-area/paid-subscriptions/linking-subscription-plans-with-payment-gateways.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.
