transfer_create
Initiate a SEPA transfer with beneficiary by ID or inline details. Handles SCA approval through polling or pending response for further processing.
Instructions
Create a SEPA transfer. Provide either beneficiary_id (existing beneficiary) or beneficiary (inline beneficiary object with name and iban), but not both. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Optional note | |
| wait | No | Maximum seconds (0-120) to poll inline for SCA approval before returning a structured pending response. Use false or 0 for a pure two-step flow (return immediately on SCA required). Default 30. | |
| amount | Yes | Amount to transfer | |
| reference | Yes | Transfer reference | |
| beneficiary | No | Inline beneficiary object (mutually exclusive with beneficiary_id) | |
| attachment_ids | No | Attachment IDs (max 5, required for transfers > 30k EUR) | |
| beneficiary_id | No | Existing beneficiary UUID (mutually exclusive with beneficiary) | |
| scheduled_date | No | Scheduled date (YYYY-MM-DD) | |
| bank_account_id | Yes | Bank account UUID to debit | |
| vop_proof_token | No | VoP proof token from verify-payee (auto-resolved when omitted) | |
| sca_session_token | No | SCA session token from a prior call to bind a previously approved SCA challenge to this retry. When set, no polling occurs and the operation runs exactly once with the token attached. |