> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/ja/nitsuitebitaidesuka/platform-features/finance/payments-withdrawals-and-balance/payout-setup/limitations-of-withdrawals-via-intermediary-banks.md).

# 中継銀行経由の出金の制限

パートナーとして、impact.comで中継銀行を利用して出金する際の制限と可能性を理解しておくことが重要です。

<div data-with-frame="true"><figure><img src="https://3659882269-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-4b5234c684a059bdf00cd9ce363b9675964a8ea4%2F60ae8f6762071e84a60b26598d6fef0093eae1ee1c694065455c8593c2de1530.png?alt=media" alt=""><figcaption></figcaption></figure></div>

## 中継銀行とは何ですか？

中継銀行とは、直接の取引関係がない2つの銀行間で国際電信送金を仲介する第三者の金融機関です。これらの銀行はコルレス銀行とも呼ばれます。

## 中継銀行を利用する場合の制限

impact.comでは出金設定時に中継銀行の情報を入力できないため、中継銀行の利用には制限があります。impact.comが処理できるのは、指定された銀行口座への直接送金のみです。中継銀行宛てに送金された場合、決済は失敗し、返金されます。

## パートナーとして中継銀行経由で出金する

出金を可能にするには、最終的な送金先の銀行情報（ご自身の銀行口座情報）を入力してください。

決済の失敗を防ぐため、銀行口座情報は必ず正確に入力してください。不明な場合は、 [サポートにお問い合わせください](https://app.impact.com/secure/mediapartner/support/customer-support-portal-flow.ihtml?execution=e2s1).


---

# 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.impact.com/partner/ja/nitsuitebitaidesuka/platform-features/finance/payments-withdrawals-and-balance/payout-setup/limitations-of-withdrawals-via-intermediary-banks.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.
