Sweep updated
Adyen sends this webhook when you successfully update a sweep.
Request Parameters
Contains event details.
The unique identifier of the balance account for which the sweep was configured.
The unique identifier of the balance platform.
Contains information about the sweep resource that triggered the event.
The type of transfer that results from the sweep.
Possible values:
-
bank: Sweep to a transfer instrument.
-
internal: Transfer to another balance account within your platform.
Required when setting priorities.
The destination or the source of the funds, depending on the sweep type.
Either a balanceAccountId, transferInstrumentId, or merchantAccount is required.
The unique identifier of the destination or source balance account.
If you are updating the counterparty from a transfer instrument to a balance account, set
transferInstrumentIdto null.
The merchant account that will be the source of funds.
You can only use this parameter with sweeps of type pull and if you are processing payments with Adyen.
The unique identifier of the destination or source transfer instrument depending on the sweep type
. To set up automated top-up sweeps to balance accounts in your marketplace or platform, use this parameter in combination with a merchantAccount and a sweep type of pull.
Top-up sweeps start a direct debit request from the source transfer instrument. Contact Adyen Support to enable this feature.> If you are updating the counterparty from a balance account to a transfer instrument, set balanceAccountId to null.
The three-character ISO currency code in uppercase. For example, EUR.
The sweep currency must match any of the balances currencies.
The message that will be used in the sweep transfer's description body with a maximum length of 140 characters.
If the message is longer after replacing placeholders, the message will be cut off at 140 characters.
The unique identifier of the sweep.
The list of priorities for the bank transfer. This sets the speed at which the transfer is sent and the fees that you have to pay. You can provide multiple priorities. Adyen will try to pay out using the priority you list first. If that's not possible, it moves on to the next option in the order of your provided priorities.
Possible values:
-
regular: for normal, low-value transactions.
-
fast: a faster way to transfer funds, but the fees are higher. Recommended for high-priority, low-value transactions.
-
wire: the fastest way to transfer funds, but this has the highest fees. Recommended for high-priority, high-value transactions.
-
instant: for instant funds transfers in SEPA countries.
-
crossBorder: for high-value transfers to a recipient in a different country.
-
internal: for transfers to an Adyen-issued business bank account (by bank account number/IBAN).
Set category to bank. For more details, see optional priorities setup for marketplaces or platforms.
The reason for disabling the sweep.
The human readable reason for disabling the sweep.
Your reference for the sweep configuration.
The reference sent to or received from the counterparty. Only alphanumeric characters are allowed.
The schedule when the triggerAmount is evaluated. If the balance meets the threshold, funds are pushed out of or pulled in to the balance account.
A cron expression that is used to set the sweep schedule. The schedule uses the time zone of the balance account. For example, 30 17 * * MON schedules a sweep every Monday at 17:30.
The expression must have five values separated by a single space in the following order:
-
Minute: 0-59
-
Hour: 0-23
-
Day of the month: 1-31
-
Month: 1-12 or JAN-DEC
-
Day of the week: 0-7 (0 and 7 are Sunday) or MON-SUN.
The following non-standard characters are supported: *, L, #, W and /. See crontab guru for more examples.
Required when type is cron.
The schedule type.
Possible values:
-
cron: push out funds based on a
cronExpression. -
daily: push out funds daily at 07:00 AM CET.
-
weekly: push out funds every Monday at 07:00 AM CET.
-
monthly: push out funds every first of the month at 07:00 AM CET.
-
balance: execute the sweep instantly if the
triggerAmountis reached.
The status of the sweep. If not provided, by default, this is set to active.
Possible values:
-
active: the sweep is enabled and funds will be pulled in or pushed out based on the defined configuration.
-
inactive: the sweep is disabled and cannot be triggered.
The amount that must be pushed out or pulled in. You can configure either sweepAmount or targetAmount, not both.
The amount of the transaction, in minor units.
The amount that must be available in the balance account after the sweep. You can configure either sweepAmount or targetAmount, not both.
The amount of the transaction, in minor units.
The threshold amount that triggers the sweep. If not provided, by default, the amount is set to zero. The triggerAmount is evaluated according to the specified schedule.type.
-
For
typepull, if the balance is less than or equal to thetriggerAmount, funds are pulled in to the balance account. -
For
typepush, if the balance is more than or equal to thetriggerAmount, funds are pushed out of the balance account.
The amount of the transaction, in minor units.
The direction of sweep, whether pushing out or pulling in funds to the balance account. If not provided, by default, this is set to push.
Possible values:
-
push: push out funds to a destination balance account or transfer instrument.
-
pull: pull in funds from a source merchant account, transfer instrument, or balance account.
The environment from which the webhook originated.
Possible values: test, live.
When the event was queued.
Type of webhook.
Response parameters
When you receive a webhook, you must respond with an HTTP status code.
HTTP Responses
200 - OK
The request has succeeded.
Show moreShow lessnotificationResponsestringRespond with any 2xx HTTP status code to accept the webhook.