$100 Welcome Bonus

Bonus of the month

$100 Welcome Bonus

10 Free Spins

Claim Now

New Games

Blackjack
Play Now
Roulette
Play Now
Wheel of Fortune
Play Now
Neon Slots
Play Now

Today's Sports

NBA Summer League

Match 1 2
Atlanta Hawks - New Orleans Pelicans 2.62 1.46
San Antonio Spurs - Houston Rockets 2.56 1.48
Boston Celtics - Milwaukee Bucks 2.13 1.67
Oklahoma City Thunder - Orlando Magic 2.00 1.76
Utah Jazz - Dallas Mavericks 1.78 1.98
Portland Trail Blazers - New York Knicks 2.01 1.75
Log In

Although a quick and easy single-step process, we establish a secure Multi Factor Login by ensuring the PIN (a knowledge factor) can only be used on an enrolled device (a possession factor).

Making things quick and easy has big advantages.

  • More logins due to a higher Login Success Rate
  • Less users bounce to your competitors improving your LTV
  • Less users take up support time lowering your costs

It’s fast, it’s highly successful and it’s incredibly secure, defending against all remote attacks such as Credential Stuffing, Password Spraying, Phishing, Man In The Middle, Reverse Proxy, Replay and many more! Stop worrying about attackers and focus on your customers!

Don't show notes
View technical notes
Log In

Once the user has successfully authenticated, the signature of the resulting JWT (JSON Web Token) must be verified. View Documentation.

After that you can issue your platform’s own session token, so you wont need to change your session management at all. MIRACL’s technology should plugin very easily, replacing existing methods such as passwords without any changes to your session or user management.

So the process is:

  • authenticate
  • verify the JWT token
  • issue a session token

The Service Operator creates their own PIN pad interface giving them full control over all functions, user experience and branding. Integrating MIRACL’s technology, is very straightforward and should take no more than a few days.

View general notes
Don't show notes
PIN Setup

Entering your new PIN completed the process, your device has been enrolled with a PIN and you are automatically logged back in, there is no need to enter the PIN twice

Hit “Log Out” and then “Log In” to try out your new PIN.

Don't show notes
View technical notes
PIN Setup

From a MIRACL Trust integration perspective, the device enrolment and PIN creation flow is indistinguishable between the initial registration of a new user, a PIN reset on an existing device and a PIN creation on a new device. The same MIRACL Trust PIN creation and device enrolment process takes place with all three.

Once the user is verified (or not verified as the case with the registration enrolment), the system goes through the same sequence namely

  • verification request
  • getActivationToken
  • register
  • authenticate
  • verify the JWT token
  • issue a session token
View general notes
Don't show notes
Registration

You have now registered an account on the service and more importantly (for this demo), you have created a PIN for this device and logged in the user.

Hit “Log Out” and then “Log In” again to try your new PIN!

Although the Service Operator’s actual registration process may involve additional registration pages, user verification steps, KYC checks etc, you will note that MIRACL’s technology does not require them to operate and the PIN can be established at any point during your existing registration process.

It also doesn't require a download, an installation, a plugin or even user permissions. If this was a real Service Operator, they would probably collect more information and verify some of the details later by using things such as an email link to verify the email address.

Don't show notes
View technical notes
Registration

Once the form is submitted, the backend of this demo creates a record with the data from the form and makes a request for a new MIRACL Trust User ID. View Documentation.

This results in an enrollment link that is passed back to the frontend. The frontend calls the getActivationToken function and then the register function with the activation token. View Documentation.

Authentication is done immediately after the registration. View Documentation.

View general notes
Don't show notes
Signing

Banks do it all the time, when a critical action has been initiated by the user, the bank will reconfirm it is the owner of the account by sending a passcode or asking the user to re-enter their password.

Why do this? Because it might not be the same user in control of the session. It could be as simple as someone else sitting down at the desktop or something more nefarious like an attack that has stolen the session tokens.

Re-authentication protects the users from account attacks and the online service from “friendly” fraud such as chargebacks.

Why doesn’t every other online service do the same? Because normally it results in too much friction coupled with a high rate of failure. Most online services fear the negative impact it will have on their users.

Fortunately MIRACL trust’s action authentication takes 2 seconds and has a 99.9% success rate, meaning it will have a negligible effect on the user experience and your revenues!

What it does mean is that you can fight friendly fraud in the form of chargebacks with an effective tool to prove who really initiated a deposit/withdrawal, or prove who bet half their wallet on a long shot!

Just re-enter the same PIN you used to log in with.

Don't show notes
View technical notes
Signing

From the perspective of the user, they are simply re-entering the same PIN they used to Log In. Just having that single authentication associated in close proximity with the action taking place is useful, but we go one critical step further.

MIRACL Trust can also create a digital signature where the UserID on this device signs any details that are required, and all without the user noticing a thing. We call this MIRACL DVS.

If you have already successfully integrated MIRACL Trust for the login then all you need to do is call the sign method of the library and that will produce a digital signature.

View general notes
Don't show notes
Signing

That was easy (and quick). As you can see your action has been authenticated, the service operator has an immutable & irrefutable proof of your action and you have not been inconvenienced at all!

The digital signature is far more detailed than the simple email signatures used for online document signing. Typically online document signatures prove the owner of a particular email address authorised the document. MIRACL Trust’s signature is unique for every UserID:Device:Service - each permutation has its own unique signature.

This means it is impossible for the user to argue that some unknown attacker from halfway around the world could have misappropriated their username/password and taken the action without their knowledge. The action can be tied to the userID on a specific device for this particular online service.

Don't show notes
View technical notes
Signing

At this point you now have a digital signature in the form of a JSON object. This signature should be send to your backend and it's validity needs to be verified against MIRACL Trust.

Signature verification is done with a single API call to MIRACL Trust. If the verification is successful, you will receive a certificate in the form of a signed JWT (JSON Web Token) in the response. View Documentation.

View general notes
Don't show notes