Payments, treasury and working capital
Take payments. Move money. Fund growth.
Accept card and crypto deposits, preview swaps, review transfers, credit Vault rewards and manage Bankroll requests from one Payfux flow.
- Card + crypto deposits
- Swap + transfer previews
- Vault + Bankroll workflows
Card / crypto collection
A deposit lands with its reference attached.
ReferenceORDER-7192
- Player
- P-20491
- Settlement
- USDC · sample
demo.deposit.confirmed · reference: ORDER-7192One continuous flow
One reference through every money movement.
The same reference and state remain visible while the focused instrument changes purpose.
Player P-20491 · BTC demo sourceP-20491
Northstar / payment threadORDER-7192
USDC demo settlementUSDC- 01Detected
- 02Matched
- 03Credited
- 04Delivered
demo.deposit.confirmed · reference: ORDER-7192200 OKBranded payment collection
Your brand in front. Payment context behind it.
Configure a branded payment surface while the amount, method, player reference and return flow stay attached to the operator record.
- 01Hosted or embedded
Choose the surface that fits your cashier.
- 02Method-aware
Options vary by customer and configuration.
- 03Operator-linked
Every payment keeps its player and return-flow context.
PayfuxSecure demo checkoutDemo- 1Payment opened
- 2Funds detected
- 3Reference matched
- 4Credit recorded
demo.deposit.confirmed · ORDER-7192Illustrative sample data. Payment methods, assets, networks and availability are confirmed during onboarding.
Payment operations workspace
Gross, fee and net on one receipt.
Search a player or payment, inspect its state, then reconcile gross, example fee and net without leaving the record.
Explore the operator demo- 1DetectedConfirmed
- 2MatchedConfirmed
- 3CreditedConfirmed
- 4DeliveredDelivered
demo.deposit.confirmed · ORDER-7192200 OK05 / Vault
12% APY, credited daily. 48-hour withdrawals.
Vault is designed for eligible Payfux wallet holders with balances above $10,000. Program details show a 12% APY, credited daily, with a 48-hour withdrawal processing period.
Vault rewards are funded from realized Payfux transaction fees and financing revenue, not from customer principal.
Eligibility, rate and program terms are confirmed before enrollment. Returns are variable and not guaranteed.
Explore Vault- 1Withdrawal requested
- 248-hour processing
- 3Transfer initiated
04 / Bankroll review
Working capital, reviewed against real operations.
Established, high-volume companies can request tailored Bankroll capacity to support larger customer transactions and payout peaks under separately agreed limits. We review activity, operating history and platform fit before presenting any terms.
A request is non-binding. It is not an approval, commitment to lend or promise of any amount, rate or limit.
Review the applicationModeled payout demand remains inside the company-funded reserve.
- PDFCompany recordsRegistration · ownership✓
- CSVActivity & volume12-month operating sample✓
- PDFOperating statsPayout peaks · disputes✓
- IDDocuments & IDAuthorized representative✓
- TXTRe-contactChannel · language · time zone✓
Payment API handoff
Send your reference. Receive it back.
Start a payment flow with the identifier you already use, then inspect the event that carries that context back.
Open integration docs- 01Example
reference: ORDER-7192 - 02Northstar / payment thread
state: confirmed - 03Event receipt
demo.deposit.confirmed
Before integration
Practical answers about iGaming payment operations.
Onboarding is adapted to the business and risk profile. Requirements vary by product, jurisdiction and transaction profile.
Onboarding is risk-adapted. Requirements vary by product, jurisdiction, transaction profile and risk, and are confirmed during integration review.
Settlement moves through visible states—queued, then completed—and the timeline for each payment is shown in the operator view. Timing depends on payment method, network conditions and review status.
Supported assets and networks are confirmed per operator during onboarding. Examples on this site use demo data and are not a supported-asset list.
A player deposit address keeps payment attribution and event history attached to the correct account. Address options are confirmed for each operator during onboarding.
Card-data handling depends on the checkout configuration and payment provider. The applicable integration model is documented during setup.
No. Vault returns are variable and not guaranteed. Eligibility, rate, liquidity, withdrawal timing and risk are set out before enrollment.
Established companies can submit a non-binding request. Every application is reviewed individually; an application is not an approval or funding commitment.
Handling depends on the payment method, provider and customer configuration. The applicable process is documented during integration review.
Availability varies by jurisdiction and product. Coverage for a specific business is confirmed during onboarding.
See the complete payment thread
Start with the product. Then inspect the integration.
Open the read-only workspace or move directly into the API documentation.