Onboarding Stages

Onboarding Stages

The complete Legiti onboarding process (from signing the contract to using Legiti in production) is composed of 4 phases. Not all phases have coding integration itself, but it is important that you are aware of them to understand the whole process. It is important to remember that this process will be reviewed with the client during the integration kick-off meeting.

Overview

Complete Onboarding Timeline
As stated above, not all phases in this image are coding parts or require the intervention of a developer, but they are part of the complete onboarding with Legiti's product. Here is a more detailed explanation of each part:

Data Dump

The data dump is an important step in Legiti's process to create a customized model for the client. The data dump is nothing more than sending, in a standardized format, data from orders, users and past frauds so that Legiti's team can start creating a customized model based on the client's data. It is important to emphasize that Legiti should receive the data dump as soon as possible, because without it it is not possible to start working on the client's model and may delay Legiti go-live.
Finally, the following are Legiti's two standardized data dump templates (one for clients with sellers and one for clients without sellers):
  • Data dump for clients without sellers - Format
  • Data dump for clientes with sellers - Format
It is imperative to emphasize that the dump must be sent in the correct pattern/format, otherwise its processing can take a long time and delay the production start of Legiti's solution.

Frontend and Backend

This is the actual code integration period. During these phases, Legiti's frontend collection SDKs will be integrated with client applications/sites, as well as Legiti's backend API integration with the client platform. Although these phases appear as sequential in the image, they can be done in parallel, but if this is not possible, we recommend starting with the frontend, because there is no backfill for this data. You can find more information about the frontend SDKs here and about the APIs here.
To try to minimize integration errors/problems, the following meetings will be held between the client and the Legiti team:
  • Kickoff Meeting: Before starting any of the phases a 15/20 minute meeting will be held between Legiti and developer in charge of the integration to give a little more detailed overview of the work ahead. Especially going through the points of attention in the integration
  • Homologation Meeting: At the end of the integration of each part (backend and frontend) a meeting will be held, between Legiti and the responsible developer, to homologate that the integration is correct. During this meeting several test cases will be passed to make sure that the data is arriving correctly to Legiti. It should be noted that until the integration has been approved, it will not be possible to deploy the integration and move forward to the next phase of onboarding

Live Testing

The Live Testing period starts as soon as the client deploys the integration into production. This is a period destined to the correction of possible integration bugs that were not detected during the homologation, because they generally need a larger mass of data traffic to be detected. During this phase Legiti will receive all the client's transactions, but will not return decisions for them. It is worth mentioning that, during this phase, the Legiti team will be close to the clients development team to confirm that the data is arriving correctly and to solve any possible problems.

Backfill Data Dump

Legiti's team will request a new data dump, in the same format as the first one, to cover the data "hole" between receiving the first data dump and receiving the first data from the API. In addition, this data dump also serves to correct possible data errors from the first one.

Ghost Mode

During this period, the integration will already be in production, just like in Live Testing, and Legiti's models will be analyzing all transactions, but without returning decisions (they will return unavailable), also like in Live Testing. This is a phase in which the Legiti team, together with the client, continuously evaluates the results of the model to optimize the risk policy that best fits the client's needs. It is worth mentioning that this period only starts when the backfill data dump is received and treated by Legiti.

Go-live

As soon as the client and Legiti decide that it is time to start using the Legiti decisions in production, a parameter change will be done on the Legiti side, on a date already pre-aligned with the client, so that the API can start returning decision values. It is worth mentioning that a quick homologation will be done before the parameter change to certify that the decisions returned by Legiti will be used correctly.

Questions

If you have any questions regarding this process, please do not hesitate to contact Legiti's Customer Solutions team.
Copy link
On this page
Onboarding Stages
Overview
Data Dump
Frontend and Backend
Live Testing
Backfill Data Dump
Ghost Mode
Go-live
Questions