Repayment history

GET /api/v1/mystery/billing/repayments packs:read

Paginated history of your verified on-chain repayments, newest first. amount_usdc is what the chain says arrived at the repayment address; applied_usdc is how much of it has been consumed stamping usage rows repaid (amount − applied across all rows = your unapplied credit).

Try it GET /api/v1/mystery/billing/repayments?limit=10

These inputs are shared across all docs pages — an id entered here carries over.

response
200 38ms preloaded server-side with the default context
object · 3 keys 
{
  "success": true,
  "data": {
    "repayments": []
  },
  "pagination": {
    "limit": 10,
    "offset": 0,
    "has_more": false
  }
}
curl (tracks the inputs above) 
curl -X GET 'https://service.rip.fun/api/v1/mystery/billing/repayments?limit=10' \
  -H 'X-API-Key: rip_…'

Request fields

FieldTypeRequiredDescription
limit / offsetquery number—Pagination (default 50, max 100)

Response fields (data)

FieldDescription
repayments[].tx_hash / amount_usdcThe tx and the on-chain-verified USDC received
repayments[].applied_usdcPortion consumed settling usage rows (never exceeds the amount)
repayments[].from_address / to_address / token_address / block_numberOn-chain audit detail decoded from the transfer