Skip to main content

/member/payments

Overview​

This endpoint retrieves a member's points or credit transaction history. It allows you to view historical payment activities including point additions, redemptions, and credit transactions.

When to Use This Endpoint​

Use this endpoint in the following cases:

  • To display a member's points or credit transaction history
  • To show detailed transaction records for member account statements
  • To audit or review historical payment activities
  • To provide transparency on loyalty balance changes

Key Considerations​

  • The budgetType parameter determines whether to retrieve points or credit history
  • Results can be filtered by date range using fromDate and toDate
  • Pagination is supported through limit and offset parameters
  • Default date range is not limited unless specified

Request Details​

Method & URL​

POST /member/payments

See API Servers for the base URL to use in place of {{server}}.

Headers​

HeaderTypeRequiredDescription
x-api-keystringYesAPI key for authentication
x-source-typestringYesOrigin of the request (e.g., POS, Web)
x-source-namestringYesName of the client or integration system
x-pos-idstringYesPOS terminal identifier
x-branch-idstringYesBranch or store location identifier

Request Body​

FieldTypeRequiredDefaultDescription
memberobjectYes—Member identifier (see Member reference)
budgetTypestringYes—Type of budget: points or credit
limitintegerNo40Max number of records (1-100)
offsetintegerNo0Number of records to skip for pagination (≥0)
fromDatestringNo—Filter start date (ISO 8601 format)
toDatestringNo—Filter end date (ISO 8601 format)

Request Example​

curl --location --request POST 'https://{{server}}/v1/member/payments' \
--header 'Content-Type: application/json' \
--header 'x-api-key: {{api-key}}' \
--header 'x-source-type: POS' \
--header 'x-source-name: pos_terminal_01' \
--header 'x-pos-id: POS001' \
--header 'x-branch-id: BR001' \
--data-raw '{
"member": {
"membershipKey": "abc123"
},
"budgetType": "points",
"limit": 20,
"offset": 0,
"fromDate": "2024-01-01T00:00:00Z",
"toDate": "2024-12-31T23:59:59Z"
}'

Success Response​

{
"status": "success",
"transactions": [
{
"transactionId": "confirmation-uuid-or-db-id",
"createdAt": "2024-06-15T14:30:00.000Z",
"operation": "AddPoints",
"type": "Point",
"amount": 105
},
{
"transactionId": "conf-uuid-2",
"createdAt": "2024-06-10T12:15:00.000Z",
"operation": "RedeemPoints",
"type": "Point",
"amount": -50
}
]
}

Response Fields​

FieldTypeDescription
statusstringRequest status indicator
transactionsarrayArray of transaction objects
transactionIdstringUnique identifier for the transaction
createdAtstringISO 8601 timestamp of the transaction
operationstringOperation type: AddPoints, RedeemPoints, AddCredits, RedeemCredits
typestringBudget type: Point or Credit
amountnumberTransaction amount (positive for add, negative for use)

Error Response Examples​

Missing Required Header​

{
"status": "error",
"error": {
"code": "101",
"message": "Missing X-Api-Key header"
}
}

Member Not Found​

{
"status": "error",
"error": {
"code": "203",
"message": "Member not found"
}
}

Invalid Budget Type​

{
"status": "error",
"error": {
"code": "1001",
"message": "Invalid or missing budgetType. Must be 'points' or 'credit'"
}
}

Invalid Date Format​

{
"status": "error",
"error": {
"code": "1002",
"message": "Invalid fromDate format. Use ISO 8601 format"
}
}

Error Codes​

CodeDescription
101Missing X-Api-Key header
102Missing X-Source-Type header
103Missing X-Source-Name header
104Missing X-Pos-Id header
105Missing X-Branch-Id header
203Member not found
1001Invalid or missing budgetType
1002Invalid fromDate format
1003Invalid toDate format
1011Invalid limit (must be an integer between 1 and 100)
1012Invalid offset (must be an integer of 0 or more)
1010Internal server error
  • Displaying member transaction history in a mobile app or web portal
  • Generating account statements for members
  • Auditing loyalty point or credit transactions
  • Providing transparency on balance changes