> 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/cn/ji-fei-yu-fu-kuan/what-forms-of-payment-do-you-accept.md).

# 你们接受哪些付款方式？

了解 Oxylabs 订阅和服务支持的付款方式。

我们接受以下付款方式：

* 信用卡支付
* PayPal
* Google Pay
* Apple Pay
* 银行转账（通过销售或客户经理团队）

我们绝不会直接存储您的卡片详情。所有结账和付款方式管理都通过您的服务提供商安全的托管界面进行。

{% hint style="info" %}
请注意，我们不接受加密货币支付。
{% endhint %}

### 管理付款方式

如果您需要添加、更新或移除付款方式，请按以下步骤操作：

1. 前往 **账单与支出** 中的 [仪表板](https://dashboard.oxylabs.io/en/).
2. 点击 **管理订阅** 以打开您的账单门户。
3. 在那里，您可以添加新的付款方式、设为默认，或移除现有付款方式。

<img src="https://523389500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpGNgdeKVOM3XvAaPheYj%2Fuploads%2FCThuAztk9axLdA81hg22%2Funknown.png?alt=media&amp;token=1ce6ef9d-de3a-4384-a5d6-7fbd82f56cab" alt="" height="164" width="624">

<img src="https://523389500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpGNgdeKVOM3XvAaPheYj%2Fuploads%2F5JOAaj60Nf3WHWGsMdtz%2Funknown.png?alt=media&amp;token=8fae8e5b-7165-4c59-90e9-b72ef0edd3c8" alt="" height="348" width="624">

{% hint style="info" %}
“管理订阅”选项仅对拥有有效套餐订阅的用户显示。
{% 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/cn/ji-fei-yu-fu-kuan/what-forms-of-payment-do-you-accept.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.
