Why we say no to some clients.

Xavion Capital has spent more than ten years building relationships across a network of over 120 banking and payment institutions in 19 jurisdictions, and those relationships were not given to us — they were earned, mandate by mandate, by consistently bringing files that were what we said they were. Every institution in that network extends us a form of trust that a first-time applicant does not get: a reasonable presumption that a file we have prepared has been genuinely screened, that the ownership is as described, and that the business narrative matches the actual activity. That presumption is the single most valuable asset the firm has, and it is entirely dependent on us saying no often enough that our yes still means something.

This is not an abstract compliance posture adopted for appearances. It is the mechanism that makes the rest of the model work. When we bring a file to a partner institution, that institution's underwriting team spends less time re-verifying our screening than they would on an unknown introducer, because our track record has earned a shorter path through their process. The moment we let one problematic file through, that shorter path closes — not just for that client, but for every other client whose file happens to sit in the same queue afterward. Institutions do not forget an introducer who sent them a sanctioned counterparty or a concealed ownership structure, and they do not distinguish between an honest mistake and a deliberate one when deciding whether to keep working with us.

There is also a client-protection dimension that is easy to underweight when a founder is focused on getting an account open this quarter. A business built on an unverifiable source of funds, an undisclosed licensing gap, or a concealed ownership structure is not simply harder to bank — it is a business carrying a risk that will eventually surface, whether through a periodic account review, a correspondent bank's own screening, a regulator's information request, or a media report. When it surfaces, the consequence is rarely a polite decline. It is an account freeze with funds trapped inside it, a suspicious activity report filed against the business, and in some cases a referral to a financial intelligence unit — all of which are dramatically worse outcomes than never having opened the account in the first place.

This document sets out, as plainly as we can, the categories of mandate we decline and why. It is written for two audiences: prospective clients who want to understand what an honest first conversation with us looks like before they invest time preparing a file, and for anyone evaluating whether an advisory firm's compliance posture is real or decorative. We would rather lose a mandate at the first call than take it on and have it fail — expensively, publicly, or both — eighteen months later.

None of what follows is legal or tax advice, and it is not a substitute for independent legal counsel in your own jurisdiction. It is a description of how we screen mandates and why, offered as general information so that a prospective client can self-assess before engaging us.

The first and least negotiable category is sanctions exposure, at any level of the ownership or transaction chain. Before we take on a mandate, every beneficial owner, director, and, where relevant, major counterparty is screened against the sanctions lists that apply across the jurisdictions our network operates in, together with politically exposed persons registers and adverse media databases. A direct hit against an applicable sanctions list ends the conversation immediately and permanently — there is no remediation path, no waiting period, and no structuring that changes the outcome, because the institutions in our network apply the same screening independently and will find the same result.

Adverse media is a more nuanced category, and we treat it that way rather than applying a blanket exclusion. A single dated news article referencing a settled commercial dispute is different from a pattern of reporting describing fraud allegations, regulatory enforcement action, or a criminal investigation. Where adverse media exists, we ask for the full context and any documentation that resolves or explains it — a court judgment showing a dispute was resolved in the client's favour, a regulator's closing letter, a settlement agreement — before forming a view. What we will not do is proceed on the basis of an unsupported assurance that a negative report is 'not accurate' or 'old news' when the underlying allegation involves the kind of conduct that a receiving institution's own screening will flag and that we would then have to explain, or fail to explain, on the client's behalf.

Indirect sanctions exposure catches more prospective clients than direct exposure does, and it deserves particular attention because it is often unintentional. A business that is clean on its own ownership and activity can still carry exposure through a major supplier, a joint venture partner, or a significant customer concentration in a sanctioned or heavily restricted jurisdiction. We map this exposure as part of our initial screening, and where it exists at a level that would concern a receiving institution, we say so directly rather than let the client discover it later in an underwriting cycle that ends in decline. In some cases the exposure is genuinely immaterial and explainable; in others it is a structural feature of the business that needs to be resolved — by exiting the relationship or the customer segment — before any banking application has a realistic prospect of success.

We also screen for exposure that falls short of formal sanctions but sits inside jurisdictions or sectors subject to broad-based restrictions from major correspondent banking networks. A business can be entirely legal in its home jurisdiction and still be effectively unbankable through the mainstream correspondent system because of where its counterparties or customers sit. Where that is the case, we say so plainly at the outset rather than accept a mandate we already know cannot be placed within our network, because taking a fee for a search we know will not succeed is itself a form of the misrepresentation we decline to engage in.

Finally, screening is not a one-time event at intake. Sanctions lists and adverse media profiles change, sometimes quickly, and a mandate that screens clean on day one can screen differently three months later if a new designation or a new report emerges. Where that happens mid-mandate, we re-run the assessment and tell the client immediately what it means for the work in progress, rather than continue placing a file we know has since changed status.

A meaningful share of the mandates we decline involve a business that is, in substance, conducting a regulated financial activity — payment processing, e-money issuance, deposit-taking, investment management, or lending — without the authorisation that activity requires in the jurisdictions where its customers sit. This is different from the licence-mismatch remediation work we do for clients who are close to correctly licensed but have a gap our companion guide on why banks reject applications addresses; this is a harder line about businesses that have no licence at all and no credible near-term path to obtaining one, while continuing to operate the activity regardless.

The distinction that matters to us is intent and trajectory, not perfection. A founder who has identified a licensing gap, has engaged counsel, and is genuinely working through an authorisation process while operating a scaled-back version of the activity in the interim is in a fundamentally different position from a founder who wants us to find a bank account so the unlicensed activity can continue or expand while the licensing question is deferred indefinitely. We will work with the first. We will not work with the second, because introducing an unlicensed regulated business into our banking network exposes every institution in that network to a regulatory action neither we nor they can see coming, and exposes the founder personally to a liability that a bank account does nothing to reduce and quite a lot to increase, since a functioning account is often the detail that turns a regulator's suspicion into an enforcement priority.

This shows up most often in three areas: payment aggregation or facilitation conducted by an entity with no payment institution or equivalent licence in the jurisdictions its merchants or customers are based in; deposit-taking or yield-generating products, frequently marketed as 'savings' or 'staking' features, offered to retail customers by an entity with no deposit-taking or investment authorisation; and lending or credit products extended to consumers in a jurisdiction that requires a specific consumer credit licence the lender does not hold. In each of these categories, the underlying commercial idea is often entirely legitimate — the problem is exclusively the absence of the authorisation the activity requires, and that absence is not something a banking relationship can paper over.

Where we see a founder who is close — activity narrowly scoped, licensing application genuinely in progress, credible counsel engaged, realistic timeline — we will often engage on a conditional basis, structuring the mandate around the licensing milestone rather than around the current unlicensed state. That is meaningfully different from taking on a mandate where the unlicensed activity is the entire business model and there is no plan to change that, which we decline regardless of the strength of the rest of the file.

We would rather tell a founder directly, in the first call, that the business as described needs a licence before it needs a bank account, than accept a scoping fee for a search that either cannot succeed or that succeeds only by placing the business with an institution that has not properly screened the activity — an outcome that ends badly for the client regardless of how it begins.

We decline mandates where a beneficial owner's source of funds or source of wealth cannot be documented to a standard that a receiving institution will accept, and where the gap is not a matter of assembling existing evidence but reflects an actual absence of a legitimate, traceable origin. These are different situations that we treat differently. A founder who has the evidence — bank statements, a sale agreement, tax filings, brokerage records — but has not yet organised it into a coherent narrative is a normal piece of preparatory work we do routinely. A founder who has no such evidence because the funds genuinely cannot be traced to a legitimate source is a mandate we will not take on, regardless of how the funds are described.

The clearest version of this problem is a beneficial owner who wants to introduce a sum into a business that is disproportionate to any documented income, business history, or asset base, with an explanation that amounts to an assertion rather than evidence — 'accumulated savings', 'family support', 'trading profits' — and no supporting documentation that would let an underwriter, or us, actually verify the claim. We ask for the same standard of evidence a competent institution will ask for, and where that evidence cannot be produced because it does not exist, we say so rather than help construct a narrative around an unverifiable claim, because a narrative built to satisfy an underwriter rather than to reflect reality is itself a misrepresentation.

A related and increasingly common pattern involves digital asset wealth where the acquisition history is genuinely untraceable — funds that moved through mixing services, exchanges with no know-your-customer requirements, or a chain of wallets with no consistent identity attached at any point. We are not reflexively hostile to digital asset wealth; a substantial share of our client base has legitimate wealth originating in digital assets, and where the acquisition and disposal history is documented through reputable exchanges, on-chain analysis, and consistent identity verification, we work through it the same way we would work through any other asset class. Where the history has been deliberately obscured, however — and forensic on-chain analysis increasingly makes the distinction between 'complex' and 'obscured' visible — we will not attempt to construct a narrative around it.

We also decline where a beneficial owner is unwilling to disclose the underlying source at all, asking instead that we simply accept a summary description without supporting evidence. This is sometimes framed as a privacy concern, and we take genuine privacy concerns seriously — we handle client documentation under strict confidentiality and do not share more than an institution requires — but privacy is not a basis for withholding the evidence a compliance process is specifically designed to require. An unwillingness to produce evidence, as distinct from a preference for how that evidence is handled once produced, is itself a signal we take seriously.

Where a genuine documentation gap exists for a legitimate reason — records were not retained at the time, a jurisdiction's own record-keeping practices were informal, a liquidity event happened decades ago — we work with clients to reconstruct the position through secondary evidence: accountant letters, historical tax filings, sworn statements, and third-party corroboration. This is materially different from a gap that exists because there is nothing legitimate to reconstruct, and our screening process is built specifically to tell the two apart before we commit time to a mandate.

A request to keep the true beneficial owner off the record — through an undisclosed nominee shareholder, a director acting for an unnamed principal, or a structure specifically designed so that no institution can identify who actually controls the business — is one of the more common declines we issue, and one of the most consequential, because concealed ownership is the pattern beneficial ownership registers, correspondent banking due diligence, and financial intelligence units around the world are specifically designed to detect and were substantially strengthened over the last decade precisely because of it.

We distinguish carefully between a nominee arrangement that is fully disclosed and documented, and one that is not. A documented nominee — where a formal declaration exists stating clearly who the nominee acts for, available to be produced to a receiving institution on request — is a known, manageable structure that many jurisdictions permit and that institutions can underwrite with appropriate diligence. An undisclosed nominee, where the arrangement exists specifically so that the true owner's identity is not apparent to the bank, counterparty, or regulator, is not a structuring choice we will help implement or work around, because its entire purpose is to defeat the verification process our network relies on.

This category also covers a more subtle version of the same request: a client who is willing to disclose ownership in principle but wants us to present a simplified or incomplete ownership picture to a receiving institution — omitting an intermediate holding entity, describing a controlling party as a passive investor when they hold operational control, or leaving out a beneficial owner who falls just under a jurisdiction's disclosure threshold but who any reasonable observer would recognize as a controller in substance. We decline these requests as firmly as we decline outright concealment, because the effect on the receiving institution's understanding of who it is actually banking is the same either way, and because our own credibility with that institution depends on every file we submit being complete, not merely technically compliant with a threshold.

There is a legitimate category of complexity that looks similar on the surface but is not concealment: multi-generational family structures, employee ownership plans, or genuine estate-planning trusts where the ownership chain is complicated but fully documentable and where every layer is willing to be identified. We work through structures like this regularly, and complexity itself is never the reason we decline a mandate — the reason is always an unwillingness to have the true controlling parties identified, documented, and screened.

Where a client raises a nominee or simplification request in the first conversation, we treat it as useful information rather than as an automatic disqualifier for future business, because founders sometimes raise it out of a genuine but mistaken belief that this is how banking relationships are normally structured, rather than out of any intent to conceal. We explain why it will not work, what a compliant alternative looks like, and let the client decide how to proceed. Where the client persists after that explanation, the mandate ends there.

We decline any mandate where the underlying business economics do not support the returns or payment obligations being promised to customers or investors, regardless of how the business describes itself. This is not limited to businesses that use the word 'investment' — it applies equally to loyalty programmes, affiliate schemes, staking products, and pre-sale or presale-adjacent structures where new customer inflows are, on close examination, the only realistic source of funds available to pay existing obligations. The label attached to the product is irrelevant to our assessment; the cash flow mechanics are what we evaluate.

The diagnostic questions we ask are consistent regardless of sector: does the business have an identifiable, sustainable revenue source independent of new customer or investor inflows that is sufficient to meet its stated obligations; do the promised returns bear a plausible relationship to any real underlying activity, asset, or market the business claims to operate in; and would the business remain solvent if new customer acquisition slowed or stopped entirely. Where the honest answer to any of these is no, we decline the mandate regardless of how sophisticated the marketing materials, legal opinions, or corporate structure surrounding it appear, because sophistication in presentation is not evidence of underlying economic substance and, in our experience, is sometimes deployed specifically to compensate for its absence.

We also decline mandates involving deliberate misrepresentation to customers or investors even where the underlying cash flow is currently sustainable — a business that materially overstates its track record, fabricates audited performance figures, or misrepresents the risk profile of a product to the people buying it is engaged in fraud regardless of whether the scheme happens to be solvent today, and a currently-solvent fraud is not a lower risk to bank than an insolvent one, since the harm to end customers and the eventual regulatory and reputational consequence to every institution in the chain are the same.

This category requires genuine sector expertise to assess properly, and it is one of the reasons our screening process involves people who have actually underwritten payments, lending, and investment products rather than a checklist alone — Ponzi-shaped economics are sometimes obvious and sometimes genuinely difficult to distinguish from an early-stage, cash-flow-negative but fundamentally sound business subsidising growth with investor capital, which is a completely normal and legitimate financing pattern. The distinguishing question is always whether the business has a credible, documented path to a revenue model that does not depend indefinitely on new inflows, and whether that path is disclosed honestly to anyone whose money is at risk.

Where we decline on this basis, we tell the client specifically what element of the economics failed our assessment, because in a meaningful minority of cases the founder has simply not modelled the sustainability question rigorously and is able to restructure the product — adjusting the return structure, adding a genuine revenue line, or being explicit with customers about risk — in a way that resolves the concern. Where the founder is unwilling to make that change, or where the change is not commercially possible without abandoning the product entirely, the mandate ends.

Gambling is one of the sectors our network does bank, through institutions specifically appetite-matched for licensed gaming operators, and we have placed accounts for licensed operators across multiple jurisdictions. What we decline is gambling activity conducted without a licence valid for the jurisdictions the operator's customers are actually located in, or activity that is licensed in one narrow jurisdiction but marketed and accessible to customers in jurisdictions where that licence has no effect and where local law prohibits the activity entirely.

The diligence question we apply is specific: does the operator hold a licence, and does the customer base, verified through actual geographic and IP data rather than assumed intent, sit inside the jurisdictions that licence covers. A gaming operator that has genuinely restricted its customer base through effective geoblocking and payment-method restrictions to the jurisdictions it is licensed in is a bankable business we will work with. An operator that holds a licence in one jurisdiction as a formality while actively marketing to and accepting customers from jurisdictions where the activity is illegal is not, regardless of how the licence is described in the application materials.

Unauthorised payment aggregation follows a similar pattern and is, if anything, more common. A payment facilitator or aggregator that processes transactions on behalf of merchants without holding, or operating under, an appropriate payment institution or acquiring licence in the relevant jurisdictions is conducting a regulated activity without authorisation, and the fact that the underlying merchants may themselves be entirely legitimate businesses does not change the licensing requirement that applies to the aggregator itself. We see this most often in businesses that have grown organically from a single merchant account into a de facto payment facilitation service for a network of related or referred merchants, without anyone in the business having recognized that the activity itself had crossed into a licensed category.

Where the aggregation activity is small in scale, recently identified, and the founder is genuinely pursuing the required authorisation or restructuring the business to operate as a properly licensed payment facilitator or under an appropriate agent-of-record arrangement with a licensed partner, we will often work with the mandate on a conditional basis tied to that resolution. Where the activity is large in scale, has continued for an extended period with no licensing steps taken, or where the founder's stated plan is simply to keep operating unlicensed while we find a bank willing to process the volume, we decline.

The consequence of getting this wrong is not abstract. Payment processors and acquiring banks run their own merchant category and volume monitoring, and unlicensed aggregation activity that is discovered mid-relationship typically results in immediate account termination, held funds, and a merchant record that follows the business and its principals into future applications — a materially worse outcome than the delay involved in obtaining proper authorisation before scaling the activity.

We decline any mandate where funds have passed through, or the business model relies on, mixing services, tumblers, privacy coins configured specifically to defeat transaction tracing, or equivalent tools whose primary function is to sever the link between the origin of funds and their current holder. This applies regardless of whether the underlying source of the mixed funds was itself legitimate, because the effect of mixing is to make that question unanswerable to the standard a receiving institution requires, and an unanswerable question is treated by every serious institution as an adverse answer.

We distinguish this from legitimate privacy-preserving technology and legitimate confidentiality practices, which we support and, in the ordinary course of client work, help implement. A business that uses privacy-preserving infrastructure for genuine operational reasons — protecting customer data, securing communications, or using privacy features of a blockchain network that do not defeat compliance-relevant tracing when the operator cooperates with legitimate requests — is a different case entirely from one that has used a mixing service specifically to obscure the transactional history of funds now being introduced into the banking system. The test is not whether privacy technology was used; it is whether the specific tool used defeats verification of source and destination in a way that cannot be reconstructed through cooperation.

This category comes up most often with digital asset businesses whose historical treasury or founder wealth passed through a mixing service at some point, sometimes years before the business existed in its current form, and sometimes for reasons the founder describes as unrelated to concealment — a general preference for on-chain privacy, a security precaution against targeted attacks, or simple unfamiliarity at the time with how thoroughly such transactions can later be reconstructed and flagged. Whatever the original motivation, the practical effect on our ability to verify source of funds is the same, and it is a gap we cannot bridge through documentation because the documentation that would normally bridge it — a clear, traceable chain from origin to current holding — is precisely what mixing is designed to destroy.

Where mixed funds sit somewhere in a beneficial owner's history but represent a small, clearly bounded, and non-material portion of overall wealth, with the substantial majority of funds cleanly traceable through conventional means, we assess this on its facts rather than applying an automatic exclusion, and in some cases the mandate can proceed on the basis of the clean portion with the mixed portion excluded or separately addressed. Where mixed or obscured funds represent the majority or the entirety of the funds in question, or where the business's ongoing model depends on continued use of such tools, we decline.

We treat this category as firmly as sanctions exposure because the receiving institutions in our network treat it the same way — on-chain forensic analysis is now a standard part of due diligence at any institution with a functioning digital asset risk function, and a history that includes mixing is one of the most reliably detected red flags in that analysis, regardless of how the rest of the file is presented.

A distinct category of decline involves businesses that are not necessarily engaged in any of the specific activities described above, but that are described to us, and intended to be described to a bank, in terms that materially misrepresent the actual activity — a payment facilitation business described as software licensing, a high-volume trading operation described as personal investment activity, a marketing-driven multi-level structure described as retail product sales with no reference to the recruitment-based compensation model that actually drives most of its revenue.

The distinguishing feature of this category, compared to a simple licensing mismatch, is intent: this is not a founder who has an outdated or slightly imprecise description of a legitimate business, but a founder who is specifically asking us to help present the business as something other than what it is because the accurate description would attract more scrutiny, a different licensing requirement, or a different institutional risk category. We decline to draft, review, or submit any business narrative we know to be materially inaccurate, because doing so is a direct participation in misrepresenting the business to the institution whose trust our entire network depends on.

This shows up in specific, recognisable requests: asking us to describe a cryptocurrency exchange as a 'technology consultancy', asking us to omit an entire product line from a business description because that product line is what would attract enhanced scrutiny, or asking us to categorise transaction flows under a merchant category code that does not reflect the actual goods or services being sold. Each of these requests is asking us to participate in a misrepresentation to a regulated financial institution, and each is a mandate we decline outright, regardless of what the underlying business actually does, because the misrepresentation itself — independent of the underlying activity — is the disqualifying fact.

We recognise that business descriptions genuinely can be complex to write clearly, and that a founder without banking or compliance experience can produce a narrative that is technically accurate but confusing or incomplete without any intent to mislead. That is a normal piece of drafting work we do as part of every mandate we accept — clarifying, organising, and presenting a business accurately so that an underwriter can actually understand it. The line we will not cross is between clarifying an accurate description and constructing an inaccurate one, and in practice founders on the wrong side of that line generally know it, because the request is usually framed explicitly around what needs to be left out or reframed so the bank does not ask further questions.

Where we suspect, based on the information available, that a description is materially inaccurate but have not been asked outright to misrepresent it, we ask direct questions before proceeding, and a founder's answers to those questions — and willingness to produce supporting evidence for them — generally tell us within the first conversation or two whether we are dealing with a genuine complexity or a concealment.

A recurring and specific request we decline is one where a prospective client is otherwise prepared to be fully transparent with us, but asks that we withhold a specific, material fact from the receiving institution — a prior account closure, an ongoing regulatory inquiry, a pending litigation, a change in ownership that occurred shortly before the application, or a previous rejection from another institution. The request is sometimes framed reasonably: 'this isn't relevant to the current application' or 'the bank didn't specifically ask about that'. We do not accept this framing, because materiality is determined by whether a reasonable underwriter would want to know the fact before deciding, not by whether the application form contains a specific question that happens to surface it.

Our role in every mandate is to prepare and present a file accurately on the client's behalf to an institution that is extending us a form of trust based on our track record. Withholding a material fact from that institution, even at a client's specific request and even where the underlying fact might not itself be disqualifying, converts the submission into a misrepresentation we are actively participating in, and it is a risk we are not willing to take on the firm's credibility regardless of how the client frames the request or how minor they believe the omission to be.

This is also, in almost every case we have encountered, poor advice for the client even setting aside our own position. A previous account closure or an ongoing regulatory matter disclosed upfront, with context and remediation, is a manageable fact that a competent underwriter can weigh alongside the rest of a strong file. The same fact discovered later — through an institution's own background checks, a shared intelligence network, or the client's own subsequent disclosure obligations — is treated as evidence of concealment, which is almost always a worse outcome than the original fact would have produced on its own, and one that follows the client into every future application.

Where a client raises this kind of request, our first response is usually to work through why the fact feels disqualifying to them and whether that assessment is actually correct — founders frequently overestimate how damaging a disclosed and explained issue will be, compared to how damaging the same issue looks when it surfaces mid-review as an omission. In a meaningful number of cases, walking through the disclosure properly resolves the client's concern and the mandate proceeds on a fully transparent basis. Where the client insists on omission after that conversation, we decline to proceed.

We apply the same standard to our own conduct with institutions in our network: we do not selectively omit facts we know to be material when presenting a client file, and we do not allow a client relationship, however commercially attractive, to put that standard at risk. It is the single asset that makes the rest of the firm's work possible.

A significant share of the mandates prospective clients assume we will decline are, in fact, mandates we take on regularly — complex ownership structures, unconventional wealth origins, sectors with a difficult reputation among mainstream institutions, businesses that have already been declined elsewhere, and founders with a genuinely messy but honestly disclosed history. Difficulty, unconventional structure, and prior rejection are not disqualifying facts on their own; they describe most of the mandates we are actually engaged to solve, and are the reason a specialist advisory relationship exists in the first place rather than a founder simply approaching banks directly.

The line we draw is not about difficulty. It is about whether the underlying facts, once fully disclosed, describe a business or a set of individuals we can present to an institution honestly and defend if questioned. A mandate is hard, not disqualifying, when the complexity is real but the client is willing to have every layer of it documented, verified, and disclosed — a multi-jurisdictional ownership structure with genuine commercial reasons, a founder whose wealth originated in an unconventional but traceable source, a business in a sector most retail banks avoid but that operates under proper licensing with a genuinely sustainable model. We take these mandates on because doing the work to make a hard case bankable, honestly, is precisely the service we exist to provide, and it is where most of our client value actually gets created.

A mandate becomes something we will not do when the obstacle is not complexity but concealment or absence — an ownership structure designed specifically so the true controller cannot be identified, a source of funds that cannot be documented because there is nothing legitimate to document, an activity conducted without a required licence with no genuine plan to obtain one, or a request that we omit or misstate a material fact to a receiving institution. In each of these cases, more work does not resolve the problem, because the problem is not a documentation gap we can close through diligence; it is a fact pattern that a compliant file cannot accurately describe as bankable.

A useful practical test we apply, and that we would encourage any founder to apply to their own business before approaching any adviser: if every fact about the ownership, the source of funds, the licensing position, and the actual business activity were laid out in full, in writing, to a competent and reasonably experienced compliance officer, would the file survive that review on its own facts. If the honest answer is that it would survive, with work, preparation, and the right institutional match, that is a hard mandate we are well suited to help with. If the honest answer is that it would not survive regardless of how it is presented, no amount of narrative construction, structuring, or advisory work changes that outcome, and the more responsible course for everyone involved is to say so early.

We recognise that this line requires judgment, not just a checklist, and that reasonable, well-intentioned founders occasionally sit close to it without realising which side they are on. That is precisely why the first conversation matters as much as it does, and why we treat that conversation as a genuine assessment rather than a sales call.

Declining a mandate is sometimes read by a prospective client as an inconvenience or a missed opportunity on our part, and occasionally as evidence that we are simply being overly cautious. In our experience it is almost always the opposite: a decline issued early, with a clear explanation, protects the client from a materially worse outcome than a delayed search — an account opened on a misrepresented basis that is later frozen, a business that scales on unsustainable economics and collapses owing customers money, a founder who becomes personally exposed to a regulatory action that a properly structured business would never have triggered.

It also protects the receiving institution, which is extending real underwriting resources and real reputational exposure to every account it opens, and which is relying on introducers like us to have done genuine screening before a file ever reaches its desk. An institution that discovers, after the fact, that an introducer's screening was superficial or selectively applied does not simply decline the individual file — it re-evaluates the entire relationship with that introducer, which affects every other client whose mandate depends on that relationship remaining intact.

And it protects our own network, in a very literal sense. The 120-plus institutions we work with across 19 jurisdictions represent relationships built over more than a decade, and every one of them is available to our current and future clients specifically because we have maintained a track record of bringing files that hold up under scrutiny. A single mandate that goes badly wrong — a sanctioned counterparty that surfaces later, a fraud that unravels publicly, a concealed ownership structure discovered during a periodic review — does not cost us one relationship. It puts every relationship in the network at risk, because it changes how every institution in it evaluates the next file we bring, for years afterward.

There is a version of this discipline that looks, from the outside, like excessive conservatism, and we accept that criticism where it is fairly made. We do occasionally decline mandates that might, in fact, have been fine — a business with a genuinely unusual but ultimately legitimate structure that we were not able to fully satisfy ourselves on within the scope of an initial screening conversation. We would rather make that error in the conservative direction than the alternative, because the cost of an incorrect decline is a missed engagement, while the cost of an incorrect acceptance is a damaged institution, a damaged client, and a damaged network — an asymmetry that should inform how any serious advisory firm screens its mandates.

This is also why we do not treat a decline as necessarily final. Where the obstacle is fixable — a licensing gap that can be closed, documentation that can be assembled, a structure that can be unwound and rebuilt transparently — we say so explicitly and describe what would need to change for the conversation to reopen. A decline based on a fixable gap is different in kind from a decline based on concealment or absence, and we try to be precise with clients about which one they are hearing.

The initial conversation with a prospective client is, deliberately, more of an assessment than a sales process, and we structure it that way because the alternative — accepting scoping fees for mandates we already suspect cannot succeed — is exactly the kind of misrepresentation this document describes declining elsewhere in a client relationship. We ask direct questions about ownership, about the actual source of funds and wealth, about licensing status, about prior banking history including any closures or declines, and about the specific mechanics of how the business generates revenue, and we ask them early rather than after a scoping fee has been paid.

We expect, and generally get, direct answers, because founders who intend to work with us honestly generally recognise that the questions are the same ones a receiving institution will eventually ask, and that answering them accurately with us first is materially better than being caught unprepared later in the process. Where an answer reveals one of the categories described in this document — unresolved sanctions exposure, unlicensed regulated activity, unverifiable source of funds, a nominee arrangement, fraud-shaped economics, unlicensed gambling or aggregation, non-compliant privacy flows, a misrepresented business model, or a request to withhold material facts — we say so in that same conversation, specifically and without hedging, rather than let the client proceed through a scoping engagement toward an outcome we already have reason to doubt.

Where the mandate is genuinely viable but hard — the far more common outcome of an initial screening call — we describe honestly what the work will involve, which categories of institution in our network are likely to have appetite, and what we cannot promise: no adviser can guarantee that any specific institution will approve any specific application, because every institution makes its own independent underwriting decision, and any adviser who promises otherwise is telling the client something we do not believe to be true. Engagement terms, including scope and cost, are set out and quoted on scoping once we understand the specific mandate, rather than offered as a generic package that does not reflect the actual complexity of the file.

We also tell prospective clients, directly, when we believe a plan will not work as currently structured, even where a modified version of the same plan might. A founder who wants to open an account for an activity that is legal in their home jurisdiction but that our network's institutions will not touch is better served by an honest statement of that fact in the first conversation than by an open-ended search that consumes months and produces the same result with less time available to pursue an alternative.

This document exists so that a prospective client can read, before ever speaking with us, roughly what that first conversation will cover and why. We would rather a founder self-select out of an engagement that was never going to work than discover it after paying for one, and we would rather a founder who reads this and recognises none of these issues in their own business come to that first call confident that the conversation from there will be about how to build the strongest possible file, not about whether the mandate can be taken on at all.