Skip to main content
POST
Create a SEPA recurring transfer
Authentication: API key OAuth 2.0
Scope: payment.write Sensitive
This operation requires Strong Customer Authentication.
Example of SCA usage: Postman visual flow
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 the Automate your business operations and Embed use cases).
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.

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

Response

SEPA recurring transfer created successfully

recurring_transfer
object
required