This API is used to reward your customers for each unit of currency they actually pay for your product or service. The Cashback API is mainly responsible for rewarding your customers' scores and points through a Cashback program based on the actual amount paid by your customers.
You may find it useful to make use of the Order Endpoint to track completed orders, reward your customer and redeem points using a Single API call. This endpoint is specifically designed for E-Commerce Businesses.
mobile or email should be sent along with the playerUniqueId in case (only if) your account supports channel merging.
Request
Header
Body
In case the customer doesn't exist on Gameball before sending the Cashback API call, the customer will be created automatically on Gameball and granted the points.
The example shown is a request sent to Gameball when you want to reward a customer ofplayerUniqueId"player123" with points equivalent to amount of 99.98. The points to be granted will be according to your points configurations on Cashback program.
The API enables the customer to use Gameball points as a payment method since it can be substituted for monetary values. A successful call will return the ID of the redeemed transaction reference created at Gameball.
You may find it useful to make use of the Order Endpoint to track completed orders, reward your customer and redeem points using a Single API call. This endpoint is specifically designed for E-Commerce Businesses.
mobile or email should be sent along with the playerUniqueId in case (only if) your account supports channel merging.
otp should be sent along with the request body in case (only if) your account has the OTP configuration enabled.
The example shown is a request sent to Gameball to redeem an amount equivalent to the amount held in the holdReference for the customer with playerUniqueId"player456".
The API is used to cancel a Cashback transaction or refund a points redemption transaction on Gameball. By providing the transactionId, Gameball checks for a corresponding cashback or redemption transaction and processes the request accordingly. After the request is successfully processed, the customer's points balance is updated to reflect the canceled or refunded transaction.
mobile or email should be sent along with the playerUniqueId in case (only if) your account supports channel merging.
The API is used to hold a specific amount of points from the customer's points balance. This is used to guarantee the availability of the points to be redeemed until the checkout process is completed. After a successful call, the API returns a holdReference number that is used later in the redemption API. The hold is active at Gameball for 10 minutes (default configurations) and automatically expires afterward. Once the hold expires, the points are returned back to the customer balance if this hold was not followed by a Redeem transaction.
You may find it useful to make use of the Order Endpoint to track completed orders, reward your customer and redeem points using a Single API call. This endpoint is specifically designed for E-Commerce Businesses.
In case this API is used, to successfully redeem the points, it should be followed by a Redemption API Call with the same resulted holdReference provided from this endpoint.
mobile or email should be sent along with the playerUniqueId in case (only if) your account supports channel merging.
Only one of the following attributes must be sent in the request bodyamountor holdPoints.
otp should be sent along with the request body in case (only if) your account has the OTP configuration enabled.
The API call is used to cancel previously held points. It can be called to cancel non-expired hold requests within the hold validity period.
Request
Header
Path Parameters
Usage Example
The example shown is a request sent to Gameball to remove held points with playerUniqueId"player456" an holdReference equals “9245fe4a-d402-451c-b9ed-9c1a04247482“.
Access manual points reward API to reward your customers for each unit currency they actually paid for your product or service or for an arbitrary amount.
mobile or email should be sent along with the playerUniqueId in case (only if) your account supports channel merging.
Request
Header
Body
Either the amount or the points should be sent along with the request.
In case the customer doesn't exist on Gameball before sending the Manual Transaction API call, the customer will be created automatically on Gameball and granted the points.
Sample Request Body
{"playerUniqueId":"player123","amount":99.98,"transactionId":"tra_123456789","transactionTime":"2019-09-19T16:14:09.895Z","username": "admin_storename","reason": "Thank You Gift"}