Clearent requires merchant’s consent through signature submission to complete the onboarding application. Once all necessary information has been added, a merchant can easily provide his/her signature in one of the following two ways:
Electronic Signature Submission
Merchants can digitally sign all required documents for a fast and secure process.
Process:
Select at least one business contact as a signer (this is typically done when entering demographic information).
Present the ‘Terms and Conditions’ to the user for review.
Provide a clear option for the user to confirm their acceptance (e.g., a clickable checkbox).
Send the collected information to the ‘Signatures' endpoint.
Complete the submission by sending the electronic signatures via ‘Signature Submission’ endpoint.
Signature Submission via Document Upload
Merchants preferring physical signatures can print, sign, and then upload the signed documents for submission.
Process:
Mark at least one business contact as a signer (again, likely done when providing demographic information).
Provide a way for users to upload a document through your site.
Send the uploaded document to the ‘Document Upload’ Endpoint.
Send the gathered information to the ‘Signatures' endpoint.
Complete the submission by sending the electronic signatures via ‘Signature Submission’ endpoint.
When a merchant attempts to submit the signatures, the system will validate all the entered information and return a list of any issues found. If no issues are detected, merchant can proceed to submit the signatures.
This process ensures that Clearent receives proper authorization while offering flexibility in how signatures are submitted. After submission, no further changes can be made to the merchant through the Merchant Onboarding Boarding API.
{
"signatureSourceTypeId": 1,
"signatureSourceTypeName": "OnlineForm",
"signatureSourceTypeDescription": "Agreement was provided online through an E-Signature system or by indicating on an approved html form."
}
For a detailed breakdown of the request and response fields and their descriptions, refer to the reference documentation ofAPI.
