Create external transfers with beneficiaries data
OAuth scope: payment.write
This operation requires Strong Customer Authentication.
Example of SCA usage: Postman visual flow
Solo basic plans
- Creates a single external transfer with beneficiary data.
- Solo basic plans are not allowed to do bulk transfers. If a bulk transfer is attempted, it will fail and an error will be returned.
Rest of plans
Creates up to 400 external transfers with beneficiaries data.
Business rules and validations are applied to each individual transfer synchronously. For instance, transfers above 30,000 EUR require at least one attachment. This validation is performed synchronously so, if the attachment is missing for one transfer, an error will be sent for that transfer (cf. response payload) but the other tranfers will be initiated normally.
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
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"
IBAN of account to debit.