What this tab shows

Players / KYC Status is the player-level document and verification workspace. It shows submitted or requested documents, verification tags, provider verification state, the action controls used to approve or reject document items, and the separate used-cards document block for successful deposit cards.

When to use it

Use this tab when you need to:

• review the player's uploaded verification documents
• filter KYC documents by tag
• inspect external verification status from Bynn or SumSub-related flows
• approve, reject, cancel, or re-request a document
• review previously used deposit cards and their document status

How to read it

The tab is centred on a paginated document table. Each row represents one user-document record and can include:

• a document preview
• tag chips
• third-party verification state
• operator/actionee metadata
• one or more KYC actions based on the current status

Below the document table, the tab renders a second block: User success deposit cards. That block merges successful deposit-card history with stored card-document records so operators can see which cards already have submitted documents and open Update/View for that card.

Filters and controls

The player tab always scopes the document list to the selected player and returns every document status for that player. The generic KYC list can show a Status filter, but the player tab hides that filter and does not apply a pending-only default.

The Search by Tag box has a two-step state:

• typing changes only the input value
• pressing Enter or Apply Filters commits the tag search and reloads the list
• Clear removes the committed tag search
• clicking a visible tag chip immediately applies that tag as the search

Pagination controls the document table only. The used-card block is loaded as its own dataset and is not paginated by the document-table page selector.

Main actions

Pending document rows can be approved or rejected. Requested rows can be cancelled. Approved, cancelled, and other non-rejected rows can be re-requested. Rejected rows do not expose the re-request icon from this tab.

Add Document uploads a file for the player and creates a completed user-document record. It is not the same as requesting a missing document from the player.

The card Update/View modal belongs to the used-card document flow. Submitting card files can create or update linked pending KYC document rows, with the number of required files driven by the configured card-verification label.

Known caveats

• 3rd Party Verification and 3rd Party Verification Date are provider-status summaries. They do not replace manual operator review of the actual document.
• The real provider-backed path on this tab is Bynn. SumSub values visible on the list are currently controller-injected placeholder fields and should not be treated as confirmed provider evidence.
• The action buttons depend on the document status. Pending records expose approve/reject actions, while requested or completed records expose a different action set.
• The row-level Verify by 3rd Party icon is visible for bynn documents, but its list-level click handler is not wired to the backend yet. The working Bynn submission flows currently live in the approval modal and the manual Bynn verification modal.
• Bynn-style dossier/report links appear only for documents where that provider context exists.
• Download filenames and Bynn submission references use the configured brand name when that setting exists.
• User success deposit cards is a separate merged dataset. It is built from successful deposit transactions plus UserCardsDocuments, so card rows can exist in required state even when no card-document record has been submitted yet.
• The card-document Update/View modal saves through the card-document flow; it is not part of the main approve/reject document flow.
• Cancelling a re-requested document returns that row to the approved state instead of deleting the historical document.