\n| type<\/a><\/td>\n | The type of document based on the services and capabilities requested by the user and your platform integration.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n \n <\/code-sample>\n<\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/marketplaces\/onboard-users\/terms-of-service","articleFields":{"description":"Get your users to accept Adyen's Terms of Service","feedback_component":true,"parameters":{"directoryPath":"\/marketplaces","model":"marketplace"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/marketplaces\/onboard-users\/terms-of-service","title":"Terms of Service","content":"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.\nIf you are using hosted onboarding, your user will complete this step as part of the onboarding process.\nThe 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.\nFor example:\n\nA cardholder accepts the document on their own behalf.\nThe owner of a restaurant accepts the document on behalf of the legal entity that represents the business.\n\nRequirements\nBefore you begin, take into account the following requirements and preparations.\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nYou must have an Adyen for Platforms integration.\n\n\nAPI credentials\nYou must have API credentials for the Legal Entity Management API (for example, ws[123456]@Scope.Company[YourCompanyAccount])\n\n\n\nWebhooks\nEnsure that your server can receive and accept standard webhooks.Subscribe to the following webhooks: Configuration webhooks\n\n\n\nSetup steps\nBefore you begin, make sure: Make sure you created legal entities for:The user that has a contractual relationship with your marketplace.The individual legal entity who will accept the document.\n\n\n\nHow it works\nTo generate the Terms of Service and have them accepted by your users, follow these steps:\n\nListen to the webhook to confirm Terms of Service requirements.\nMake an API request to get the types of Terms of Service required.\nMake an API request to generate the Terms of Service documents.\nPresent the Terms of Service document to your user.\nMake an API request to confirm that your user has accepted the Terms of Service.\nOptionally, make an API request to see the Terms of Service information for a specific legal entity.\n\n1. Confirm Terms of Service requirements\nWhen 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.\nIf your user is required to accept Adyen's Terms of Service, it is indicated in the verificationErrors array.\n\n \n\n2. Get the types of Terms of Service required\nIf 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.\n\nNote that your user may need to accept more than one Terms of Service document.\n\nIn 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.\n\n \n\n3. Generate the Terms of Service documents\nTo 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.\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\n type\n\nThe type of document based on the services and capabilities requested by the user and your platform integration.\n\n\n language\n\nThe language used for the Terms of Service document, specified by the two letter ISO 639-1 language code. Possible value: en for English or fr for French. Note that French is only available for some integration types in certain countries\/regions. Reach out to your Adyen contact for more information.\n\n\n termsOfServiceDocumentFormat\n\nThe requested format for the Terms of Service document. Default value: JSON. Possible values: JSON, PDF, or TXT.\n\n\n\n\n \n\nThe response returns the following information:\n\n\n\nParameter\nDescription\n\n\n\n\n document\nThe generated document in the Base64-encoded format.\n\n\n id\nThe unique identifier of the organization legal entity.\n\n\n language\nThe language of the document.\n\n\n type\nThe type of document based on the services and capabilities requested by the user and your platform integration.\n\n\n termsOfServiceDocumentId\nThe unique identifier of the document.\n\n\n termsOfServiceDocumentFormat\nThe requested format for the Terms of Service document. Default value: JSON. Possible values: JSON, PDF, or TXT.\n\n\n\n\n \n\nThe response returns the document and its unique termsOfServiceDocumentId.\n\nYour user may need to accept more than one Terms of Service document depending on your integration. In this case, every required document and termsOfServiceDocumentId is returned in the response.\n\nYou 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.\n4. Present the Terms of Service document to your user\nYou 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.\n\n\n \n \n \n \n\n\n5. Accept the Terms of Service\nTo 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.\nIn the body of the request, specify the following:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\nacceptedBy\n\nThe 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.\n\n\nipAddress\n\nThe IP address of the user.\n\n\n\nThis 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.\n\n \n\nThe response returns the following information.\n\n\n\nParameter\nDescription\n\n\n\n\nacceptedBy\nThe individual legal entity id of the user who accepted the terms of service.\n\n\nid\nThe unique identifier of the accepted document.\n\n\nipAddress\nThe IP address of the user. Only if provided in the request.\n\n\nlanguage\nThe language of the document.\n\n\ntermsOfServiceDocumentId\nThe unique identifier of the document.\n\n\ntype\nThe type of document based on the services and capabilities requested by the user and your platform integration.\n\n\n\n\n \n\n6. (Optional): Get the Terms of Service information for a legal entity\nTo 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.\n\n \n\nThe response returns information about the Terms of Service document linked to the legal entity.\n\n\n\nParameter\nDescription\n\n\n\n\ncreatedAt\nThe date the document was created.\n\n\nid\nThe unique identifier of the accepted document.\n\n\nacceptedBy\nThe id of the individual who accepted the terms of service.\n\n\nacceptedFor\nThe id of the main legal entity.\n\n\ntype\nThe type of document based on the services and capabilities requested by the user and your platform integration.\n\n\n\n\n \n\n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Marketplaces","lvl2":"Onboard and verify users","lvl3":"Terms of Service"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/marketplaces","lvl2":"https:\/\/docs.adyen.com\/pt\/marketplaces\/onboard-users","lvl3":"\/pt\/marketplaces\/onboard-users\/terms-of-service"},"levels":4,"category":"Marketplaces","category_color":"green","tags":["Terms","Service"]}}
|
![\"-white_check_mark-\"](\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" "\\"-white_check_mark-\\"")
<\/td>\n