Register multiple devices to play from anywhere!
Add funds to your account so you’re ready to play.
The more you play, the better your chances of winning.
On the first deposit we give a bonus.
Play now and win.
| 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 |
One of the big advantages of MIRACL’s technology is that it works on any browser without compatibility concerns. No downloads, plug-ins or even user permissions are required.
By stripping out all unnecessary steps, we’ve created a login that is the fastest in the world - just 2 seconds, and also has the highest success rate, 99.88% averaged across all of our clients.
Once you initiate it, the first thing the login does is check for an existing User ID on the device. If you have already registered then your User ID (your email address) is already entered and displayed. Keep in mind that aAny ID scheme can be used - emails, phone numbers, usernames, government IDs etc
So the user does not need to remember their ID and only their PIN entry is required.
All GUI is created and hosted on the service operator's side so the service operator has full control over the look, feel and function of that interface.
Integration of the PIN pad to MIRACL’s service is accomplished with a client-side JavaScript library. The library manages the cryptographic operations and API calls to MIRACL Trust so the integration is very straightforward and should take only a few days to be completed.
In this case, the PIN pad checks if there is a User ID. If it does, it immediately asks for a PIN to be entered. View documentation.
When the PIN is entered, the authenticate function is called. If the produced token is successfully verified, the user can be logged in. View Documentation.
The MIRACL Trust technology is independent from the user registration process, so the Service Operator can use exactly the same form and user journey that they have already built.
By linking into existing processes we reduce the integration effort to just a few lines of code, yet by discarding complex passwords in favor of simple, easy to remember PINs, we have seen registration completion rates improve by up to 18%.
MIRACL’s technology does not require access to any of the personal information contained in the registration form. The technology only requires two items of data to work - the USER ID and the PIN so there are no concerns with data privacy or ownership.
In this demo the USER ID is your email address but it can be anything the Service Operator normally uses such as a username, Phone#, Government ID or any other identifier. This is the only piece of information that will be shared with MIRACL - no other information is required by MIRACL.
The PIN is a special case, it is not shared with the Service Operator, MIRACL nor any other party. It is only used temporarily to establish the required cryptography on the device then it is discarded. It is ultra secure because there is no database of PINs locally or remotely and the PIN cannot be intercepted in transit or stolen from the device.
The rest of the information on the form is whatever the Service Operator would normally collect during their registration process, which remains unaltered.
The entire enrollment process remains under the operator’s control. Once the user has completed the sign-up process, a HTTP request is made for a MIRACL Trust Verification URL for the given User ID. View Documentation.
To finish the device registration process, you will need the MIRACL Trust Client JS Library. The library manages the cryptographic operations and API calls to MIRACL Trust so there is very little coding work to do. View Documentation.
The user can also be authenticated at the same time, so no further action is required by the user and they are logged in.
When integrating with MIRACL Trust there is no need to change the existing session management, user interface or user journeys if you have an existing service.
You are trying to log into a device that hasn’t been enrolled and doesn’t have a PIN. First you need to tell us who you are by entering your User ID (in this case an Email address). If you don’t have an account you will be directed to “Sign Up” and register.
If you do have an account you will then need to verify you’re really the owner of the account before you are allowed to create a PIN.
What do we mean by verify? This is a process which proves the user who created the account is the same person who wants to create a PIN on a new device.
It is important to understand that this verification process has nothing to do with MIRACL’s technology. So, for example, the service operator can use the same verification process they have already established for a password reset, but at the end, instead of changing a password you are instead creating a PIN for this device.
In this demo, we’ll prove you own the account by sending a passcode to the registered email address (your email address). The process will start as soon as you enter your email and hit “Next”.
Almost nothing new has to be developed to verify the user to create a PIN for a new device if you already have a password/account reset.
This makes the integration incredibly simple because you can re-use your existing password reset verification process to verify a user before creating a new PIN or resetting an existing PIN.
If you’re creating your verification process from scratch, then you can use any technology you’re familiar with, style it any way you want and create a journey that suits the requirements. You simply initiate the MIRACL Trust PIN creation and enrolment process at the end of it.
Although we have a 99.9% login success rate, there’s still a 1/10th of a percent (1 in 1000 logins) of people who forget or want to change their PIN.
The Service Operator obviously cannot allow anyone to change the PIN so they need to verify it is the account’s rightful owner who wants to change it.
What do we mean by verify? This is a process which proves the user who created the account is the same person who wants to change the PIN.
It is important to understand that this verification process has nothing to do with MIRACL’s technology. So, for example, the Service Operator can use the same verification process that they have already established for a Password reset, but at the end, instead of changing your password you are instead changing your PIN.
In this demo, we’ll prove you own the account by sending a Passcode to the registered email address (your email address).
Fortunately there is no chance that you forget your User ID because the device already knows it. So the only action required is for you to hit “I forgot my PIN” which starts the process.
Almost nothing new has to be developed to verify the user for a PIN reset if you already have a password/account reset.
This makes the integration incredibly simple because you can re-use your existing password reset verification process to verify a user before creating a new PIN or resetting an existing PIN.
If you’re creating your verification process from scratch, then you can use any technology you’re familiar with, style it any way you want and create a journey that suits the requirements. You simply initiate the MIRACL Trust PIN creation and enrolment process at the end of it.
After entering the correct passcode, you have verified that you’re the rightful owner of the account and the next step is to choose your new PIN.
This demo uses a verification method often used for an account/password reset and that illustrates how the Service Operator can re-use their existing password reset journey with the exception that you will change your PIN, not a password.
Once you have verified yourself to the Service Operator's satisfaction, the Service Operator can initiate the PIN enrolment at any time. Typically verification will be in the form of an OTP or Link sent via email or SMS Text but in practice it can be anything else such as a biometric verification.
With Custom User Verification, a Verification URL is issued that can be used to enrol a device and create a PIN. This Verification URL can be embedded within your verification email, SMS or IM which has the effect of verifying identity. When opened, the end user is prompted to choose their PIN and the device is enrolled.
This means you don’t have to worry about creating and tracking verification sessions for each User ID and can let MIRACL do it for you.
