Processing for a licensed operator does not swap one regime for another — it stacks a gaming exposure on top of the money-transmission, financial-crime and network obligations you already carry. Every merchant you board brings its jurisdiction footprint, its licence status and its restricted-transaction risk onto your programme. Apparently keeps both layers in one obligation set.
Apparently is software, not a law firm. Nothing here is legal advice, and we do not issue reliance opinions or certify any merchant's legality.
The overlay
A single gaming payment is simultaneously a licensed money-transmission activity, a restricted- transaction question, and a network-rules question. They are supervised by different people who do not coordinate their examinations for your convenience.
Layer 1 — what you already carry
State money-transmitter licensing through NMLS, federal money services business registration, bonding, net-worth and permissible-investment conditions, an anti-money-laundering programme with monitoring and reporting, and control-person obligations that reach your cap table and your executive hires. None of this changes because the merchant is a casino.
Layer 2 — what the gaming merchant adds
Federal law directs designated payment systems and their participants to maintain policies and procedures reasonably designed to identify and block restricted transactions connected to unlawful internet gambling, and the implementing regulation contemplates commercial-customer due diligence supported by evidence of the merchant's legal status. Separately, several states treat companies providing services to licensed operators as gaming-related vendors requiring their own registration or licence.
Layer 3 — what the private rulebooks add
Card networks maintain their own registration, coding and monitoring requirements for gambling merchants, and acquirers and sponsor banks impose diligence conditions that are frequently stricter than the statutory floor. These are contractual rather than statutory, which does not make them optional — losing the sponsor is the fastest way to lose the business line.
Merchant taxonomy
What you have to establish before boarding — and what you have to keep establishing afterwards — changes sharply by merchant category. These are the distinctions that decide whether a merchant is a licensing question, a legal-analysis question, or a question your sponsor bank will not let you answer at all.
Licensed sportsbook and iGaming
State-regulated operators and their platform providersA current licence in each state where play is accepted, the operator's jurisdiction footprint, geolocation and age-verification controls, and confirmation that settlement flows match the licensed entity rather than an affiliate.
Footprint drift — the operator launches a new state, or lets a licence lapse, and the file that justified boarding no longer describes what is being processed.
Tribal gaming operations
Operations conducted under IGRA on Indian landsTribal licensing and compact status, the identity of the licensing tribal gaming commission, and whether the activity and its payment flows sit inside the compacted scope.
Applying a state-licensing template to a regime that is not state-licensed, and missing tribal vendor-licensing requirements that attach to you as the service provider.
Daily fantasy and skill contests
DFS operators, skill-wagering platformsWhich states license or expressly permit the activity, which prohibit it, and whether the merchant blocks the states where it cannot lawfully operate.
Inconsistent state treatment. This is a per-state legal analysis rather than a licence lookup, and processors frequently inherit a merchant's optimistic reading of it.
Sweepstakes and dual-currency casino
Promotional-model social casino and sweepstakes playThe promotional structure itself: consideration and chance analysis, a genuine free method of entry, official rules, prize handling, and the states where the model is registered, restricted or the subject of active enforcement attention.
Regulatory posture is moving quickly and unevenly across states. A model boarded on last year's analysis can be squarely inside this year's enforcement attention.
Prediction markets and event contracts
Markets operating under the federal derivatives regimeThat the venue and the intermediary roles sit within the Commodity Exchange Act framework, and how the merchant handles states whose gaming regulators assert their own jurisdiction over the product.
A contested perimeter. The same merchant can be a regulated derivatives venue federally and the subject of a state gaming enforcement action at the same time.
Digital-asset gaming flows
Crypto-denominated deposits, withdrawals and settlementThe digital-asset regime that applies to the flow alongside the gaming analysis, custody arrangements, transfer-rule handling, and the sanctions and jurisdiction screening applied at the wallet level.
Two overlays at once — the gaming exposure and the digital-asset exposure — with sponsor-bank appetite usually the binding constraint rather than the statute.
Offshore and unlicensed operators
Operators without US licensure accepting US playersGenerally, that you are not processing it. This is the category the restricted-transaction rules are aimed at, and misrepresented merchant identity is the usual mechanism.
Transaction laundering and merchant misrepresentation — payments routed through a boarded merchant that is not the one actually being served.
Merchant file
Whether the question comes from a state examiner, a sponsor bank, a card network or an acquirer's risk team, it is the same question in different words: show me why processing this was permissible, and show me that it still is.
Status
Not a screenshot taken at onboarding. Licence status, the states in scope, and the identity of the licensed entity behind the settlement account, maintained as facts that change.
Basis
Where a merchant relies on a legal analysis of its model rather than a licence, the file needs that analysis, its date, its scope and its author — and a view on whether it still holds.
Controls
Restricted-transaction controls, geolocation, state blocking and transaction coding have to reflect what the file says is permitted — the gap between the two is what an examination finds.
Monitoring
Volume patterns, geography, chargeback behaviour and merchant-behaviour changes reviewed on a stated cadence, with what you did about exceptions recorded.
Your own status
Several states treat companies providing services to licensed operators as gaming-related vendors with their own registration or licensing duty — an obligation on you, not on your merchant.
Production
When an examiner, a network or a sponsor bank asks, the answer is a package that already exists — with the version of each fact as it stood at the time the decision was made.
Sequence
Classify
Licensed operator, tribal operation, DFS, sweepstakes model, event-contract venue or digital-asset flow. The category decides whether the next step is a licence verification or a legal analysis of the model.
Verify
A merchant is rarely lawful everywhere and unlawful everywhere. The unit of analysis is the state, and the file records which states are in scope and on what basis.
Overlay
The composition of your book determines whether you need gaming-vendor registration in a given state, what your restricted-transaction procedures must cover, and which network registrations attach.
Board
Coding, blocking, monitoring thresholds and escalation paths are configured to match the analysis at boarding, so the controls and the justification are consistent from day one.
Maintain
New states, lapsed licences, model changes, enforcement developments and amended rules all invalidate part of an onboarding file. Those are surfaced against the file rather than discovered in an exam.
Produce
State examiners, sponsor banks, acquirers and networks ask overlapping versions of the same question. One maintained file answers all of them without a reconstruction project.
AApparentlyTomorrow
A regulatory obligation is a cost with a deadline and a consequence attached. Today it sits entirely on the company that holds it. Apparently is the layer that determines and maintains those obligations. Tomorrow — The American Risk Exchange — is the layer being built to turn a maintained obligation into a defined, priced position that an institutional counterparty can take on.
Which obligations attach to this business, in which jurisdictions, under which authority — and what each one requires next. Kept current as the underlying rules move.
A maintained obligation can be described in the terms a risk desk needs: what it costs to satisfy, when it falls due, how exposed it is to a rule change, and what happens if it is missed.
Once an obligation is defined that precisely, it stops being an open-ended liability and becomes a position — one an institutional counterparty can price and hold, continuously rather than per policy term.
Tomorrow is a separate company building The American Risk Exchange. Nothing on this page is an offer, solicitation, or recommendation to enter into any transaction, and no product described here is offered to retail participants. Availability of any risk-transfer arrangement depends on its regulatory treatment and on counterparty eligibility. Apparently, Inc. is a software platform, not a law firm, an insurer, or a registered exchange, and describing a regulatory regime here is not a claim of registration with, endorsement by, or approval from any agency.
Questions
No. Apparently, Inc. is a software platform, not a law firm, and it does not issue reliance legal opinions or certify that any merchant or transaction is lawful. What it does is maintain the obligation set and the merchant file — what has been established, on what basis, when it was last verified, and what has changed since.
Financial-crime monitoring and restricted-transaction controls answer different questions. One asks whether this transaction looks like laundering; the other asks whether this transaction was permissible to process at all, in that state, for that merchant, on that date. Programmes built only for the first frequently cannot evidence the second.
In several states, yes. Companies providing services to licensed operators can fall within gaming-related vendor or supplier registration requirements, with their own disclosure and key-person obligations. Whether it attaches depends on the state, the service and the contractual relationship — and it is an obligation on the processor, not on the merchant.
As a promotional-structure question rather than a licensing one, and as a moving target. What matters is the structure itself — consideration, chance, free entry, prize handling — plus the current enforcement posture in each state, which has been changing faster than most onboarding files are refreshed.
We would not promise that; the bank sets its own conditions. What a maintained file changes is the cost of answering them, because diligence requests are answered from a record that already exists rather than assembled per request.
Load your own licences and your merchant book once. Apparently maintains both layers — what you owe as a licensed processor, and what each gaming merchant adds on top of it.
Apparently, Inc. is a software platform and is not a law firm, a bank, a money transmitter or a card network, and it is not licensed, registered, endorsed or approved by FinCEN, the Federal Reserve, any state financial or gaming regulator, or any payment network. It does not issue reliance legal opinions and does not certify the legality of any merchant or transaction. Descriptions of these regimes are general information, not legal advice.
