Read members listed for point abuse

# Read members listed for point abuse

## Find and select a member

Use members_list with type POINT_ABUSE for the selected channel. The list is separate from channel bans and viewing restrictions.

```json
{"channelCode":"selected-channel","type":"POINT_ABUSE","page":1,"limit":15}
```

These are input examples, not observed results. The default page is1 with15 rows; sizes15/30/50/100 are supported. Search is passed unchanged as search; matching and ordering stay server-defined. Follow nextPage only for the needed scope. Full identifiers remain masked unless includeDistinctIds:true.

Copy the row id into member_get.profileId and select pointAbuse:true. The bridge resolves the member identifier internally; do not supply a wallet, account ID or separate distinctId.

```json
{"channelCode":"selected-channel","profileId":7,"pointAbuse":true}
```

Omit include, membershipHistory, points and viewRestriction. The bridge verifies that the point-abuse detail belongs to the same profile, identifier and channel. The single returned console link opens the selected point-abuse detail. A list link preserves its page and search.

## Interpret the amount and status

The detail balance comes from inChannelWalletSummary and the observed positive branding ratio. The separate currentAmount source field is not a substitute. Missing wallet data returns balance.status unavailable, while an observed zero remains available with a zero amount. Missing or invalid branding is an error; the bridge does not invent a ratio of one. Source numbers and their quotient are not an exact-decimal financial statement.

The source lists these members in its point-abuse view. This is not an independent determination of misconduct or current visitor access. The console uses a fixed explanatory label, so the bridge does not invent an individual server-provided reason. Null detection dates and missing images remain absent rather than being fabricated.

## Access, recovery and human actions

OWNER or DELEGATEE with MANAGE_MEMBERS and explicit POINT service configuration are required. MANAGE_MONETIZATION or PAY configuration is not a substitute. Missing configuration never falls back to the core API. Changed member/branding/response/context data, malformed responses or oversized bodies return no partial result. Retry a fresh read when needed; these reads have no task to resume.

An empty first page is valid. MEMBER_POINT_ABUSE_PAGE_OUT_OF_RANGE requires an explicit valid page request; the bridge does not read a replacement page automatically. No automatic traversal or CSV export is performed.

Use the exact returned point-abuse console destination for a requested penalty waiver. The MCP does not waive penalties, reward or withdraw points, change balances, ban a member or execute a payment. Reading or opening the link does not complete those actions.