For the complete documentation index, see llms.txt. This page is also available as Markdown.

Payments (User)

Operations related to payments from a user viewpoint.

Get the authenticated user's payments

get

Retrieves payments belonging to the authenticated user. Use the page parameter to paginate results. Each payment may include the raw generic player identifier in the player_id field.

Authorization:

  • Requires a valid JWT Bearer token.

  • The token must identify an authenticated end user.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Query parameters
pageintegerOptional

The page number to retrieve.

Default: 1
max_pageintegerOptional

The maximum number of elements per page. This number must be between 5 and 50.

Default: 50
Responses
200

Successful operation

application/json
payment_countintegerRequiredExample: 12
get/user/payments
GET /v1/user/payments HTTP/1.1
Host: api.tip4serv.com
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
  "payments": [
    {
      "id": 10203,
      "status": "Paid",
      "cart": "VIP+",
      "sub_id": 1,
      "date": 1761234717,
      "amount": 6.49,
      "currency": "USD",
      "username": "RandomUser123",
      "identifier": "discord_id:274785054121525248",
      "player_id": "C84A567",
      "gateway": "PayPal",
      "details_page": "https://tip4serv.com/dashboard/payment-details?id=10203"
    }
  ],
  "payment_count": 12
}

Last updated