Create a SEPA recurring transfer

OAuth scope: payment.write

This operation requires Strong Customer Authentication.

Example of SCA usage: Postman visual flow

Creates a new SEPA recurring transfer for a beneficiary. You can either provide a beneficiary_id for a known beneficiary or beneficiary data which will create an untrusted beneficiary on the fly.

Note:

• if a beneficiary with the same IBAN already exists, the provided details (such as name) will be updated;
• this endpoint is not trusting the beneficiary - you can trust a beneficiary through the Qonto app (for more details, please refer to this article) or through this endpoint (available for Embed partners only).

The subsequent transfer will be executed according to the specified frequency between the first and last execution dates. If no last execution date is provided the transfer will be executed indefinitely.

For recurring transfers above 30,000 EUR, at least one attachment is required.

POST /v2/sepa/recurring_transfers

Create a SEPA recurring transfer

cURL

curl --request POST \
  --url https://thirdparty.qonto.com/v2/sepa/recurring_transfers \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-Qonto-Idempotency-Key: <x-qonto-idempotency-key>' \
  --data '
{
  "vop_proof_token": "proof_1234567890abcdef",
  "recurring_transfer": {
    "beneficiary_id": "66b7e300-0126-4905-9688-27b445a48c4e",
    "bank_account_id": "420e13ac-9d3e-4c11-93a1-0c3c8304f2df",
    "reference": "Lease payment",
    "amount": "1100.50",
    "frequency": "monthly",
    "first_execution_date": "2025-04-22",
    "last_execution_date": "2026-08-21",
    "note": "Lease payment for offices in Paris",
    "attachment_ids": [
      "394f77f1-0d2c-46fb-8a7e-a959dbdeee63"
    ]
  }
}
'

200

Example

{
  "recurring_transfer": {
    "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "initiator_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "bank_account_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "amount": 1100.5,
    "amount_cents": 110050,
    "amount_currency": "EUR",
    "beneficiary_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "reference": "Lease payment",
    "note": "Lease payment for offices in Paris",
    "first_execution_date": "2025-04-22",
    "last_execution_date": "2026-08-21",
    "next_execution_date": "2025-05-22",
    "created_at": "2025-04-22T12:00:00Z",
    "updated_at": "2025-04-22T12:00:00Z",
    "status": "<string>"
  }
}

Authorizations

Authorization · string · header · required

Bearer authorization header: Bearer <token>, where <token> is the access token received from the authorization server at the end of the OAuth 2.0 flow.

Headers

X-Qonto-2fa-Preference · enum<string> · default: paired-device

Learn more in Strong Customer Authentication.

Available options: paired-device, passkey, mock, sms-otp

X-Qonto-Idempotency-Key · string · required

Learn more in Idempotent Requests.

Example:

"123e4567-e89b-12d3-a456-426614174000"

X-Qonto-Sca-Session-Token · string

Learn more in Strong Customer Authentication.

X-Qonto-MFA · string

Learn more in the SMS OTP Flow.

X-Qonto-Staging-Token · string

Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.

Body

application/json

vop_proof_token · string · required

Proof token from a payee verification attempt or skip verification request. Use the token from verify payee.

Example:

"proof_1234567890abcdef"

recurring_transfer · object · required

Show child attributes

Response

200

application/json

SEPA recurring transfer created successfully

recurring_transfer · object · required

Show child attributes