What this page shows
Card Approval Rates is a read-only snapshot of how often card deposits succeed.
It covers three card providers, NetworxPay, Paydex, and Carouseller, and splits
each one into Trusted and NonTrusted player traffic.
For every provider and traffic segment the page shows:
- the approval rate for today
- the approval rate over the previous 30 full days
- the change between the two, shown in percentage points
- the most common decline reasons recorded today
A separate panel at the bottom flattens today's decline reasons into a single list that can be aggregated by a Telegram bot.
When to use it
- check whether card deposits are succeeding at the normal rate right now
- spot a provider or segment whose approval rate has dropped against its 30-day norm
- see which decline reasons are driving today's failures
- compare Trusted against NonTrusted traffic for the same provider
How to read it
Each provider card has two segment blocks, Trusted and NonTrusted. Inside each block:
Todayis the approval rate since the reporting service's server-local midnight, with the successful count over the initiated count shown underneath30dis the approval rate over the previous 30 full days, ending at that server-local midnight today, with its own successful over initiated counts- the chip at the top right is the delta in percentage points, today minus the 30-day rate, where green is up, red is down, and grey is flat
Today top errorslists up to four decline reasons for that segment, each with a count and its share of that segment's failures today
The approval rate is the share of card deposits that succeeded. It is the number of successful card deposits divided by the number of card deposits that were started, for that provider and segment, in that time window, shown as a percentage to one decimal.
Reading a zero or empty segment
The approval rate is always a number, never blank. When no card deposits were started
for a provider and segment in a window, the page shows 0.0% for that window rather
than a dash or N/A. A 0.0% rate with 0 / 0 counts underneath means there was no
card deposit traffic, not that every deposit failed. Always read the counts under the
percentage before reacting to a low rate, because a 0.0% over real traffic
(for example 0 / 40) is a genuine outage signal, while 0.0% over 0 / 0 is simply
no activity.
Time windows
Todaystarts at the reporting service's server-local midnight and runs to the moment the snapshot was generated30dis the 30 full days immediately before today, ending at that server-local midnight, and does not include today- the two windows do not overlap, so the delta compares today against a clean prior baseline
Last updatedshows when the reporting snapshot was generated
The deployed server timezone is not shown on this page. Do not assume that these boundaries use the operator's browser timezone or UTC.
What counts as a card deposit
Only deposit transactions are included. The provider is resolved from the payment
provider on each deposit. Carouseller rows count only when the provider is
carouseller_cc, or when carouseller has a card indicator: Visa/Mastercard method
text, method code 501/502/3001/3002, matching Carouseller payment-method text,
non-empty card last digits, or a BIN. Deposits that cannot be matched to one of the three providers
are dropped from the cards. Deposits whose player cannot be classified as Trusted
or NonTrusted are excluded from the provider cards and are tracked separately as an
unclassified count in the snapshot response, which this page does not display.
Decline reasons
Today top errors and the bottom feed only count deposits that ended in a terminal
failure today, such as failed, cancelled, rejected, or expired. Successful and still
pending deposits are not counted as errors. Each reason is normalized to a canonical
label so the same decline can be grouped across providers and brands. The share shown
next to each reason is that reason's count divided by the total failures for that
provider and segment today.
Refresh behavior
- the page reloads the snapshot automatically about once a minute
Refreshforces an immediate reload- by default, the owner service caches a snapshot for 30 seconds
- the cache duration is deployment-configurable and can be disabled
- a refresh during the active cache window can return the same generated time
Why this can differ from other reports
- this report counts card deposits only and ignores other deposit methods
- it is a count-based approval rate and carries no money amount or currency, so it will not match revenue or deposit-value reports
- the rate excludes deposits that cannot be matched to a provider or to a Trusted or NonTrusted segment, so the counts here can be lower than a raw all-deposits count
- today is a partial day until midnight, so an early-day rate can swing on low volume
Known caveats
- an empty segment reads as
0.0%, which looks the same as a genuine all-failed segment; the counts underneath are what tell them apart - the today window is partial and low-volume early in the day, so the delta can look dramatic before enough deposits accumulate
- unclassified players and unmatched providers are excluded from the visible cards
- the decline-reason list is limited to the top reasons per segment on the page
- resolved reason-text ordering is not guaranteed when several raw texts map to one normalized reason
Access and dependencies
The page requires GamingRevenueReport: R. It is read-only and is intended for payments, risk, senior operations, or management users who monitor card-deposit performance.
The system setting casinoBackendAddress tells the reporting service where to request the casino-owned snapshot. It affects whether the report can be reached; it does not define provider classification or approval-rate formulas.