"REL-IDverify is the only security product that can meet all of your omni-channel needs. The power of REL-IDverify is in its flexibility. The potential use-cases are endless. With the REL-ID secure channel at its core, REL-IDverify extends mutual authentication to any transaction for a seamless, OOB, omni-channel experience."

Customer Service Verification
Brick & Mortar
Web Login
Customer Service Transaction
OOB Transaction Approval
Workflow Transaction Approval

What are the benefits of REL-ID verify

BRAND

REL-ID is available in an embeddable SDK. With REL-IDverify, you can brand your authentication mechanism across all channels.

AFFORD

REL-ID offers more features at a lower cost than every competitor product. With disruptive technology come disruptive prices.

TRUST

REL-ID has a patented MITM-proof channel built on its relative identity model. REL-IDverify extends that trust to any omni-channel transaction while meeeting NIST's 800-63B standards.

CONTROl

With REL-ID, no 3rd party is involved in your trust chain. Other 2FA products manage your notifications and handle your traffic. REL-ID is entirely on-premise with no need for certs.

MODIFY

The REL-IDverify backend API is flexible on both the server and client side. Trigger any message from your enterprise from any secure-zone server, display that message however you’d like. REL-ID can mix and match any FIDO compliant biometric and tie it to a continuously authenticated assurance level.

SCALE

The REL-ID infrastructure is extended as a soft appliance. It is built to scale into the 10s and hundreds of millions. It is the top IoT security solution available today.

USE-CASES

One Party Authentication

Scenario:

One person needs to confirm their own transaction or interaction with a REL-ID system.

Example 1:

A client A is on vacation and wants to see their financial account information and doesn’t want to do it from a small phone screen. They attempt to login from a hotel computer. The enterprise, seeing an unknown computer with an uncommon IP address, sends the login attempt to its risk engine. The risk engine determines that enhanced authentication is required and pushes a request to the REL-IDverify API endpoint on the REL-IDgateway. The gateway sends a push notification to the correct client’s phone. The client taps the notification, which opens the app and pulls down the authentication question: “Are you logging in from IP address Z, in location Y?” The client confirms or rejects.

Example 2:

A client A wants to move money from one account to another bank’s account. The amount is very large. The bank’s risk engine requires that the user confirm from a secondary device before finalizing the transaction. Client A logs in from their home computer and inputs the account information, requesting a move of $10,000 from account A to another account B at a separate bank. The client clicks the “Confirm” button. This routes a request from the admin system to the REL-IDverify module at the REL-IDgateway and then to the client’s phone. A notification pops up. The client taps the notification which opens the REL-ID enabled app. The app pulls down the request information through its secure REL-ID channel. The client sees the notification inside the application: “Are you are trying to move $10,000 from A to B?” The client either confirms or rejects the details of the transaction. If the client sees this request and did not make the request they can flag it as fraud and lock out further login attempts.

Two Party Authentication

Scenario:

One person needs another’s confirmation and authorization on a transaction.

Example 1:

A client Y on vacation calls into the call center requesting help with a transfer of funds. Before being allowed access to records, the operator X tells the client her name and location and pings the users phone. The notification opens up into a REL-ID application and, with the secure tunnel, pulls down the authentication question: “Are you speaking with Operator X in New York?” The Client Y, now confident they are speaking to a legitimate operator, confirms access for the operator. The operator can now see the client’s information.

Example 2:

In the same scenario as above, the client Y requests that the Operator move $500 from one account A to another account B. The operator enters the information into their administrative system and hits a “Confirm Transaction with User” button. This routes a request from the admin system to the REL-IDverify module at the REL-IDgateway and then to the client’s phone. A notification pops up. The client taps the notification which opens the REL-ID enabled app. The app pulls down the request information through its secure REL-ID channel. The client sees the notification inside the application: “Are you are trying to move $500 from A to B?” The client either confirms or rejects the details of the transaction. Both the operator and the client now have confidence that the other person is 100% who they say they are.

Card-Not-Present Authentication

Scenario:

One person needs another’s confirmation and authorization on a transaction.

Example 1:

Client Y on vacation attempts to use a credit card to purchase a scuba equipment rental. The bank sees the transaction is coming from a foreign point of sale, but has not corresponding travel purchase information. The risk engine flags the transaction as potential fraud.

The bank sends a notification to the user. The user taps the notification and pops open the REL-ID enabled banking application. The notification opens up into a REL-ID application and, with the secure tunnel, pulls down the authentication question: “Are you attempting to purchase something from XXX in YYYY in the amount of $ZZZ."

The Client Y confirms the purchase and the bank can proceed without flagging the account as fraud.

The bank can additionally, if given a confirmation, ask if the user is out of the country and for how long. From the app, the user can quickly alert the bank as to his or her travel plans.

Let's Get in Touch

Locations
7 World Trade Center
250 Greenwich St
New York, NY 10007
466 Southern Blvd
Chatham Township, NJ 07928
Teerth Technospace
S. No. 103
Mumbai Banglore Highway
Baner, Pune
Maharashtra 411045, India
Phone Numbers
US:
+1 212 520 2557
+1 844 33-RELID
+1 844 337-3543
Hong Kong:
+852 6417 4790
Pune:
+91 20 6725 3900