Velocity Abuse is a feature created to automatically prevent the same users from opening multiple accounts, requesting multiple loans or abusing sign-up bonuses etc.

If Velocity feature is enabled, then every user can be approved just once. If the same user was to submit any recurring verification attempt after already being approved, we will automatically decline them on Veriff’s side.

We have three Velocity flags that can be activated altogether or independently from each other:

  • Velocity/abuse duplicated user - person in the session has been previously approved in current integration

  • Velocity/abuse duplicated ID - document in the session has been previously approved in current integration

  • Velocity/abuse duplicated device - after 10th approved session submitted from the same device, all further attempts will be declined (done in order to prevent systematic identity abuse).

How does Velocity/Abuse work?

When elements of two different vendor sessions match, then we link the sessions together, we call it “Cross-Linking“. Cross-Linking utilizes and combines elements of device, network and personal data in different layers in order to link sessions together in real-time. If Velocity feature is enabled and we are confident that the user in the cross-linked session has been previously approved, we will automatically decline the session.

Cross-Linking is always done in multiple layers to prevent irrelevant sessions becoming linked and in order to filter out irrelevant matches to make sure we only take into account the sessions that are in fact related (for example, to avoid Cross-Linking strangers who happen to share the same name or use the same public network to submit sessions). Hence, when we decline the session with Velocity/Abuse, we are very confident that the same person, document or device have been previously approved.

Velocity User and Velocity ID also look at the initialization data that clients send us. If same person is coming with same vendor data (ID in client’s database), we don't trigger velocity as we consider it to be a legit reverification. This allows clients who send us VendorData to use velocity in conjunction with reverifications.

Velocity/Abuse in Risk labels

If Risk labels and Crosslinks features are enabled, a session that triggered Velocity/Abuse will be displayed under the risk labels Person previously approved, Document previously approved or Device previously approved in the Station together with cross-linked user name and session’s verified date:

Did this answer your question?