Create a Bulk Transfer
OAuth scope: payment.write
This operation requires Strong Customer Authentication, except when all transfers include a beneficiary_id and all beneficiaries are trusted, in which case SCA is not required.
However, if at least one transfer passes the beneficiary object then SCA will be triggered.
Example of SCA usage: Postman visual flow
Creates a batch of SEPA transfers for asynchronous processing. If the payload is valid, a BulkTransfer is created and returned, which can be polled via GET v2/sepa/bulk_transfers/:id.
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).
Business rules and validations are applied to each individual transfer after the BulkTransfer is created. For instance, transfers above 30,000 EUR require at least one attachment. This validation is performed asynchronously, meaning the BulkTransfer will be created, but if the attachment is missing, the result for that transfer will contain an error.
By default, transfers will be processed as instant. If instant processing isnโt possible, it will automatically fall back to standard processing. It will be the case if the amount of the individual transfer is above the following thresholds ๐
Untrusted beneficiary
Untrusted beneficiary
- The individual transfer is above 5,000 EUR;
- More than 20,000 EUR have been sent to this beneficairy within 24 hours.
Trusted beneficiary
Trusted beneficiary
- The individual transfer is above 10,000 EUR;
- More than 50,000 EUR have been sent to this beneficairy within 24 hours.
To learn more about instant transfers, please read this article.
Authorizations
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
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.
Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.
Body
Proof token from a bulk payee verification attempt. Use the token from bulk verify payee to opt-out from the verification.
"proof_1234567890abcdef"
The ID of the bank account from which the amount will be debited from.
List of SEPA transfers to process (up to 400).
400Response
Successfully creates a BulkTransfer for processing