Account — transaction history

The dealer Account → Transaction History screen lists balance movements (top-ups, transfers, AI job charges, refunds) for the signed-in user. Integrators use the same upstream path with the user access_token.

Use your registration domain in the form body — not the API hostname.

Not usage-history

Per-job analytics use POST /api/v2/usage-history (action=stats / logs). Transaction history is the wallet ledger (paymentsHistory). See Usage history (preview).

Playground & Profile

Playground — Home feed → Platform → Transaction history when running npm run docs:stack. Profile → Account can load a recent ledger preview when signed in.

Upstream ledger

POST https://api.gommo.net/api/apps/go-mmo/users/paymentsHistory
Content-Type: application/x-www-form-urlencoded

Field	Required	Notes
access_token	yes	User session token
domain	yes	Registration domain
limit	yes	Dealer UI uses 500 (max per capture)
time_start	yes	Unix timestamp; 0 = no lower bound (all time)
time_end	yes	Unix timestamp; 0 = no upper bound
currency_name	optional	Empty = all types; e.g. credits_ai
source	optional	Filter by ledger source key; empty = all
language	optional	e.g. EN, VI
device_id, device_name, device_info	optional	Same pattern as login / transfer

PowerShell (replace domain; use a real token only in a secure session):

$domain = $env:GOMMO_API_DOMAIN
if (-not $domain) { throw 'Set GOMMO_API_DOMAIN to your registration domain' }
$h = @{ 'Content-Type' = 'application/x-www-form-urlencoded' }
$body = "access_token=$env:TOKEN&domain=$domain&limit=500&currency_name=&source=&time_start=0&time_end=0&language=EN"
Invoke-RestMethod -Method Post -Uri 'https://api.gommo.net/api/apps/go-mmo/users/paymentsHistory' -Headers $h -Body $body

curl.exe (Windows — set env vars first):

curl.exe -X POST "https://api.gommo.net/api/apps/go-mmo/users/paymentsHistory" ^
  -H "Content-Type: application/x-www-form-urlencoded" ^
  --data-urlencode "access_token=%TOKEN%" ^
  --data-urlencode "domain=%REGISTRATION_DOMAIN%" ^
  --data-urlencode "limit=500" ^
  --data-urlencode "currency_name=" ^
  --data-urlencode "source=" ^
  --data-urlencode "time_start=0" ^
  --data-urlencode "time_end=0" ^
  --data-urlencode "language=EN"

Response shape

Typical success body:

{
  "data": [
    {
      "fluctuation_type": "minus",
      "value_change": 720,
      "value_last": 487900,
      "currency_name": "credits_ai",
      "source": "createImageSeedream45WithAICredit",
      "message": "Create image with AI Credit [GPT Image 2 - low]",
      "created_time": 1789442037,
      "id_base": "03883f3e0cbb4aaa"
    }
  ],
  "runtime": 0.12
}

Field	Meaning
fluctuation_type	plus (credit in) or minus (debit)
value_change	Amount (positive magnitude)
value_last	Balance after this row
source	Ledger key — e.g. sendBalances, receivedBalances, chatAiUsage, refundAICreditCreateVideoError
object_id	Related job/pool id when present
from_user	Counterparty on some P2P rows

Client-side summary (dealer UI): sum value_change where plus → total in; minus → total out; net = in − out. Group by source for the “By source” table.

P2P transfer rows: outgoing sendBalances (minus), incoming receivedBalances (plus). See Transfer credits.

Mode B (optional gateway)

POST {gateway}/gateway/credits/transactions — Bearer required; JSON body:

{
  "limit": 500,
  "currency_name": "",
  "source": "",
  "time_start": 0,
  "time_end": 0,
  "language": "EN",
  "device_id": "…",
  "device_name": "Browser 1",
  "device_info": "{\"device_type\":\"desktop\"}"
}

Server fills access_token and domain from Bearer + tenant. Omitted limit defaults to 500 on the gateway. Optional device_* match login; Playground sends browser device fields in the JSON body.

• Valid JSON upstream → pass-through (same HTTP status and body, usually { data, runtime }).
• Empty or non-JSON upstream → gateway JSON { success: false, code: "UPSTREAM_ERROR", raw: { http_status, body? } }.

OpenAPI: openapi.yaml — /gateway/credits/transactions.

SDK: @ai-gateway/client — auth.listPaymentsHistory(). See SDK authentication.

→ Transfer credits · Change password · Session devices · Support tickets · Partner program · Creator rewards · Endpoint map · Deploy → Self-host (advanced)