Webhooks v1 - Merchant account created

Webhook parameters

Required Optional

createdAt string Required

Timestamp for when the webhook was created.

data object Required

Contains event details.

capabilities object Required

Key-value pairs that specify the actions that the merchant account can do and its settings. The key is a capability. For example, the sendToTransferInstrument is the capability required before you can pay out funds to the bank account. The value is an object containing the settings for the capability.

Show children

allowed boolean

Indicates whether the capability is allowed. Adyen sets this to true if the verification is successful.

allowedLevel string

The allowed level of the capability. Some capabilities have different levels which correspond to thresholds. Higher levels may require additional checks and increased monitoring.Possible values: notApplicable, low, medium, high.

capability string

The name of the capability. For example, sendToTransferInstrument.

problems array [object]

List of entities that has problems with verification. The information includes the details of the errors and the actions that you can take to resolve them.

Show children

entity object

The ID and the type of entity that has verification errors.

Show children

verificationErrors array [object]

List of verification errors.

Show children

requested boolean Required

Indicates whether you requested the capability.

requestedLevel string Required

The level that you requested for the capability. Some capabilities have different levels which correspond to thresholds. Higher levels may require additional checks and increased monitoring.Possible values: notApplicable, low, medium, high.

verificationStatus string

The status of the verification checks for the capability.

Possible values:

pending: Adyen is running the verification.
invalid: The verification failed. Check if the errors array contains more information.
valid: The verification was successful.
rejected: Adyen checked the information and found reasons to not allow the capability.

companyId string Required

The unique identifier of the company account.

legalEntityId string

The unique identifier of the legal entity.

merchantId string Required

The unique identifier of the merchant account.

status string Required

The status of the merchant account.

Possible values:

PreActive: The merchant account has been created. Users cannot access the merchant account in the Customer Area. The account cannot process payments.
Active: Users can access the merchant account in the Customer Area. If the company account is also Active, then payment processing and payouts are enabled.
InactiveWithModifications: Users can access the merchant account in the Customer Area. The account cannot process new payments but can still modify payments, for example issue refunds. The account can still receive payouts.
Inactive: Users can access the merchant account in the Customer Area. Payment processing and payouts are disabled.
Closed: The account is closed and this cannot be reversed. Users cannot log in. Payment processing and payouts are disabled.

environment string Required

The environment from which the webhook originated.

Possible values: test, live.

type string Required

Type of notification.

Response parameters

After submitting a call, you receive a response message to inform you that your request was received and processed.

Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.

HTTP Responses

200 - OK

The request has succeeded.
Show more Show less
notificationResponse string

Respond with HTTP 200 OK and [accepted] in the response body to accept the webhook.

Merchant account created

Webhook parameters

Response parameters

HTTP Responses

200 - OK