01 / Workflow
From player payment to operator record
The payment journey stays connected to the player or order that created it, so the operating team can follow what happened without rebuilding the story from separate tools.
- 01
Create the payment context
The operator starts a payment session or supplies the player, order and return-flow references needed for attribution.
- 02
Present the configured methods
The checkout shows the options available for the customer, amount, currency, location and account configuration.
- 03
Track the payment state
Payment records keep the gross amount, fees, credited entity and confirmation state together as evidence arrives.
- 04
Reconcile and settle
The operator view connects the transaction to its settlement destination and records the move from queued to completed.
02 / Operations
What the operating team can follow
Payfux is organized around the questions cashier, payments and treasury teams answer during a normal shift.
Player attribution
A payment reference or configured deposit address keeps the transaction and its event history attached to the intended player account.
Checkout ownership
Operators control the surrounding logo, colors, method presentation and return flow within their agreed configuration.
One transaction record
Gross value, fees, source, state, credited entity and settlement destination remain visible in one operating timeline.
Treasury handoff
Settlement records show the selected destination and current state without presenting a universal timing promise.
03 / Requirements
Built for approved business use
Payfux is a business service. Product access depends on the operator, its activity, jurisdiction, transaction profile and the results of onboarding.
- The operator remains responsible for its licences, player obligations, responsible-gaming controls and the legality of each market it serves.
- Payment methods, assets, networks, custody arrangements, fees and limits are those confirmed in the account or written product terms.
- Displayed product flows use sample records where identified and do not establish support for a particular provider, country, asset or network.
04 / Questions
Questions operators ask
Is Payfux only for online casinos?
No. The operating model supports payment workflows for online casinos, sportsbooks, crypto-native platforms and complex digital commerce. Access is assessed for each business and product during onboarding.
Can Payfux show card and crypto payment options together?
Payfux supports card and crypto collection in the described product scope. The options shown at checkout depend on customer location, amount, currency, provider status and account configuration.
Does Payfux support player deposit attribution?
The product flow keeps a payment reference or configured player deposit address attached to the correct account and event history. Address options are confirmed with each operator.
When does settlement complete?
The operator view shows a settlement moving through visible states such as queued and completed. Timing depends on the payment method, network conditions, provider review and customer configuration.
What does onboarding review?
Requirements vary by product, jurisdiction, transaction profile and risk. Payfux may review the business, ownership, licences, expected activity and the people authorized to operate the account.
Operator onboarding
Map your payment flow with Payfux
Share the business model, operating markets, expected payment activity and the workflow your team needs to run.
Talk to onboarding