Vinfotech DFS - Our new product ability to integrate fantasy sports into your existing gaming platform

Brief

The online gaming market in India has seen tremendous growth of late, driven, in part, by the surge in digital usage. The revenues have nearly doubled over a period of four years, reaching INR43.8 billion in FY18 and are expected to grow further at a CAGR of 22.1 percent from FY18-23, expected to reach INR118.8 billion. The increase in online gaming activity driven by the growth in the number of gamers by nearly ten times over 2010-2018

The architecture comprises a list of all the APIs required from another team and a list of APIs which will be available for our end for seamless and secure integration. This ensures that integration should be secure, reliable, scalable and easy to maintain.

The document outlines the thought process for every aspect of the integration and clearly explains why specific decisions were made.

Requirements

Functional Requirements

• Secure
• Reliable
• Scalable
• Easy to maintain

Non-Functional Requirements

• Distributed architecture
• Integration must be open for constant product enhancements

Game Type

• DFS Contest = 0
• Network Contest = 1

Required Details from Client

• Api endpoint
• Client token

Winning data upload path(ex : winning/)

API Details

#1 Token Validation

Purpose of the token validation API is to make sure a request which we are getting from a third party is valid, no one is trying to phish in the system. In this API we will send a user access token which we will receive from WebView and in response we will check whether this token is valid or not.

#2 Get Balance

This API will be used to get the current balance of the user. We are going to send user token in the header parameter and user balance will be required in response.

#3 Deduct Balance

This API will be used to deduct contest entry fees from the user's account balance. We will send the user token in the header parameter.

#4 Refund (Contest cancellation)

This API will be used to refund the contest joining amount into the userʼs account balance on the cancellation of the contest. This will be applicable to all the users who have joined the contest. We will send client key in the header parameter and contestID in the body section.

#5 Refund (To an individual user)

This API will be used to refund contest joining amount in to userʼs account balance

• In case of user is not able to join a contest because of error
• In case of contest room got filled and there is not vacant seat available for user

We will send user token and client key in the header parameter and contestID in the body section

#6 Validate Contest Status

This API will be used by client to make sure that request raised is valid

#7 Content winning listing file upload and notification API

A contest can have thousands of contestants. So, winners listing can also be in thousands to manage this huge list a files system will be used. We will make a JSON file which will be uploaded on the client's SFTP or S3 location. Once the file will get uploaded on the client's location. We will notify the client accordingly and the client will process the winning amount into the wallet of winners.

We will send Vinfotechʼs ClientID in the header. File name, Contest ID, file MD5 hash in the body

#8 Winning credit notification API

A contest can have thousands of contestants. So, winners listing can also be in thousands to manage this huge list a files system will be used. We will make a JSON file which will be uploaded on the client's SFTP or S3 location. Once the file will get uploaded on the client's location, we will notify the client accordingly and the client will process the winning amount into the wallet of winners.

#9 API for notify about notifications to client

This API will be used to notify clients for sending push notifications to users who have joined contests.

This api is used for receiving contest refunds and winning data process status from clients.

Frontend Integration Details:

#1 Init Fantasy

Event will be fired from Webview to Client Application when all the essential initialization has been done on the webview side and webview is ready to accept the Client Application javascript event. To trigger client app all events the team has to create an Android interface name will be “AndroidInterface”. Inside this interface team have to define the below event which triggers from the webview side.

Event returns a json object which contains logintoken and push notifications payload if any or any other data.

#2 Set Token

Purpose of this functionality is to get a token from a client application by triggering an event or Post message, which we will receive in a webview loaded site and on site we will check whether this token is valid or not.

#3 Refresh Token

Purpose of this functionality is to logout users from the application when a token is invalidated in webview by triggering an event or Post message, which will be received by the client application and perform corresponding action.

#4 Add Fund

Purpose of this functionality is to add funds in the user wallet. On the web side we will trigger an event or Post message which will be received by the client application and an add fund screen/popup will appear.

Triggered by: Vinfotech

Received by: Client Application

#5 Transaction Status

Purpose of this functionality is to update funds in the user wallet. Aher adding the fund transaction client application will trigger an event about transaction success/failure which will be received by the web site, then on the web side we will update user balance and proceed further.

#6 Push Redirection

Purpose of this functionality is to redirect users on different web pages on the basis of notification payload, when they click on push notification. On Client application when a user clicks on push notification an event will be triggered which we will receive in a webview loaded site and on site we will check push payload and redirect to different screens as per data.

#7 Track Event

Purpose of this functionality is to track analytics events by sending event details from webview to client application.

#8 Logout App

Purpose of this functionality is to logout applications by sending events from webview to client application.

We at Vinfotech, are in constant pursuit of evolving alongside the industry and inventing at the boundaries of technology to facilitate a stronger fantasy sports business. Our commitment to providing you a high-quality solution will elevate your users’ game experience whilst increasing your revenue. We have always ensured with the principle of ‘stay first“ and providing the best in class services and updates to all our customers.