Castrump FAQ

The Situation an FAQ Page Covers

A player arrives at an operator's FAQ page with a specific transaction or account problem already in progress. A deposit has not appeared, a withdrawal is marked pending, a document was rejected, or a bonus did not credit. The FAQ is the first place the operator routes that player, and the page is built to absorb the questions that repeat across thousands of accounts. What the FAQ can do is describe the operator's standard process: which steps a withdrawal passes through, which documents the verification team commonly asks for, which payment routes appear in the cashier and what happens when one fails. What the FAQ cannot do is tell the reader anything that depends on their own account. It cannot say why this particular deposit is delayed, whether this particular withdrawal will be released today, or whether this reader's document is sufficient. Those answers live in the account itself, in the transaction history, or in a direct support reply, and the FAQ's real function is to tell the reader which of those places carries the answer they need.

The Castrump FAQ is therefore best read as a map of processes, not as a promise about outcomes. A reader who treats it as a set of guarantees will be misled; a reader who treats it as a directory of where each binding answer lives will get exactly what the page can give. The rest of this article walks through that distinction, item by item.

Which Questions an FAQ Answers Bindingly

An operator FAQ can answer questions about process and route because those things are the same for every account. The page can state, for example, that a withdrawal passes from the cashier to a processing queue, then to a verification check, then to a payment provider, and that the player sees a status label change at each stage. That sequence is not a fact about any one reader; it is the operator's published procedure, and the FAQ is the natural place for it. The same applies to the list of documents the verification team accepts: a passport or national ID for identity, a recent utility bill or bank statement for address, and so on. The FAQ can list those document types without knowing anything about the reader, because the list is the same for everyone.

Route questions work the same way. An FAQ can say which deposit methods appear in the cashier for the reader's country, which of them also support withdrawals, and what happens when a method does not support withdrawals — the player must choose another route. It can say whether the operator requires the withdrawal method to match the deposit method, and what the cashier does when no matching method exists. All of that is process knowledge, and it is binding in the sense that the operator will not normally deviate from it. The FAQ is the right place to read it, and the reader should read it before contacting support, because support will repeat the same process back.

Where the FAQ Stops: Account-Dependent Answers

The boundary is easy to state and hard to respect in the moment. Any question whose answer changes depending on which account is asking is a question the FAQ cannot answer. "Why is my withdrawal still pending?" is the clearest example. The FAQ can say that a withdrawal remains pending until verification completes, until the processing queue reaches it, or until the payment provider confirms receipt. It cannot say which of those is true for this reader, because that depends on the reader's documents, the reader's transaction history, and the operator's internal queue at this moment. The FAQ's answer is a list of possible causes; the binding answer is in the account's transaction history or in a support reply that names the specific cause.

The same boundary applies to bonus questions. An FAQ can explain how wagering requirements work in general, what counts as a qualifying game, and what happens when a player withdraws before the requirement is met. It cannot say whether this reader's bonus is still active, how much wagering remains on this reader's balance, or whether this reader's play has satisfied the requirement. Those numbers are account state, and they change with every bet. The FAQ is the wrong place to look for them, and a reader who asks the FAQ for them will get only the general rule. The reader should instead open the bonus terms attached to the specific promotion, or the account's bonus balance screen, or a support reply that quotes the current figure.

Verification questions sit on the same boundary. The FAQ can list the document types the operator accepts and the common reasons a document is rejected — blurry image, expired document, name mismatch, address outside the accepted age range. It cannot say whether this reader's document will pass, because that depends on the document itself and on the operator's review. The FAQ's rejection list is a checklist the reader can use before submitting; the actual decision is made by the verification team, and the reader learns it from the account status screen or from an email. The FAQ does not make that decision and cannot predict it.

What Changes Without Notice, and What Stays Fixed

A reader should treat the FAQ as a snapshot of the operator's process at the time the page was last updated. Some items on it change frequently, and a figure read today may not hold next month. The clearest examples are the payment routes themselves. An operator adds and removes deposit methods as providers change their terms, as countries change their rules, and as the operator's own risk team adjusts. The FAQ may say that a certain method is available, but the cashier is the only place where the reader sees the current list for their country and currency. The FAQ's list is a guide, not a guarantee.

Bonus terms change even more often. A promotion's wagering multiple, its qualifying games, its maximum bet during wagering, and its expiry window are all set per promotion, and the operator changes them from one campaign to the next. The FAQ may describe the standard wagering multiple, but the binding figure is on the promotion's own terms page, attached to the specific bonus the reader claimed. A reader who relies on the FAQ's general figure instead of the promotion's specific one is reading the wrong document.

What stays fixed, or changes slowly, is the account process itself. The sequence of verification steps, the rule that a withdrawal cannot be released to a third party, the rule that the account must be verified before a first withdrawal, the rule that self-exclusion cannot be undone on request — these are structural, and the FAQ is a reliable place to read them. The reader can treat them as stable. The distinction matters because it tells the reader which parts of the FAQ to trust as binding and which parts to treat as a pointer to another page.

Reading the FAQ Against the Terms and the Account

The FAQ is one of three documents that together answer a player's question, and the reader's job is to know which one carries the binding answer. The FAQ carries the process. The terms and conditions carry the rules that govern the account as a whole: what constitutes bonus abuse, what triggers a source-of-funds check, what the operator may do when a rule is breached. The account itself carries the state: the current balance, the pending withdrawal, the verification status, the active bonus and its remaining wagering. A reader who asks the FAQ for a rule that lives in the terms will get a summary at best; a reader who asks the FAQ for a state that lives in the account will get nothing useful.

The practical reading order is this. First, read the FAQ to learn the process and the vocabulary: what "pending" means, what "verification" means, what "wagering" means. Second, open the specific page that governs the transaction: the promotion's terms for a bonus, the cashier for a payment route, the account history for a transaction status. Third, if the answer is still not visible, contact support and quote the specific transaction ID or bonus code. The FAQ teaches the reader how to ask the question; it does not answer the question for this account.

One more point about the FAQ's limits. An FAQ page is written for the typical account, and the operator's support team is allowed to deviate from it in individual cases. A withdrawal that the FAQ says takes a certain number of business days may clear faster or slower for a particular reader, because the reader's verification status, payment method, and transaction amount all affect the actual path. The FAQ's timeframe is an estimate of the standard path, not a promise about this transaction. The binding answer for this transaction is in the transaction history, and the reader should read that screen before concluding that the FAQ was wrong.

When the FAQ Does Not State an Item

An FAQ page is also informative by what it omits. If the FAQ does not state the wagering multiple for a bonus, the reader cannot assume a figure from memory or from another operator. The binding figure is on the promotion's terms page, and if that page also omits it, the reader should ask support before claiming the bonus. The absence of a figure is itself the answer: there is no figure the reader can rely on, and the only safe move is to get it in writing from support.

The same applies to payment routes. If the FAQ does not list a withdrawal route for a deposit method, the reader cannot assume one exists. The cashier is the only place where the current mapping is visible, and if the cashier shows no withdrawal route for the method the reader used to deposit, the reader must choose another method or contact support. The FAQ's silence on this point is not an oversight; it is the operator declining to promise a route that may not exist for this reader's country or currency.

Finally, if the FAQ does not state a verification document list, the reader should not guess. Submitting the wrong document delays the withdrawal and may trigger a longer review. The reader should ask support for the current list before submitting anything, and should treat the support reply as the binding answer. The FAQ's silence means the operator has chosen not to publish the list, and the reader's only safe route is to ask.

FAQ

Does the Castrump FAQ tell me why my withdrawal is pending?

No. The FAQ can list the possible causes — verification incomplete, processing queue, payment provider delay — but it cannot say which one applies to your account. The binding answer is in your transaction history or in a support reply that names the specific cause.

Can I rely on the FAQ's deposit method list?

Only as a guide. The cashier screen shows the current methods for your country and currency, and that screen is the binding source. If the FAQ lists a method that the cashier does not show, the cashier wins.

Where do I find the wagering requirement for my bonus?

On the promotion's own terms page, attached to the specific bonus you claimed. The FAQ may describe a standard multiple, but the binding figure is per promotion, and it changes between campaigns.

What should I do if the FAQ does not answer my question?

Open the specific page that governs the transaction — the cashier for payments, the promotion terms for bonuses, the account history for status — and if the answer is still not visible, contact support with the transaction ID or bonus code. The FAQ teaches you the vocabulary; support gives you the binding answer.

This page is an independent summary of what an operator FAQ page covers and where it stops. It is not published by Castrump, and it states no figure or status for that operator; Castrump's own FAQ and the specific pages it points to are the only binding sources.

Play responsibly

Gambling should be treated as paid entertainment, never as a way to earn income or recover losses. 1-800-MY-RESET (1-800-697-3738)

18+ or 21+ depending on where you are; follow the minimum age that applies to you.

This article is general information about how these mechanics work. It is not legal advice and not a recommendation to gamble or to use any particular operator. Availability and legality differ by jurisdiction — check the rules that apply where you are.