> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/help-center/billing-and-payments/what-forms-of-payment-do-you-accept.md).
# What forms of payment do you accept?
Discover supported payment methods for Oxylabs subscriptions and services.
We accept payment methods listed below:
* Credit card payments
* Paypal
* Google Pay
* Apple Pay
* Wire transfers (via Sales or Account Managers teams)
We never store your card details directly. All checkout and payment-method management happens through your provider's secure, hosted interface.
{% hint style="info" %}
Please note that we do not accept cryptocurrency payments.
{% endhint %}
### Managing payment methods
If you need to add, update, or remove a payment method, follow these steps:
1. Go to **Billing & Spending** in the [dashboard](https://dashboard.oxylabs.io/en/).
2. Click **Manage subscription** to open your billing portal.
3. From there, add a new payment method, set a default, or remove an existing one.
{% hint style="info" %}
The Manage subscription option only appears to users with an active plan subscription.
{% endhint %}
---
# 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://developers.oxylabs.io/help-center/billing-and-payments/what-forms-of-payment-do-you-accept.md?ask=&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.