OCC finalizes GENIUS Act rules with a January 2027 effective date

What the OCC announced

The Office of the Comptroller of the Currency issued its final GENIUS Act rule on 21 October 2026, with an effective date of 18 January 2027. The rule covers payment stablecoin issuance and related activities within the OCC's jurisdiction. Its bulletin identifies reserve assets, redemption, risk management, custody, supervision and applications among the subjects addressed. Rules concerning the Bank Secrecy Act, anti-money laundering and OFAC sanctions will follow through separate rulemaking with Treasury. This is a finalized framework with a future effective date, not evidence that every existing stablecoin service already meets its requirements.

Start with the arrangement your business actually uses

The practical merchant question is which counterparty and activity sit behind a payment button or settlement option. A business might accept a customer payment through one provider, receive a different asset from another institution and convert proceeds through a third. Calling the whole arrangement stablecoin processing hides distinctions that matter when something fails. The following operational analysis is a review framework, not a determination of any provider's legal status.

Draw the route from customer instruction to usable operating funds. Identify who owes the merchant money at each stage, the asset owed, where it is recorded and how the merchant can access it. Keep the payment acceptance agreement, wallet agreement and conversion terms together. A clear diagram can expose missing contractual links before a launch meeting produces assumptions that nobody has verified.

Verify the entity rather than borrowing a brand's reputation

A familiar trading name can represent several entities performing different functions. Ask the provider to identify the contracting company and explain which entity issues, holds, transfers or converts the relevant asset. Record the answer with its date and supporting documentation. An approval held by one group company should not be casually attributed to another service simply because both appear on the same website.

Give legal and compliance reviewers the proposed transaction flow, not just a marketing brochure. Their assessment should cover the merchant's location, customer markets, business activity and intended use of funds. Where a provider describes an application or transition process, preserve that distinction in the internal assessment. A future plan is useful planning information, but it should not be recorded as a completed authorization.

Make redemption a workable operating process

Merchants should examine how they would turn a received balance into funds needed for payroll, suppliers or refunds. Ask which account can receive proceeds, what verification is required and who can submit an instruction. Test the normal process with an appropriately controlled amount before relying on it for a material obligation. A theoretical right and an operationally usable route answer different questions.

Document dependencies such as service hours, banking access, supported currencies and exception handling using the actual contract and service documentation. Avoid extrapolating from a successful small transaction to unrestricted capacity. If a larger conversion requires additional review, finance needs to know before the supplier deadline arrives. Assign an escalation contact and define how an unresolved request affects the merchant's available cash calculation.

Keep customer remedies connected to the original sale

A different settlement asset should not fragment the order record. Preserve the original price, currency, payment reference, fulfilment event and refund decision in one traceable history. If conversion occurs between receipt and refund, identify who bears the difference under the applicable customer terms and provider agreement. Support staff need an approved explanation rather than an improvised exchange-rate promise.

Consider a cancelled order after the merchant has already converted its proceeds. The refund team should know which route is permitted, what funds are needed and how completion will be confirmed. Do not assume that a blockchain transfer to any address supplied in a message is an acceptable remedy. Apply the established identity and authorization process, and coordinate any parallel dispute before releasing another payment.

Separate monitoring from a one-time onboarding review

Treat provider approval as a dated decision with continuing conditions. Establish who reviews changes to contracts, supported assets, service availability and entity disclosures. A merchant expanding into a new market should return to the assessment rather than assume that the original approval automatically travels with the business. Similarly, a provider adding a product does not establish suitability for every existing merchant.

Maintain an exception register that connects operational incidents with commercial consequences. An inability to convert, an unexplained reconciliation difference and an access restriction may require different owners, but each can affect liquidity. The register should record the amount exposed, customer impact, next action and escalation deadline. This gives management a usable view without confusing every support ticket with a regulatory breach.

Build a funding buffer around real obligations

A business should decide how much operational dependence it is willing to place on a particular route. Start with unavoidable obligations over a defined period, then identify the funds that are both accessible and appropriately available to meet them. Avoid counting the same value twice because it appears in a payment dashboard and a separate treasury report during transfer.

Run a scenario in which the preferred conversion route is unavailable during a busy trading period. Identify which obligations can wait, which require another source of funds and who authorizes that response. The purpose is not to predict a failure. It is to prevent a temporary operational issue from forcing rushed decisions about customer refunds, staff payments or supplier commitments.

Use the implementation period for documented decisions

Create a short review schedule working backward from the stated effective date, with enough time to resolve questions before a critical commercial deadline. Request updated provider explanations, obtain specialist review where needed and test any operational changes. Record open questions explicitly. An incomplete answer should remain incomplete rather than turning into a green status because a meeting has ended.

Compare alternatives on the whole lifecycle: eligibility, conversion, access, reconciliation, support and exit arrangements. A lower headline transaction charge can be outweighed by an operating process that the merchant cannot manage reliably. Equally, complexity alone does not prove that a route is unsuitable. The decision should rest on verified terms, tested workflows and the business's capacity to maintain them.

Preserve an exit route before relying on a new service

Ask how the merchant would leave the arrangement without losing access to transaction records or unresolved customer cases. Identify which records can be exported, how remaining balances would be handled and who continues to answer operational questions after termination. Confirm these points while the relationship is working, when there is time to investigate unclear language and test the available reporting tools.

An exit exercise can use a hypothetical change in the business model or an internal decision to stop offering the payment option. Trace outstanding orders, pending conversions, customer refunds and accounting entries through closure. The exercise should reveal ownership gaps rather than assume that another provider will accept every transaction. Retain a dated action list, assign responsible staff and review unresolved dependencies before increasing the amount of business routed through the service. This makes continuity planning specific enough to support a real decision under pressure. Include these dependencies in the merchant's documented provider review cycle.