recurring_transfer_create
Create a recurring transfer with defined amount, frequency, and beneficiary. Handles Strong Customer Authentication automatically or via a session token for retries.
Instructions
Create a recurring transfer. vop_proof_token is auto-resolved via verify_payee when omitted (and sca_session_token is not provided). 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 | Transfer amount (number or decimal string; serialized as a string per the Qonto API) | |
| currency | Yes | Currency code (e.g. EUR) | |
| frequency | Yes | Transfer frequency | |
| reference | Yes | Transfer reference | |
| beneficiary_id | Yes | Beneficiary UUID | |
| bank_account_id | Yes | Bank account UUID to debit | |
| vop_proof_token | No | VoP proof token from verify_payee covering the beneficiary (auto-resolved when omitted, except on SCA retry per PSD2 dynamic linking) | |
| 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. | |
| first_execution_date | Yes | First execution date (YYYY-MM-DD) |