01 / Workflow
Reconcile the journey, not only the ending balance
Each stage contributes a fact the operating team may need later, from the original business reference to the recorded settlement result.
- 01
Start with the source record
Identify the card, crypto, invoice or other configured source and the payment reference attached to it.
- 02
Check the credited entity
Confirm which player, customer, invoice or order the payment is intended to credit.
- 03
Compare gross and fees
Review the recorded gross amount and fees rather than inferring them from the settlement value alone.
- 04
Follow state and destination
Use the timeline to compare confirmation evidence, settlement destination and the move from queued to completed.
02 / Operations
Fields that answer operating questions
The ledger is structured for investigation: every visible field should help explain ownership, economics, evidence or destination.
Payment reference
A stable operating reference connects the customer journey, API events and dashboard record.
Credited entity
The record identifies the player, order, invoice or customer the operator expects to credit.
Gross and fee breakdown
Separate values make it possible to explain why collected and settled amounts may differ.
Event timeline
State changes remain visible when new provider, network, dispute or reconciliation evidence arrives.
03 / Requirements
The ledger supports, but does not replace, accounting
Payfux provides operating records for payment review and reconciliation. The operator remains responsible for its books, customer balances, taxes and required financial reporting.
- A displayed state may change when reliable evidence identifies a reversal, dispute, network change or earlier record error.
- Settlement timing depends on the method, network, provider and review conditions; the state sequence is not a timing commitment.
- Corrections should preserve an audit trail and must not be used to create an unsupported customer liability.
04 / Questions
Questions operators ask
What information appears in a Payfux transaction record?
The described record includes source, gross amount, recorded fees, current state, credited entity, destination and settlement status.
Can operators search by player or order reference?
The operating model keeps player, invoice, order or customer context attached to the transaction. Exact search and filter controls are those available in the operator product.
Why can gross and settlement amounts differ?
Recorded fees, conversion terms or other agreed economics may affect the value entering settlement. The applicable schedule and product record control.
Does a completed state prevent every later change?
Not necessarily. Disputes, reversals, reliable new evidence or correction of a record error may require a later state or audit entry.
Can Payfux replace the operator's accounting system?
No such claim is made. Payfux provides payment operating records, while the operator remains responsible for accounting, tax and financial reporting.
Operations review
Map the records your team reconciles today
Share the references, fee fields, states and settlement destinations your payment and treasury teams need to connect.
Talk to onboarding