JackCode navigationCreate, launch and scale iGaming products.
Change language
Practical guide

Transaction statuses

Flexible status system in the back office: tracking the status of applications, transactions and user actions - from waiting to error and rejection.
Expert Igor Chernov

Managing transactions, claims, and user activities in the back office requires a clear status system that reflects the current status of each process. We implement a convenient model with the main statuses - "Pending," "Successful," "Error," "Rejected," which apply to all key operations: deposits, conclusions, requests for support, accruals, KYC and much more.

Basic statuses and their purpose

Status Appointment
Expects Operation started but not yet completed (in process, under review)
Successfully Operation completed with no errors, result committed
Mistake The operation completed with a technical error or system failure
Rejected Transaction was manually rejected or failed automatic review

Where statuses apply

Deposits and conclusions

Bonus accruals

Verification Requests

Support tickets

Orders, reservations, transactions

Internal processes (KYC, limits, locks, etc.)

Status System Functions

Automatic switching at process termination

Manual status management (by role)

Status change notifications

Logging change history

Filtering and Status Reporting in the Interface

Advantages

Increase transparency of all processes

Rapid operator orientation by task status

Responsive Error and Deviation Control

Unified approach for different modules

Reasonable history of each transaction

Where especially important

Casinos and financial platforms

Products with claims, transactions and manual moderation

Services with KYC, tickets, requests and balance

Marketplaces, SaaS and products with operational cycle


The status system is an indicator of the life of all processes. We will help you implement a single, logical and customizable approach to statuses so that every step in the system is understandable and manageable.