Debt Formalization
By default, QI Tech collects signatures via QI Sign, and the contract is sent to the signatories at the time of issuance. However, there is also the possibility for the partner to independently collect signatures and send the signed document or signature evidence to QI Tech to proceed with the operation.
For the partner to collect signatures and then submit the signed document via API, it is necessary to request the configuration of this flow from the QI Tech support team.
The signing process can be done in two ways:
1 - Signatures are collected through the QI Tech platform;
2 - The partner independently collects signatures and then sends the signed contract to QI Tech - This option allows for either the submission of the signed PDF or the submission of a signature hash;
The flow of calls changes according to the chosen process and can follow the call paths below:
Flow 1
After requesting the configuration of signature flow 1 from the QI Tech support team, the only call needed to issue the debt is the call from set 3, according to the credit borrower of the operation.
QI Tech will issue the pre-configured credit contract and send it for signing - the operation can be monitored via API 5.1 or through the sent callbacks.
The document is signed through the QI Sign platform and can occur via email, WhatsApp, or SMS within 7 days after the contract issuance.
Due to the asynchronous nature of the signature, when the contract is signed by the borrower, an event is triggered via webhook to the originator.
Flow 2
After requesting the configuration of signature flow 2 from the QI Tech support team, there is a sequence of calls that must be made.
The first call will necessarily be the set of APIs 3 (according to the credit borrower of the operation) to issue the contract PDF, and the last call will be API 4.1 to submit the already signed contract.
In the case of document signing via a certification authority, it is necessary to send the URL with the signed PDF in API 4.1.
In the case of signing via opt-in on the frontend, the information to be sent in API 4.1 will be the acceptance evidence from the client.
QI Tech will then follow the flow for disbursement - the operation can be monitored using API 5.1 or through the sent webhooks.
Accepted Signature Types
pdf-signature
This type indicates that the PDF issued through "/debt" will be signed, and the link to the signed PDF will be sent via API 4.1 as a form of authentication.
data-signature
This type indicates that the PDF issued through "/debt" will be signed through a hash attached to its last page.
Data authentication can have three types:
Opt-in
Opt-in signature means that the client will consent to the contract through the frontend.
For this signature to be valid, some data must be sent mandatorily.
Zip
Zip signature involves the submission of a proof file, such as a recorded call.
Selfie
Selfie authentication is available to partners using QI Tech's CaaS services, where selfie authentication is validated, and a proof ID is generated.