> 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.