Create a business line

post /businessLines

Creates a business line.

This resource contains information about your user's line of business, including their industry and their source of funds. Adyen uses this information to verify your users as required by payment industry regulations. Adyen informs you of the verification results through webhooks or API responses.

If you are using hosted onboarding, only use v2 for your API requests.

Endpoint destination URL
Click to copy

Request parameters

capability string Deprecated in version 3

Use service instead.

The capability for which you are creating the business line.

Possible values: receivePayments, receiveFromPlatformPayments, issueBankAccount

industryCode string Required

A code that represents the industry of the legal entity. For example, 4431A for computer software stores.

legalEntityId string Required

Unique identifier of the legal entity that owns the business line.

salesChannels array [string]

A list of channels where goods or services are sold.

Possible values: pos, posMoto, eCommerce, ecomMoto, payByLink.

Required only in combination with the service paymentProcessing.

service string Required

The service for which you are creating the business line.

Possible values: paymentProcessing, issuing, banking

sourceOfFunds object

Contains information about the source of your user's funds. Required only for the service banking.

webData array [object]

List of website URLs where your user's goods or services are sold. When this is required for a service but your user does not have an online presence, provide the reason in the webDataExemption object.

webDataExemption object

The reason why the web data is not provided.

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
  • 400 - Bad Request

    A problem reading or understanding the request.

    Show more Show less
  • 401 - Unauthorized

    Authentication required.

    Show more Show less
  • 403 - Forbidden

    Insufficient permissions to process the request.

    Show more Show less
  • 422 - Unprocessable Entity

    A request validation error.

    Show more Show less
  • 500 - Internal Server Error

    The server could not process the request.

    Show more Show less
  • Request
  • Click to copy
  • Response
  • Click to copy