ACCOUNT_UPDATED

This notification is triggered when an account is updated.

Common fields

The table below lists the fields that are present in each Adyen MarketPay notification and provide general information about the event that triggered this notification.

Name Type Returned by default Description
eventType String (tick)

This notification event's type.

For this event, it is ACCOUNT_UPDATED.

eventDate DateTime (tick)

NEW IN V4 The date and time when an event has been completed.

executingUserKey String (tick)

A user or process that has triggered the notification.

live Boolean (tick)

Informs about the origin of the notification:

  • true: the notification originated from the live environment.
  • false: the notification originated from the test environment.
pspReference String (tick) PSP Reference of the notification.
content Object (tick)

Notification message content, which is specific for each notification type.

For the detailed description of its structure, see the table below.

Content field structure

The content field of this notification contains the following elements.

Name Type Returned by default Description
pspReference String (tick) PSP Reference of the original request to /updateAccount.
accountCode String (tick)

A code of the account that was updated.

payoutSchedule Object (tick) A container for schedule details.
  schedule Enum (tick)

The new schedule interval.

Possible values:

  • DEFAULT – the default setting for the marketplace;
  • DAILY – every day;
  • WEEKLY – every Monday;
  • MONTHLY – on the first day of the month;
  • HOLD – not scheduled, the payout should be initiated manually.
submittedAsync Boolean (tick)

Indicates whether the call is processed synchronously or asynchronously.

Depending on your marketplace settings, the following scenarios may be applied:

  • sync – The processing of the request is immediately attempted; it might result in an error if the corresponding service is momentarily unavailable.
  • async – The request is queued and will be executed when the corresponding service is available, in the order the requests are received.
  • asyncOnError – The processing of the request is immediately attempted, but in case the corresponding service is unavailable, the request is scheduled in a queue.

Code example: A received account updated

{
   "eventType":"ACCOUNT_UPDATED",
   "eventDate":"2018-05-02T13:30:18+02:00",
   "executingUserKey":"ws_582414",
   "live":false,
   "pspReference":"8815252606188163",
   "content":{
      "accountCode":"177883605",
      "payoutSchedule":{
         "schedule":"DAILY"
      },
      "pspReference":"8815252606188163",
      "submittedAsync":"false"
   }
}