Player verification allows you to integrate your own authentication layer into your webstore. Once you have setup player verification the webstore will ping an endpoint hosted on your own website with information about the player attempting to login.
Depending on your response you can deny/allow the player from logging in and also enable sales, apply coupons automatically, or enable categories/packages.
The player verification system opens up a whole new world of opportunities for integrating with your own backend systems. An example would be checking if a player has logged into your server recently or if they are a registered member on your forums or existing website.
How To Setup Player Verification
- Go to Integrations > Player Verification.
- Enter the full URL of your endpoint, for example http://example.com/tebex/verification.php. You can use any programming language to create your endpoint as long as it returns the response as listed below.
Accepting Notifications And Returning A Response
When a player attempts to login to your webstore we will send a GET request request to the URL you have previously set as outlined above. An example request URL would
look like the following:
Request Query Parameters
- ign - The username of the player attempting to login.
- ip - The IP address of the player attempting to login.
- country - The country code of the player (Based from GEO locating their IP address).
To allow the player to login based on the provided query parameters you need to return a JSON response such as the following example:
"message":"An optional message to send to the player upon login. This field is optional."
If you don't want to allow the user to login you can return a JSON response such as:
"error":"You are not allowed to access our webstore."
Applying Changes To The Webstore/Basket Upon Login
The player verification feature also allows you to make changes to the webstore or basket upon login such as the following:
- Apply a sale that otherwise would be inactive.
- Automatically apply a coupon code.
- Allow the player to view a category or package that otherwise would be disabled.
Just return the following JSON object. Each additional element is completely optional (For example you might only want to apply a coupon and not enable a category).
I'm not a developer! Help!
We understand not everyone understands the world of programming, and if that's the case we recommend reaching out to a contractor who understands what they're doing. Just send them this article and it'll include enough information for them to develop you a custom system.