The sepaTransfers namespace contains all the functions related to SEPA transfer operations, including both single and bulk transfers. It can be accessed like this:const
sepaTransfers:object
=sepaTransfersNamespace.sepaTransfers
bulkTransfers: object
createBulkTransfer: (Creates a new SEPA bulk transfer from the current user to one or more beneficiaries. Depending on the beneficiaries’ trust status, this function may either create the bulk transfer directly via the API or open the UI to complete the SCA process for untrusted beneficiaries.params
) =>Promise
<BulkTransfer
>
BulkTransferParams
<NewBulkTransfer
>
An object containing the settings for the bulk transfer, including:
bulkTransferSettings
: An object that contains the mandatory bankAccountId
and an array of bulkTransfers
.operationSettings
: An object with operation-level settings such as
accessToken
, stagingToken
, and other optional parameters. See BulkTransferParams.
If the transfer needs to be created
for an untrusted beneficiary, the operationSettings
object must also include
the uiParentElementId
property. This has to specify the ID of the DOM element
where the UI for MFA will be displayed. Note that this means that creating
transfers for untrusted beneficiaries can only happen in the client side.
The createBulkTransfer
function requires an idempotencyKey
as well. If this
property is not passed as part of operationSettings
, a new one will be
generated automatically.
You can also specify an mfaPreference
in the operationSettings
to choose the
multi-factor authentication method to use for the SCA flow (e.g., ‘passkey’,
‘sms-otp’, or ‘paired-device’). If not provided, the default MFA method will be used.Promise
<BulkTransfer
>
A promise that resolves to a BulkTransfer object containing details of the created bulk transfer.
transfer
parameter is not an object
or is missing, or if the required properties of the transfer object are
missing or invalid. Also thrown if uiParentElementId
is not provided in the
operationSettings
, which is required for the iframe flow.
getBulkTransfer: (Fetches a specific SEPA bulk transfer by its ID.params
) =>Promise
<BulkTransfer
>
SepaTransferParams
<GetBulkTransfer
>
An object containing:
sepaTransferSettings
: An object that contains the mandatory bulkTransferId
to identify the bulk transfer to retrieve.operationSettings
: An object with operation-level settings such as
accessToken
, stagingToken
, and other optional parameters. See SepaTransferParams.Promise
<BulkTransfer
>
A promise that resolves to a BulkTransfer object containing details of the requested bulk transfer.
bulkTransferId
parameter is not a string or missing.
getBulkTransfers: (Fetches the list of SEPA bulk transfers for the current user.getBulkTransfersParams?
) =>Promise
<GetBulkTransfersResponse
>
SepaTransferParams
<never
>
An optional object containing operationSettings
.
The operationSettings
object can include:
accessToken
: If not provided, the function will use the token from initialize.stagingToken
: Optional, required only for staging environments.paginationSettings
: Optional object with page
and itemsPerPage
properties for pagination control.Promise
<GetBulkTransfersResponse
>
A promise that resolves to an object containing an array of bulk transfers and a meta
object containing pagination state.
cancelSepaTransfer: (Cancels an existing SEPA transfer identified by the providedcancelSepaTransferParams
) =>Promise
<void
>
sepaTransferId
.
SepaTransferParams
<CancelSepaTransferParams
>
An object with the parameters to cancel the
transfer. If it was not provided when calling the SDK’s initialize
function, an operationSettings
object has to be passed too with the
accessToken
and stagingToken
values.
Promise
<void
>
A promise that resolves without return value.
sepaTransferId
parameter is
missing, or if the provided value is not a string.
createSepaTransfer: (Creates a new SEPA transfer from the current user to a given beneficiary. Depending on the beneficiary’s trust status, this function will either create the transfer directly via API or open the UI to complete the SCA process.createTransferParams
) =>Promise
<SepaTransfer
>
SepaTransferParams
<NewSepaTransfer
>
An object with the parameters to create the
transfer. If it was not provided when calling the SDK’s initialize
function, an operationSettings
object has to be passed too with the
accessToken
and stagingToken
values. If the transfer needs to be created
for an untrusted beneficiary, the operationSettings
object must also include
the uiParentElementId
property. This has to specify the ID of the DOM element
where the UI for MFA will be displayed. Note that this means that creating
transfers for untrusted beneficiaries can only happen in the client side.
The createSepaTransfer
function requires an idempotencyKey
as well. If this
property is not passed as part of operationSettings
, a new one will be
generated automatically.
You can also specify an mfaPreference
in the operationSettings
to choose the
multi-factor authentication method to use for the SCA flow (e.g., ‘passkey’,
‘sms-otp’, or ‘paired-device’). If not provided, the default MFA method will be used.
Promise
<SepaTransfer
>
A promise that resolves to the created SEPA transfer.
transfer
parameter is not an object
or is missing, or if the required properties of the transfer object are
missing or invalid.
getSepaTransfer: (Fetches a single SEPA transfer of the current user by ID.Object
) =>Promise
<SepaTransfer
>
SepaTransferParams
<GetSepaTransfer
>
An object with the sepaTransferId and the optional accessToken
and stagingToken properties.
Promise
<SepaTransfer
>
A promise that resolves to a SEPA transfer.
sepaTransferId
parameter is not a
string or is missing.
getSepaTransfers: (Fetches the list of SEPA transfers for the current user.getSepaTransfersParams?
) =>Promise
<GetSepaTransfersResponse
>
SepaTransferParams
<never
>
An optional object containing accessToken
and stagingToken
parameters. If the accessToken
is not provided, the
function will use the token previously passed to the initialize function. The
stagingToken
is optional, but it has to be passed to use the SDK in staging
environments (it will be ignored in production). This function also allows
managing pagination by passing the paginationSettings
property, which
accepts an object with the page and itemsPerPage properties.
Promise
<GetSepaTransfersResponse
>
A promise that resolves to an object containing an array of SEPA
transfers and a meta
object containing pagination state.