---
title: "POST /api/v4.0/integrations/transactions/cashback"
method: POST
path: "/api/v4.0/integrations/transactions/cashback"
---

# POST /api/v4.0/integrations/transactions/cashback

`POST /api/v4.0/integrations/transactions/cashback`

This API awards loyalty points to customers in Gameball through a cashback program based on the amount.

## Request body

- object
  - `customerId` string, required — Unique identifier for the customer that you can reference across the customer's whole lifetime. Could be a database ID, random string, email or anything that uniquely identifies the customer.
  - `email` string — Customer's email address. This is required if your account uses email-based channel merging.
  - `mobile` string — Customer's mobile number. This is required if your account uses mobile-based channel merging.
  - `transactionId` string, required — A unique identifier for a transaction in your system (e.g., order number or invoice number). This ID is critical for managing transaction lifecycle events such as reversals, cancellations, or refunds in Gameball.
  - `transactionTime` string, date-time, required — The time of the transaction in your system (e.g., order datetime, invoice datetime). Must be in UTC (ISO 8601 format).
  - `amount` number, required — Monetary value of the transaction for which the customer will be rewarded, based on the Cashback program configuration.
  - `merchant` object — This object contains details about the specific merchant involved in the transaction, which is particularly important for businesses managing multiple merchants or branches under the same Gameball account. This object can provide identifying information about both the main merchant and any associated branch where the transaction took place.
    - `uniqueId` string — Unique identifier for the merchant.
    - `name` string — Name of the merchant.
    - `branch` object
      - `uniqueId` string, required — Unique identifier for the branch where the transaction took place.
      - `name` string — Name of the branch where the transaction took place.
  - `configurations` object — This object contains configurations related to the cashback settings.
    - `returnWindow` integer — The number of days the cashback will stay in a pending state, typically aligning with the return window in e-commerce to account for potential order cancellations or refunds. The value should be between 0 and 7,300 days (20 years).

## Response `200`

Cashback issued successfully

- object
  - `customerId` string — Unique identifier for the customer that you can reference across the customer's whole lifetime. Could be a database ID, random string, email, or anything that uniquely identifies the customer.
  - `gameballTransactionId` number — Unique identifier for the transaction in the Gameball system.
  - `rewardAmount` number — The monetary value equivalent of the points rewarded to the customer for the transaction. Example: If the customer earns 50 points for their purchase and each point is worth $0.10, the rewardAmount will be $5.
  - `rewardEquivalentPoints` number — The number of points rewarded to the customer for the transaction. Example: If the customer earns 50 points for their purchase, the rewardEquivalentPoints will be 50.

---

[API](https://skmtc.net/gameballers/apis/gameball-api.md) · [All operations](https://skmtc.net/gameballers/apis/gameball-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/gameballers/gameball-api/versions/2e4a8bfe2291/schema)