1. Objective
The Version Lifecycle Policy (PCVV) aims to give customers transparency about the Confirma Fácil lifecycle: how updates are made available, which components follow each evolution model, how discontinuations are handled, and what the rights and obligations of Senior and the customer are.
2. Web portal - APIs and mobile app (Audit 2.0)
Confirma Fácil consists of the web portal, the APIs and the Audit 2.0 mobile app, used in the field. All of them follow the continuous evolution model, in which new features, fixes and improvements are incorporated into the product incrementally. However, they differ in how updates reach the user, as shown in the table below.
Updates can be made available at any time, with no fixed release window, and take effect for all customers at the same time. Previous versions of the portal or the APIs are not maintained in parallel.
Note
Confirma Fácil does not provide a staging environment for customers. Updates are made available directly in the production environment, already validated by Senior.
3. Discontinuation and API changes
As the product evolves, features may be replaced or discontinued. When there is a relevant impact on customers' operations, the discontinuation will be communicated in advance through Senior's official channels.
Changes that modify the API contract — fields, formats, authentication rules or request limits — are assessed for their impact on customer integrations. When incompatible with existing integrations, they will be communicated in advance. The current API specification, including request limits, is published in the product's technical documentation.
4. Rights and obligations
Confirma Fácil rights and obligations: Senior is responsible for ensuring that Confirma Fácil works as defined, making its evolution available — new features, fixes and improvements — and handling incidents reported through the support channels.
Customer rights and obligations: the customer has access to the features and enhancements made available in Confirma Fácil and must use it in accordance with the established guidelines and conditions, reporting any problems or incidents through the available support channels.
Where applicable, the customer is responsible for assessing the impacts of the communicated changes on their integrations and internal processes, observing the technical documentation and the API usage limits, and keeping the Audit 2.0 app updated on the devices used in their operation, including by carriers and other partners acting on their behalf.
5. Glossary
6. FAQ - Confirma Fácil
Can I validate an update before it reaches my environment?
No. Confirma Fácil does not provide a staging environment for customers; updates are made available directly in production, for all customers at the same time.
Do I need to do anything to receive portal and API updates?
No. The web portal and the APIs are updated automatically and the customer always uses the most current version.
Can I keep using a previous version of the portal or the APIs?
No. Previous versions are not maintained in parallel.
What happens if the Audit 2.0 app is not updated on the device?
Previous versions may no longer be compatible with the platform as it evolves. Therefore, the app must be kept updated, including on the devices of carriers and partners acting on behalf of the customer.
How will I know about changes that affect my integration?
Changes that are incompatible with existing integrations and discontinuations with relevant impact are communicated in advance through Senior's official channels. The current API specification is available in the product's technical documentation.
For more information, visit: PCVV - Version Lifecycle Policy