Terms of Service

Your users must accept Adyen's Terms of Service before they can perform particular actions in your marketplace. If you build your own UI to collect data to onboard your users, you must generate a Terms of Service document, show the document to your users, and ask them to accept it. If you are using hosted onboarding, your user will complete this step as part of the onboarding process.

The Terms of Service document must be accepted by an individual legal entity that represents a physical person. For organizations, the document must be accepted by an authorized signatory of the organization. For example:

• A cardholder accepts the document on their own behalf.
• The owner of a restaurant accepts the document on behalf of the legal entity that represents the business.

Requirements

Make sure that you have API credentials for the Legal Entity Management API and that you have created legal entities for:

• The user that has a contractual relationship with your marketplace.
• The individual legal entity who will accept the document.

Step 1: Confirm Terms of Service requirements

When you create an account holder, certain capabilities are requested for them. To check whether your user must accept the Terms of Service, listen to balancePlatform.accountHolder.updated webhooks.

If your user is required to accept Adyen's Terms of Service, it is indicated in the verificationErrors array.

Step 2: Get the types of Terms of Service required

If your user is required to accept Adyen's Terms of Service, you must determine which types of documents they need to accept. Make a GET /legalEntities/{id}/termsOfServiceStatus request, specifying the id of the main legal entity in the path. For sole proprietorships, this is the individual legal entity ID of the owner.

In your test environment, only the document type adyenForPlatformsAdvanced is returned regardless of your actual integration. This is since all accounts use the same default configuration. In your live environment, the actual Terms of Service document types are returned.

Step 3: Generate the Terms of Service documents

To generate the Terms of Service documents, make a POST /legalEntities/{id}/termsOfService request, specifying the id of the main legal entity in the path. For sole proprietorships, this is the individual legal entity ID of the owner.

Parameter	Required	Description
type		The type of document based on the services and capabilities requested by the user and your platform integration.
language		The language used for the Terms of Service document, specified by the two letter ISO 639-1 language code. Possible value: en for English.
termsOfServiceDocumentFormat		The requested format for the Terms of Service document. Default value: JSON. Possible values: JSON, PDF, or TXT.

The response returns the following information:

The response returns the document and its unique termsOfServiceDocumentId.

You will need to present the document to your user in the next step. Use the document ID when you confirm your user has accepted the Terms of Service.

Step 4: Present the Terms of Service document to your user

You need to ask your user to review and accept the Terms of Service document. The process to do this depends on the format of the document.

Step 5: Accept the Terms of Service

To confirm that your user has accepted the Terms of Service, make a PATCH /legalEntities/{id}/termsOfService/termsOfServicedocumentid request, specifying the id of the main legal entity and the termsOfServiceDocumentId of the document in the path. For sole proprietorships, include the legal entity ID of the owner in the path. For organizations, include the legal entity ID of the organization in the path.

In the body of the request, specify the following:

Parameter	Required	Description
acceptedBy		The individual legal entity id of the user accepting the Terms of Service. For sole proprietorships, this is the individual legal entity ID of the owner. For organizations, this is the legal entity ID of an authorized signatory for the organization.
ipAddress		The IP address of the user.

This request populates the Terms of Service document with the data of the main legal entity. For sole proprietorships, this is the information for the individual legal entity of the owner. For organizations, this means the document contains both the data for the organization and the individual legal entity of the authorized signatory who accepted the document.

The response returns the following information.

Step 6 (Optional): Get the Terms of Service information for a legal entity

To see the Terms of Service information for a legal entity, make a GET /legalEntities/{id}/termsOfServiceAcceptanceInfos request with the id of the main legal entity in the path. For sole proprietorships, this is the individual legal entity ID of the owner.

The response returns information about the Terms of Service document linked to the legal entity.