> For the complete documentation index, see [llms.txt](https://help.listly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.listly.io/docs/ja/support/faq/payment-and-refund/karapaypaldeoutosurutonaergashimasu.md).

# 海外からPayPalで支払おうとすると、不明なエラーが発生します。

海外のカードを使用したり、母国以外からサブスクリプションを購読しようとする際に、お支払いに問題が発生していますか?

[代替決済方法](https://www.listly.io/pricing?highlight=paypal-alternative)をお試しください。DoDo Paymentsをご利用の場合、お客様の所在地に基づいて自動的に税金が適用されることにご注意ください。これは一回限りのお支払いであり、自動更新されません。

{% hint style="info" %}
**ヒント**

まずブラウザを切り替えることをおすすめします。Safariをご利用の場合は、Chromeをお試しください。Chromeをご利用の場合は、Firefoxをお試しください。ブラウザを切り替えた後もエラーが続く場合は、ListlyアカウントIDを添えて <hello@listly.io> までメールをお送りいただき、お支払いリンクをリクエストしてください。お客様のサブスクリプションプランを確認し、カスタム請求書をお送りいたします。
{% 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://help.listly.io/docs/ja/support/faq/payment-and-refund/karapaypaldeoutosurutonaergashimasu.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.