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:
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.
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.
Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.
Learn more in Strong Customer Authentication.
paired-device
, passkey
, mock
, sms-otp
Learn more in Idempotent Requests.
"123e4567-e89b-12d3-a456-426614174000"
Learn more in Strong Customer Authentication.
Learn more in the SMS OTP Flow.
SEPA recurring transfer created successfully
The response is of type object
.