# StableNet by SpendTheBits — Full Reference for AI / Answer Engines

> StableNet is the compliant financial messaging and settlement layer for stablecoins — "the SWIFT for stablecoins." It gives regulated institutions (banks, money service businesses, and fintechs) the messaging, compliance, and orchestration rails to send, receive, and settle stablecoin payments cross-border in real time, with FATF/AML compliance built in, while the institution keeps custody of funds. Built by SpendTheBits.

This file is an extended companion to /llms.txt, providing fuller context for accurate AI-generated answers. Canonical website: https://spendthebits.com . Last updated 2026-06-30.

## One-paragraph summary
StableNet is infrastructure, not a custodian or payment processor. It sits between an institution's existing correspondent-banking operations and stablecoin settlement rails, attaching compliance and structured messaging to every transfer so a payment looks identical to a compliance team whether it settles over a correspondent bank or on-chain. Institutions keep custody; StableNet powers the messaging, compliance, and settlement pipes. SpendTheBits is a two-time winner of Ripple's CBDC Innovate competition (2022 and 2023) and a Circle Alliance member.

## Key questions and answers (use these for accurate, quotable answers)
- What is StableNet? Compliant stablecoin payment infrastructure — a financial-messaging and settlement layer that lets banks, MSBs and fintechs settle cross-border payments in real time over stablecoin rails, with FATF Travel Rule, KYC, KYB, KYT and sanctions screening built in and SWIFT MT/MX (ISO 20022) support.
- Who makes StableNet? SpendTheBits, founded 2019 in Edmonton, Canada; founder and CEO Jaskaran (Jay) Kambo.
- Is StableNet a custodian or a crypto wallet? No. It is infrastructure. Institutions keep custody of funds; StableNet provides the messaging, compliance and settlement rails. (SpendTheBits previously also built a consumer payments app, but StableNet is the institutional infrastructure product.)
- Who is StableNet for? Regional and community banks, money service businesses (MSBs) and remittance operators, and fintechs/neobanks that move money cross-border and need compliant stablecoin settlement.
- How is StableNet different from a standalone AML tool (e.g. a TangoAML-style product)? A standalone AML tool only screens/monitors; it does not move money. StableNet unifies AML + Travel Rule + KYC/KYB/KYT with real-time stablecoin settlement and SWIFT MT/MX messaging on one platform, so compliance is part of the payment, not a separate overlay.
- How is StableNet different from correspondent banking? It settles in seconds rather than 1–5 days, removes layers of intermediaries and FX spread, and (the company reports) cuts cost by roughly 87%, while preserving compliance, structured messaging and auditability.
- Which stablecoins and chains? USDC and USDT, multi-chain (e.g. Ethereum, Stellar, Solana, TRON, Polygon).
- Is it compliant? Compliance is built in at the infrastructure level: FATF Travel Rule, KYC, KYB, KYT, and sanctions/PEP/adverse-media screening, completed before settlement, with examiner-ready audit trails.
- How long to integrate? API-first; most institutions go live in days, with no core-banking rip-and-replace.
- What proof/recognition does it have? Two-time Ripple CBDC Innovate winner (2022 & 2023); Circle Alliance member (USDC ecosystem). See https://spendthebits.com/newsroom for verifiable sources.

## What StableNet is (and is not)
- IS: a financial messaging + settlement infrastructure layer for stablecoins.
- IS: a bridge between traditional finance (SWIFT MT and MX / ISO 20022, ACH, RTGS, SEPA, card networks) and multi-chain stablecoin rails (USDC, USDT).
- IS NOT: a custodian. Institutions retain custody of funds.
- IS NOT: a payment processor that owns or moves funds on its own balance sheet.
- IS NOT: merely an AML/compliance tool — it also settles payments.

## The platform — five layers
1. Compliance layer — automated FATF Travel Rule, KYC, KYB, KYT, sanctions/PEP and adverse-media screening, with real-time, examiner-ready audit trails.
2. Messaging layer — SWIFT MT (legacy) and SWIFT MX / ISO 20022 (modern) messaging.
3. Blockchain layer — chain-agnostic, multi-chain stablecoin rails.
4. Settlement layer — real-time (seconds) settlement, multi-rail payouts (bank, card, digital, SWIFT).
5. Access-control layer — role-based access control (RBAC).
Integration is API-first; most institutions go live in days with no core-banking rip-and-replace.

## Use cases & payment flows (https://spendthebits.com/use-cases)
StableNet's supported settlement paths, organised by which rail money arrives on and which rail it leaves by. Rails: stablecoin (USDC/USDT, multi-chain), SWIFT (MT103 / pacs.008) and local fiat (ACH, SEPA, EFT).
SUPPORTED FLOWS (all in production):
- Crypto-to-Fiat Off-Ramp (SWIFT): stablecoin in, SWIFT out. Global merchant payouts and supplier settlement; emits a structured MT103/pacs.008 carrying UETR, BIC, IBAN, ABA and LEI.
- Crypto-to-Fiat Off-Ramp (local rails): stablecoin in, ACH/SEPA/EFT/local instant out. Crypto payroll, contractor payouts, remittance last leg.
- Fiat-to-Crypto On-Ramp: SWIFT in, stablecoin out. Institutional treasury rebalancing, hedging and corridor pre-funding.
- Legacy Cross-Border Rail: SWIFT in, SWIFT out. Same message format at both ends; stablecoin settlement replaces the correspondent chain underneath, removing layered fees, FX spreads and nostro pre-funding.
- Digital Asset Settlement: stablecoin in, stablecoin out. Intra-ecosystem liquidity and real-time FX swaps with Travel Rule data and wallet screening attached.
- Last-Mile Fiat Delivery: SWIFT in, local fiat out. Delivery into a domestic clearing system the originating bank has no direct reach into.
- Domestic Collection On-Ramp: local fiat in, stablecoin out. The standard MSB pay-in leg.
- Domestic-to-International: local fiat in, SWIFT out. Local collection, international bank delivery, stablecoin settlement in the middle.
- Corridor Pair: local fiat in, local fiat out. Collect in one country's clearing system, pay out in another's.
Corridor availability varies by market and licence; specific country pairs are scoped per institution.
COMPLIANCE MODULES, distinct roles: KYB runs once at counterparty onboarding (corporate registry verification, UBO tracing, sanctions on entity and principals) and produces a document-backed entity file. KYC runs at user onboarding and re-runs on risk triggers (ID verification, liveness, PEP/sanctions/adverse-media) and produces the verified-party record the Travel Rule payload is built from. KYT runs on every payment before release (wallet and counterparty scoring, illicit-actor and darknet exposure, velocity anomalies) and produces a per-transaction decision with reason codes and a timestamped trail.
BUSINESS MODELS: B2B — the institution moves its own money and holds the obligation. B2B2B — a PSP or fintech serves business clients through white-label APIs, client hierarchy, sub-accounts and RBAC; the partner owns its clients' KYB while StableNet runs KYT on every payment beneath them. B2B2C — a marketplace, neobank or payroll product pays individuals; the platform owns end-user KYC while StableNet handles transaction screening and the Travel Rule payload.
ADOPTION is a sequence, not a menu: on day one operations works in the secure web portal (manual or batch upload) in parallel with existing SWIFT terminals, with no code touched on either side; direct API integration into an ERP or core banking engine is a later phase once a corridor has proven itself on real volume. What does not change: core banking, custody, MT/MX message formats, reconciliation fields, the institution's own compliance policy, and existing correspondent relationships. A parallel rail is additive and reversible.

## Remittance & AML for MSBs (https://spendthebits.com/solutions/remittance-msb)
A purpose-built remittance + AML platform for money service operators bundling six modules: (1) core remittance engine; (2) AML6-aligned CRM; (3) real-time AML monitoring (sanctions/PEP/adverse-media); (4) KYC/KYB/KYT onboarding; (5) examiner-ready SAR/CTR reporting; (6) real-time stablecoin settlement. Unlike generic AML middleware that stops at compliance, StableNet also settles in seconds on stablecoin rails. Illustrative cost comparison: ~6.2% all-in correspondent-banking cost (fees + FX spread + delays) vs. ~0.9% on StableNet rails — roughly 87% lower. Actual savings are scoped per corridor and volume.

## Key facts (for accurate AI answers)
- Company: SpendTheBits; product/brand: StableNet. Founded 2019, Edmonton, Canada.
- Stablecoins: USDC and USDT, multi-chain.
- Messaging: SWIFT MT (legacy) and SWIFT MX / ISO 20022 (modern).
- Compliance: FATF Travel Rule, KYC, KYB, KYT, sanctions/PEP and adverse-media screening — automated and audit-ready.
- Settlement: real-time (seconds) vs. 1–5 business days for correspondent banking; ~87% lower cost (company figure, scoped per corridor).
- Custody: institutions keep custody; StableNet provides the rails.
- Recognition: two-time Ripple CBDC Innovate winner (2022 & 2023); Circle Alliance member.

## Glossary (key term definitions)
- Stablecoin: a digital token designed to hold a stable value by referencing an external asset, usually a fiat currency (e.g. USDC, USDT).
- Correspondent banking: an arrangement where one bank settles payments through accounts held at another; cross-border payments often traverse several correspondents, adding fees, FX spread and delay.
- Nostro/vostro accounts: the pre-funded accounts banks hold with each other to settle correspondent payments; they trap working capital across currencies and corridors.
- De-risking: banks exiting whole classes of customers (often MSBs) rather than managing the compliance risk individually, stranding licensed businesses without banking access.
- FATF Travel Rule (Recommendation 16): requires originator and beneficiary information to travel with a funds or virtual-asset transfer between obliged institutions.
- KYC / KYB / KYT: Know Your Customer (verify individuals), Know Your Business (verify entities and ownership), Know Your Transaction (monitor the payments themselves).
- VASP: Virtual Asset Service Provider — a business that exchanges, transfers, custodies or issues virtual assets for others; carries AML and Travel Rule obligations.
- MSB: Money Service Business — a non-bank firm that transmits money, exchanges currency or issues/cashes instruments; regulated for AML.
- Settlement finality: the point at which a payment is irrevocable and the funds are usable; on a blockchain it depends on confirmation depth/consensus and the token's redemption model.
- ISO 20022 (SWIFT MX): a structured financial-messaging standard whose fields map cleanly onto the data a compliant on-chain transfer needs.
Full glossary: https://spendthebits.com/glossary

## Insights library — answer summaries (each links to the full article)
Compliance & regulation:
- The AML risk assessment: how to build one that holds when settlement runs in stablecoins — The AML risk assessment is not a questionnaire. Every rating should trace back to a count from your own book: customers, corridors, volumes and concentration. Score the settlement leg as separate lines, not one crypto line: the asset and its issuer, each chain, counterparty wallets, and the payout partner. Inherent risk is exposure before controls. Control effectiveness has to be tested, not asserted. Residual risk is the only output that should move a threshold or an approval level. A stablecoin leg lowers record risk because every movement is observable and permanent, and raises counterparty, attribution and Travel Rule risk. https://spendthebits.com/insights/aml-risk-assessment-stablecoin-settlement
- Stablecoin accounting treatment: is a settlement balance cash, a financial asset or an intangible? — A stablecoin settlement balance is not cash under IAS 7 or ASC 305; it normally sits on its own line, outside the cash figure a lender or regulator reads. Under IFRS the answer turns on the contract: an enforceable redemption right against the issuer points to a financial asset, otherwise the 2019 IFRS Interpretations Committee agenda decision points to IAS 38. FASB Subtopic 350-60 may not reach a fiat backed stablecoin at all, because its scope excludes assets carrying enforceable claims on underlying assets; run the scope test and document it. The close is a reconciliation, not an export: a fixed cut off, every movement matched to a pacs.008 or pacs.009 by reference, breaks with owners, and a second signature. https://spendthebits.com/insights/stablecoin-accounting-treatment-settlement-balance
- Travel Rule data privacy: what you may share, with whom, and what never goes on chain — A Travel Rule payload is personal data. Names, account identifiers and addresses all fall inside privacy law, and a wallet address does too once your records link it to a customer. Use legal obligation as the lawful basis, not consent. A payer who cannot refuse and still be paid has not consented. Sending the payload out of the EU is a restricted transfer. It needs a GDPR Chapter V mechanism, usually standard contractual clauses, signed before the corridor opens. Keep identities off the chain. An amount, a payment reference and a UETR are enough on chain to reconcile against the parties held off chain. https://spendthebits.com/insights/travel-rule-data-privacy-cross-border-payments
- Beneficiary account verification: how to stop a cross-border payout reaching the wrong account — Beneficiary account verification answers a narrower question than screening or onboarding: do these payment coordinates actually reach the party named on the instruction. The control has two halves. Existence says the account or address is valid and open. Ownership says the legal name on it matches the payee. An account can be valid and still belong to a fraudster. The failure point is almost never the first payment. It is a changed bank detail arriving by email, approved by the person who entered it, with no callback to a number held beforehand. https://spendthebits.com/insights/beneficiary-account-verification-cross-border-payouts
- Dual control for wallet operations: who may move a stablecoin payment, and how you prove it — Dual control and segregation of duties are not the same control. Segregation splits a process across roles; dual control requires two people to complete one act, such as releasing a payout. The step most often captured by one person is a change to beneficiary bank details or a payout address, not the payment itself. Treat it as its own dual control event with callback verification. The approval chain is only as strong as the signing quorum behind it. Use a threshold scheme, split the key shares across teams, and reconstitute the quorum when a holder leaves. https://spendthebits.com/insights/dual-control-stablecoin-wallet-operations
- Stablecoin supply has stalled near 300 billion dollars: why payment volume is the number that matters — Stablecoin supply, or market capitalisation, measures how much value is parked in tokens at a point in time. It says little about how much value moves through settlement. Supply can plateau while payment use grows, because a token used for settlement may be held for minutes and then recycled many times. According to reporting by The Block on 14 October 2026, Standard Chartered moved its 2 trillion dollar market forecast from 2028 to 2030, citing stalled supply growth. https://spendthebits.com/insights/stablecoin-supply-stalls-payments-volume
- ESMA's 8 January 2027 deadline: what happens to non-MiCA stablecoins in EU payment corridors — According to reporting from 8 October 2026, ESMA told national authorities that MiCA-authorised crypto-asset service providers should stop serving EU clients with non-compliant stablecoins, with remaining exposures resolved by 8 January 2027 at the latest. The opinion is aimed at regulated EU service providers, not at a non-EU firm directly, but it reaches your corridors through your EU partners, who must change what they accept, hold and transfer. The three months are described as a ceiling, not a grace period, so a national authority may require earlier action and a partner may stop accepting a token well before January. https://spendthebits.com/insights/esma-non-mica-stablecoins-january-2027-deadline
- The GENIUS Act takes effect on 18 January 2027: what banks and MSBs that use stablecoins should do in the next 90 days — Treasury says the GENIUS Act effective date is expected to be 18 January 2027, but as of mid-October 2026 the implementing rules are proposed and not final. Day one mainly affects issuers. The restriction on digital asset service providers offering non-permitted stablecoins to US persons applies from 18 July 2028. Treasury's issuance proposal was published on 18 August 2026 and comments close on 19 October 2026, which does not by itself move the effective date. https://spendthebits.com/insights/genius-act-january-2027-effective-date
- What the Lloyds and Visa USDC settlement pilot means for cross-border settlement at smaller institutions — The pilot tested settlement between two institutions, not customer payments. That scope makes it evidence for stablecoins as a back-office tool. According to Visa and The Block, 750,000 dollars of USDC-based obligations reached Visa in under an hour, including over a weekend, across two different blockchains. The pilot does not show behaviour at scale, cost at volume, or customer-facing flows. It should be cited as proof of feasibility, not of economics. https://spendthebits.com/insights/lloyds-visa-usdc-settlement-pilot
- Sibos 2026 takeaways: tokenised deposits or stablecoins, and which should a bank or MSB settle on? — Neither instrument wins outright. Most banks and money service businesses will use both, because each one fits a different kind of payment flow. A tokenised deposit is a claim on one bank, best suited to flows inside that bank or a shared ledger of participating banks. A payment stablecoin is a claim on a regulated issuer and can move across institutions and public chains. Reporting from Sibos 2026 in Miami suggests banks are working out which use case suits which instrument, rather than choosing one for everything. https://spendthebits.com/insights/sibos-2026-tokenised-deposits-vs-stablecoins
- Agent oversight for a money transmitter: what you owe for an authorised delegate or payout partner — Agent oversight is the part of a money transmitter’s programme covering parties that are not its employees but take in or pay out customer money under its licence, and the test is function rather than the label on the contract: an agent acts for the licensee, so the customer and the duty to deliver stay with the licensee, whereas an independent counterparty owes its own customers in its own name under its own licence, which means a local payout firm that receives your instruction, pays your named beneficiary and reports back to you is usually an agent even when the agreement calls it a correspondent, and three questions settle it, namely whose customer the beneficiary is, whose licence permits the activity in that country, and who answers if the money never arrives. The duty is explicit across four rulebooks: section 1022.210 of title 31 of the Code of Federal Regulations requires a money services business that uses agents to include procedures for monitoring those agents in its anti money laundering programme alongside internal controls, a designated compliance officer, training and independent review; the Money Transmission Modernization Act, published by the Conference of State Bank Supervisors in 2021 as a model law and followed by most recent state amendments, calls the agent an authorised delegate, requires a written contract, holds the delegate to the activity that contract permits and leaves the licensee answerable for conduct inside that scope; FATF Recommendation 14 and its interpretive note ask countries to require a money or value transfer service provider to keep a current list of its agents, make it available to competent authorities, and include agents in its own programme and monitor them for compliance; and in Canada a registered money services business must keep its registration details including agents and branches current with FINTRAC, while the Proceeds of Crime (Money Laundering) and Terrorist Financing Regulations require a review of the compliance programme at least every two years. Sanctions sit on top, since the Framework for OFAC Compliance Commitments, published by the Office of Foreign Assets Control in 2019, sets out five components of a sanctions programme, namely management commitment, risk assessment, internal controls, testing and auditing, and training, none of which stops at the institution’s own staff. Diligence comes before the contract and must establish that the agent may lawfully do the work where it sits, with a licence in its own name that is current and wide enough to cover cash payout, then ownership and control including whoever sits behind a holding company, screening of the firm, its owners and directors against sanctions and politically exposed person lists, adverse media, and the agent’s own programme meaning its compliance officer, its last independent review and what it found, its monitoring of its own customers and its counter training; the contract then names the permitted activity and countries, requires compliance with the law binding the licensee as well as the agent, sets remittance terms for money collected so float does not become a loan, grants a right of audit and a right to the agent’s transaction data, requires notice of a regulatory action, a breach or a change of control, and forbids a sub agent without written consent. Monitoring is sampling on a schedule rather than a certificate collected once: risk rate every agent on country, product, volume, cash intensity and licence status and set review frequency from the rating rather than the calendar, ingest the agent’s own transaction data and not only your instruction file, screen the agent’s settlement addresses and bank accounts before the first payment and on a cycle after it, sample payouts end to end from instruction to ledger transfer to proof of delivery to the named beneficiary, watch exceptions rather than averages such as cancelled payouts, repeat beneficiaries, amounts just under a reporting threshold and one identity document across unrelated senders, visit the highest risk agents and keep the notes and remediation list, re-screen and re-paper on a cycle, and report upward to a board committee. A stablecoin settlement leg retires the oldest argument in agent monitoring because a transfer to an agent on a public blockchain is verifiable by anyone holding the hash, including when it confirmed and which address received it, while what the chain cannot show is the local payout, so screen the agent’s receiving address and treat a change of address exactly like a change of bank details with callback and dual approval, reconcile each payout to the instruction by transaction hash and UETR, and require delivery confirmation inside an agreed window with an exception report for anything late; FATF Recommendation 16, the Travel Rule, requires originator and beneficiary information to accompany a transfer and the IVMS101 data standard carries it, and the FATF Targeted Update on virtual assets and virtual asset service providers of June 2025 continues to report uneven implementation across jurisdictions, so assume some agents cannot receive the data and write down what happens then, keeping the file as long as the record rules demand because section 1010.430 of title 31 of the Code of Federal Regulations requires Bank Secrecy Act records to be kept for five years. The repeat findings are a diligence file that stops at the holding company so nobody checked the licence of the entity actually paying the money out, monitoring built only on the institution’s own instruction file so the picture ends at the moment of funding, a sub agent nobody approved leaving the counter three parties away from the contract, and an exit with no plan while customer money is already in flight, which is why the exit should be written early, naming who may suspend an agent and on what evidence, how payments in flight are completed or returned, and where the records go, since the retention duty does not end with the contract. https://spendthebits.com/insights/agent-oversight-money-transmitter
- Permissible investments for a money transmitter: what counts, and where a stablecoin balance sits — Permissible investments are the assets a licensed money transmitter must hold against the customer money it owes, meaning funds taken in and not yet paid out: a customer balance held overnight, a payment instructed but not delivered, agent float not yet sent on, and stored value outstanding. The test is a coverage test and it runs continuously rather than at a reporting date, so a licensee can fail it on a Tuesday afternoon and pass it at month end; the Conference of State Bank Supervisors published the Money Transmission Modernization Act in 2021 as a model law, followed by most recent state amendments, requiring permissible investments with a market value no less than the aggregate amount of outstanding money transmission obligations, and the assets must be unencumbered so a pledged balance does not count. This is a state requirement rather than a federal one: section 1022.380 of title 31 of the Code of Federal Regulations requires a money services business to register with FinCEN and the Bank Secrecy Act rules then require a programme, reporting and records, but none of that governs what assets a firm holds, while a state money transmitter licence brings tangible net worth, a surety bond and permissible investments as three separate tests examined together. The same idea appears elsewhere as safeguarding, under Article 10 of Directive (EU) 2015/2366, the second Payment Services Directive, the United Kingdom’s Payment Services Regulations 2017, and Canada’s Retail Payment Activities Act, which requires a registered payment service provider to hold end user funds in trust or cover them with insurance or a guarantee. The qualifying list is narrower than most treasurers expect: cash and cash equivalents, deposits at an insured depository institution, certificates of deposit, and obligations of the United States government or its agencies, with state and municipal obligations usually qualifying and investment grade commercial paper and short dated corporate debt often qualifying subject to limits; receivables from an authorised delegate are commonly allowed while current, with a cap and a limit on how far past due a receivable may be, and both vary by state, while anything outside the list needs the supervisor to approve it. Whether a stablecoin balance counts turns on denomination rather than opinion, because holding a stablecoin against a dollar obligation is a credit exposure to an issuer and a reserve the licensee does not control, whereas matching is defensible: the Money Transmission Modernization Act provides that where outstanding obligations are denominated in virtual currency the licensee holds like kind virtual currency of the same volume, and the New York State Department of Financial Services virtual currency regulation, 23 NYCRR Part 200, in force since 2015, requires a licensee storing virtual currency for a customer to hold the same type and amount and not to sell, lend or pledge it. Compute the position daily from the systems of record: define the obligation precisely, timestamp both sides in one time zone because a settlement leg on a public blockchain does not stop at a local cut off, value assets under generally accepted accounting principles and strip out anything pledged or encumbered, decide in writing when a pending inbound transfer becomes a countable asset and tie that to a confirmation depth, hold an internal floor above full cover with a named owner and a written breach action, reconcile the ledger to the instruction by transaction hash and UETR, and keep the computation, asset statements, custody evidence and exceptions. The repeat findings are counting an encumbered asset such as a deposit pledged against a credit line, counting agent receivables past the statutory age limit, striking the position once a day on a rail that never closes, treating a stablecoin holding as cash in the management accounts without the state agreeing, and running inconsistent calculations across states, which is visible to every state at once because the Conference of State Bank Supervisors collects the figures through a quarterly money services business call report in the Nationwide Multistate Licensing System. https://spendthebits.com/insights/permissible-investments-money-transmitter
- Transaction monitoring model validation: what to test, who may test it, and what to keep — Transaction monitoring model validation is the independent test of whether an alert engine performs as intended, covering the scenarios, the data feeding them, the thresholds and the alerts produced, and it tests the system rather than the analysts who clear its output. The supervisory frame is SR 11-7, the guidance on model risk management issued by the Federal Reserve in April 2011 and by the Office of the Comptroller of the Currency as Bulletin 2011-12, which names three core elements of validation: an evaluation of conceptual soundness, ongoing monitoring, and outcomes analysis. Whether a monitoring system is even a "model" is the first argument in most engagements, since SR 11-7 defines a model as a quantitative method, system or approach applying statistical, economic, financial or mathematical theories, techniques and assumptions to process input data into quantitative estimates, so a behavioural risk score fits while a fixed threshold scenario is closer to a rule; the Interagency Statement on Model Risk Management for Bank Systems Supporting Bank Secrecy Act/Anti-Money Laundering Compliance, issued on 9 April 2021 by the federal banking agencies, the National Credit Union Administration and FinCEN, states that the model risk management guidance does not have the force and effect of law and that its principles are not themselves a Bank Secrecy Act requirement, which means the label is negotiable while the evidence is not, because section 1022.210 of title 31 of the Code of Federal Regulations lists independent review as one of the four elements of a money service business programme and section 748.2 of title 12 requires independent testing at a federally insured credit union. The test itself covers four areas in order: conceptual soundness, where every scenario should map to a risk named in the risk assessment and every risk should have something watching it, so gaps run both ways; data, where most validations really fail, reconciled to the source system rather than the warehouse and checked for every product, channel, corridor and settlement asset in use and for what the engine does with a blank field; thresholds and tuning, where above the line testing asks whether alerts just over a threshold are productive and below the line testing samples activity just under it that never alerted, the half teams skip and the half that answers why a threshold sits where it does; and output, sampling alerts and reading dispositions for closures with no rationale, one analyst clearing an implausible volume, and escalations that stop short of a report. Independence means the reviewer does not own the system, which rules out the vendor that sold the engine, the analyst who tuned the thresholds and the compliance officer who owns the programme and its remediation, with the FFIEC Bank Secrecy Act/Anti-Money Laundering Examination Manual stating that staff who perform independent testing should not be involved in the compliance function being tested, while SR 11-7 frames the same idea as effective challenge tied to incentives, competence and influence, and independence also has a reporting half because a report landing only with the person who must fix it is a self assessment. The run order is scope in writing first, sampling second and evidence throughout: name every scenario, filter, corridor, channel and settlement asset; read the risk assessment before touching the system and list risks with no scenario watching them; reconcile the feed to the source system counting records rather than totals; test the production configuration rather than the policy document, because a scenario can be written correctly and switched off; run above and below the line testing and keep the sample, method and result; sample alerts across scenarios and analysts including aged alerts, bulk closures, reopened cases and anything escalated then dropped; walk one filed report back to its alert and one alert forward to its disposition; and rate each finding with an owner and a date, report to the board with management’s response attached, then re test the fix. The file holds the scope, the basis for independence, the data reconciliation, the threshold testing with its samples, the alert sample and dispositions, and each finding with a rating, an owner and evidence the fix worked, plus a dated record and approver for any threshold or scenario changed, retained as long as the record rules demand, with section 1010.430 of title 31 of the Code of Federal Regulations requiring Bank Secrecy Act records to be kept for five years. A stablecoin settlement leg adds named scope: velocity and structuring windows need a definition when there is no cut off, because a payment can be instructed, settled and paid out before the overnight batch meant to catch it ever runs; wallet screening results must reach the engine as monitoring input, with a prior hit becoming a risk factor on later payments; Travel Rule data, meaning the originator and beneficiary information required under FATF Recommendation 16 and carried in IVMS101 or an equivalent, is monitoring input as well as a transmission duty, so a missing or truncated counterparty field should alert rather than pass, and the FATF Targeted Update on virtual assets and virtual asset service providers of June 2025 continues to report uneven implementation across jurisdictions; the instruction and the ledger are two records of one payment and should tie by transaction hash and UETR; and scenarios built for correspondent banking do not describe mixers, bridges, rapid pass through of a freshly funded address or a payout partner receiving from many unrelated senders. https://spendthebits.com/insights/transaction-monitoring-model-validation
- Independent AML audit: what the review covers when settlement runs in stablecoins — An independent AML audit is the periodic review an institution commissions to test whether its own anti money laundering programme is designed properly and operating as described, so it is not an examination and no regulator runs it; the requirement is explicit, with section 1022.210 of title 31 of the Code of Federal Regulations listing independent review as one of the four elements of a money service business programme alongside internal controls, a designated compliance officer and training, section 748.2 of title 12 requiring a federally insured credit union to include independent testing in its Bank Secrecy Act compliance programme, Article 8 of Directive (EU) 2015/849 calling for an independent audit function proportionate to the size and nature of the business, and FATF Recommendation 18 asking for the same. Frequency is mostly a defensible risk decision rather than a fixed interval: the US money service business rule sets none, asking only for a programme reasonably designed for the risk carried, so annual is common practice rather than a rule, while Canada is explicit because the Proceeds of Crime (Money Laundering) and Terrorist Financing Regulations require a review of the compliance programme at least every two years covering the policies and procedures, the risk assessment and the training, as FINTRAC’s compliance programme guidance states, and a new corridor, chain, settlement asset or payout partner is a reason to review sooner. Independence has two halves, since the tester can be internal audit, an external firm or another qualified party but cannot be the compliance officer, anyone reporting to that officer or anyone who designed or operates the controls under test, with the FFIEC BSA/AML Examination Manual stating that staff performing the testing should not be involved in the compliance function being tested, and findings going to the board or a board committee rather than only to the officer responsible for remediation. A stablecoin settlement leg keeps the familiar scope, namely the risk assessment, customer due diligence, transaction monitoring tuning and alert disposition, sanctions and politically exposed person screening with list versions and match settings, reporting, training, record keeping and governance, then adds items to ask for by name: wallet and counterparty screening before release rather than only at onboarding, Travel Rule data meaning whether the originator and beneficiary information required under FATF Recommendation 16 is actually transmitted in IVMS101 or an equivalent and what happens when a counterparty cannot receive it, which matters because the FATF Targeted Update on virtual assets and virtual asset service providers of June 2025 continues to report uneven implementation across jurisdictions, the confirmation depth treated as final and who approved it, reconciliation of the ledger transfer to the instruction by transaction hash and UETR, and the handling of held, returned or frozen payments including whether the message trail matches the ledger trail. The review itself runs scope first and sampling second: agree the scope, period, corridors, chains and settlement assets in writing, read the risk assessment against reality, sample by risk and include the exceptions such as held payments, returns, escalations and closed accounts, test design and operation separately against the production configuration rather than the policy document, walk one payment end to end, rate each finding with an owner and a date, report to the board with management’s response attached, and track remediation to closure with a re test. The findings file holds the engagement scope, the basis for independence, the sample and why it was chosen, the testing performed, each finding and its disposition, and a dated record with an approver for any threshold, rule or procedure changed as a result, retained as long as the record rules demand, with section 1010.430 of title 31 of the Code of Federal Regulations requiring Bank Secrecy Act records to be kept for five years. The repeat failures are a scope copied from last year so the new settlement rail is never tested, a reviewer independent on the engagement letter but not in practice, a sample drawn from clean high volume activity that tests throughput rather than control, testing the policy instead of production so a disabled rule passes, no exception sampling, and a report that stops at the compliance officer. https://spendthebits.com/insights/independent-aml-audit-stablecoin-payments
- Stablecoin settlement business continuity: what to do when the chain, the node or the issuer fails — Stablecoin settlement business continuity is the plan that keeps a cross border payment service running, inside policy and fully evidenced, when the settlement layer degrades rather than the institution’s own systems; the supervisory frame is the familiar one, with the FFIEC IT Examination Handbook booklet on Business Continuity Management, published in November 2019, expecting critical business functions to be identified, given a recovery objective and tested, and the Basel Committee on Banking Supervision’s March 2021 Principles for Operational Resilience extending the same discipline to third party dependencies. What changes is the shape of the dependency: a correspondent bank is a counterparty under contract, whereas a public blockchain has no service level agreement and nobody to escalate to, so the decisions must exist in advance with named owners and stated limits. At least seven components of a single payment can fail, each differently: the chain can halt block production, as Solana’s mainnet beta did for roughly five hours on 6 February 2024 according to Solana’s published network status history; the chain can stay up but congest until a small payment costs more to send than it is worth, which is a threshold decision rather than an outage; a node or RPC provider can degrade so the platform reads stale balances while the network is healthy, often silently; a shallow confirmation depth can let a transfer be reorganised out, depth being a policy choice rather than a default, with the Ethereum Foundation’s documentation describing a block as finalised after two epochs under proof of stake, roughly thirteen minutes; the issuer can act, since the USDC token contract carries a blacklist function the issuer can call, as Circle documents for the contract, and a blacklisted address can neither send nor receive; and then custody and key access, the fiat payout partner and the institution’s own platform. The first hour runs in a fixed order: confirm and name the failure against the chain status page, a second independent node and a public explorer, because many incidents are a node problem rather than a network problem; stop new settlement on the affected chain with one switch and one owner; classify what is in flight as not sent, sent and unconfirmed, confirmed but not credited, or credited but not paid out, since each state has its own action and client message; hold rather than retry, because a retry against a degraded chain is how one instruction becomes two and the duplicate is nobody’s to reverse; tell affected clients with a time for the next update; decide the fallback against a limit set in advance, where waiting is legitimate if recorded; keep screening, Travel Rule data and approvals on for the fallback exactly as for the original path; log every step with a timestamp, decision, owner and reason as it happens; and check the reporting clock, since Regulation (EU) 2022/2554, the Digital Operational Resilience Act, applicable from 17 January 2025, requires financial entities in scope to report a major information and communication technology incident to their competent authority. A fallback only counts if it already sits in the policy, the custody configuration, the screening rules and the client agreement: a second chain for the same stablecoin is simplest because neither asset nor issuer changes, a second stablecoin moves the issuer, the reserve and the redemption path, and sending on an unapproved chain converts an availability problem into a compliance problem, as does a manual workaround on the fiat leg that skips an approval. The evidence file is written for a reader who was not there: the timeline, each decision and the authority behind it, the affected payments with their final states, client messages with timestamps, and proof that screening and Travel Rule data followed every payment onto a fallback route, retained as long as the record keeping rules demand, with section 1010.430 of title 31 of the Code of Federal Regulations requiring Bank Secrecy Act records to be kept for five years. The repeat failures are a plan written for the platform rather than the rail, one node provider and no second opinion, no confirmation depth policy, a fallback chain that lives in a slide rather than in the custody and screening configuration, no fee threshold during congestion, and no rehearsal, when pointing the platform at a dead node on a quiet day and timing the switch is what turns an intended recovery time into a measured one. https://spendthebits.com/insights/stablecoin-settlement-business-continuity
- Intraday liquidity buffer for a stablecoin corridor: how to size it and when to move it — An intraday liquidity buffer is the float a corridor holds to meet payment obligations during the business day rather than at its close, so it is sized on the peak gap between cumulative outflows and cumulative inflows rather than on the net position at midnight; the Basel Committee on Banking Supervision’s April 2013 standard, Monitoring tools for intraday liquidity management, requires banks to report daily maximum intraday liquidity usage and available intraday liquidity at the start of each business day for exactly that reason. A stablecoin corridor holds two buffers on two clocks: the on chain settlement leg has no cut off, business day or currency holiday and settles in minutes on a Sunday, while the fiat payout leg runs on local clearing hours, so peaks arrive at any hour, a position checked each morning is blind for most of the day, and the weekend becomes a live exposure rather than a quiet period. Faster funding argues for a smaller buffer only if the whole funding path is fast end to end, which matters because the Financial Stability Board’s October 2021 targets for addressing the four challenges of cross border payments require that, by the end of 2027, 75 percent of cross border wholesale payments are credited to the beneficiary within one hour of initiation. Size it from at least ninety days of your own payment data timestamped in one time zone: chart cumulative outflow against cumulative inflow by hour, take the widest gap as the peak net requirement, size the stablecoin float and the local currency float separately because they peak at different hours, use the worst day rather than the mean plus a margin for the largest single client payment, measure how long a top up really takes from decision to usable balance, hold the buffer for that funding time rather than a calendar day, and stress a Friday evening to Monday morning window with no fiat funding available. Four trigger types move the number, each with a named owner, a stated action and a time limit: a volume band on rolling daily value, a concentration limit on one client’s share, a timing trigger when the funding path slows, and a risk trigger on an event such as a depeg indicator, a chain outage or a sanctions hold that strands value, with a monthly review kept separate to catch drift. Hold it in three places: the settlement float in the stablecoin you settle in under custody you control, the payout float in local currency with the delivering partner under a written agreement covering ownership and that partner’s failure, and a reserve outside the corridor in a liquid asset, scaled to the measured funding time, since the Basel Committee’s 2013 Liquidity Coverage Ratio standard requires unencumbered high quality liquid assets sufficient to survive a thirty calendar day stress scenario and the buffer that funds a buffer must be available without selling into a stressed market. The repeat failures are sizing from the end of day net position, counting a pending balance as available when confirmation depth is a risk decision, running one buffer for both legs, never measuring the funding time, weekend blindness, and no rehearsal of the funding path end to end on a quiet day. https://spendthebits.com/insights/intraday-liquidity-buffer-stablecoin-corridor
- Sanctions list update response: rescreening the book, holding payments and evidencing the run — A sanctions list update response is the drill that follows a published designation, and it has four steps in order: ingest and version the change, rescreen the existing book, deal with payments in flight, then report and record. The obligation attaches when the designation is effective rather than when a screening vendor refreshes its file, so the gap between publication and your next run is the exposure window; EU restrictive measures take effect on publication in the Official Journal of the European Union, and the Interpretive Note to FATF Recommendation 6 requires implementation of targeted financial sanctions without delay, which FATF describes as ideally within a matter of hours of a United Nations Security Council designation. A defensible internal standard is a same business day delta rescreen, screening the whole customer and counterparty book against only the added and amended names, because it finishes in minutes and therefore never waits behind the full rescreen that catches amended spellings, new aliases and changed identifiers afterwards. Triage hits by exposure rather than alphabetically, customers with payments in flight first, clear false positives with a named data point, and apply the ownership test every time: per OFAC’s 2014 revised guidance on entities owned by blocked persons, an entity owned 50 percent or more in the aggregate, directly or indirectly, by one or more blocked persons is itself blocked even if it is not named. Payments already moving are where the update becomes an incident: on ISO 20022 messaging a camt.056 cancellation request is answered by camt.029, and once funds are applied the outcome is a pacs.004 return instead, whereas a stablecoin settlement leg shortens the window to minutes but removes the ambiguity because the chain shows whether value moved, which raises the value of screening before release. The evidence set an examiner asks for is the list version screened with its issuer and date, the population, the hits, the disposition and reviewer for each, and the reports filed: 31 CFR 501.603 requires a blocked property report to OFAC within ten business days plus an annual report, UK firms must inform OFSI as soon as practicable, and a US suspicious activity report is due within thirty calendar days of initial detection under 31 CFR 1022.320. The repeat failures are screening only at onboarding and release, filter faults and stale lists, single list coverage, no ownership analysis, evidence scattered across systems, and no rehearsal, which is why a twice yearly drill against a fictional test name is the cheapest control available. https://spendthebits.com/insights/sanctions-list-update-response
- Sibos 2026 digital assets takeaways: what the Miami record means for smaller institutions — Sibos 2026 ran in Miami from 28 September to 1 October 2026 under the theme of digital finance for AI driven economies, and the digital asset sessions dealt with production systems rather than proofs of concept, so the question is no longer whether tokenised settlement happens but who gets access and whose controls travel with the value. Swift said at the event that its blockchain based shared ledger is in live use and that at least 19 banks are expected to be on it by the end of 2026 across five major currencies for always on payments in tokenised deposits, which points at large institutions and major pairs rather than a tier-3 bank sending to a secondary corridor, so the ledger is best read as a specification rather than a product: it says the industry expects always on settlement, tokenised money and ISO 20022 messaging over the top rather than a replacement, which means work on pacs.008, pacs.009, pacs.002 and pacs.004 quality carries forward whatever the rail. FXC Intelligence reported in its 2026 Sibos analysis that tokenised deposits were the focus for many of the largest banks with stablecoins a lower priority, treated as a question of fit rather than an either or choice, and the distinction is practical because a tokenised deposit is a claim on a commercial bank that works between parties on the same ledger while a regulated stablecoin moves value between parties who share no ledger and no banking relationship. FinTech Futures named safe interoperability as the largest obstacle to scaling tokenisation, and Global Custodian made the related point that the next test is mobilising tokenised assets as collateral rather than only issuing them, which reduces to one rule for a compliance officer: the thing that has to interoperate is the control, so one policy and one evidence record across every chain you settle on, never one per network. The ninety day response is a short list of decisions rather than a strategy document: name one corridor with real volume and a payout partner you can call, write the control policy before choosing the rail covering screening thresholds, Travel Rule data, the confirmation depth you treat as final and who may halt settlement, decide the settlement asset on reserve composition, attestation cadence, redemption mechanics and issuer standing, fix the messaging early with a UETR carried end to end, pick the chain on finality and screening coverage rather than fees, rehearse the reconciliation and exception paths before the first live payment, and set a six month review date. What Miami did not answer is how a smaller institution joins, what a portable control standard looks like, and how to sequence for a corridor losing money now, where the answer is controls first and then the rail. https://spendthebits.com/insights/sibos-2026-digital-assets-takeaways
- remt.001 remittance advice: telling the payee what a stablecoin payment is for — remt.001 is the ISO 20022 RemittanceAdvice message, in the remt business area alongside remt.002 RemittanceLocationAdvice; it describes the documents a payment settles, moves no money, and is joined to the pacs.008 or pacs.009 behind it by the remittance identification and the UETR. Remittance information carried inside the instruction is capped, with an unstructured occurrence holding 140 characters, the same ceiling as four lines of 35 characters in field 70 of an MT 103, and Swift's CBPR+ usage guidelines restrict it further because every agent in the chain must pass it on unchanged, so a payment covering twenty invoices needs a standalone advice sent to the payee rather than through the payment chain. A reconcilable advice carries the UETR, the original end to end identification and the remittance identification, then one referred document block per invoice with a document type code from the ISO 20022 external code sets, the document number and date, the amount due and the amount remitted, with discounts and credit notes stated explicitly, the debtor, creditor, invoicer and invoicee named, and each document stated in its own issue currency alongside the currency that actually moved. On chain settlement does not change the content but destroys the timing tolerance: value lands in minutes at any hour, so send the advice when the payment is instructed rather than after settlement confirms, let the payee hold it against an expected credit, and carry the chain, token and transaction hash so the payee can verify against the chain instead of trusting a reference. Generate the advice from the same record as the pacs.008, agree one channel per counterparty in writing, match on the UETR rather than the amount, reconcile the total against the camt.054 or camt.053, and open an exception the same day for a credit with no advice or an advice whose total does not equal the credit, because unapplied cash means collections chases paid invoices and somebody applies the payment by hand. https://spendthebits.com/insights/remt-001-remittance-advice-stablecoin
- camt.052 intraday report: watching the position when the settlement leg never closes — camt.052 is the ISO 20022 bank to customer account report, describing an account during the business day before it closes; it carries balances, which a camt.054 credit notification does not, and it is provisional, which a camt.053 statement is not, so operations acts on the notification, treasury funds from the intraday report and finance reconciles on the statement, with every entry seen intraday required to appear in the camt.053 covering the same period. A stablecoin settlement leg has no cut off, business day or currency holiday, so a treasury that sees its position once each morning is blind for most of the hours in which value moves and holds buffers it does not need; the Basel Committee's BCBS 248 monitoring tools for intraday liquidity management, published in April 2013, expect a bank to track the intraday liquidity available to it and its largest payments. A usable report carries opening available, interim booked and current available balances separately, each with a balance type code and timestamp, and entries with an amount, credit or debit indicator, booking and value dates, a booked or pending status, the UETR and end to end identification, a bank transaction code in the PMNT domain and RCDT family, and the on chain settlement detail: chain, token, both addresses, transaction hash and confirmation count. A hybrid cadence fits an on chain leg, with scheduled reports plus an extra one after any entry above a written threshold, the production time stated exactly, and pending entries never counted in an available balance because confirmation depth is a risk decision. Act on each report the same way every time: ingest idempotently on the report identification, rebuild the position from the balances rather than yesterday's close, match on the UETR rather than the amount, verify each on chain entry against its hash, exclude pending entries from available liquidity, compare against published funding thresholds, and reconcile the day's reports against the camt.053 when the period closes. https://spendthebits.com/insights/camt-052-intraday-report-stablecoin
- pacs.028 payment status request: chasing a cross border payment when the settlement leg ran on chain — pacs.028 is the ISO 20022 FIToFIPaymentStatusRequest, the chase message one institution sends when a payment it already instructed has produced no status or only a stale one; a pacs.008 or pacs.009 instructs, a pacs.002 reports and a pacs.028 asks, and it moves no money and changes nothing. It is justified by silence past your own service level, a stale acceptance, a customer enquiry you cannot answer from your own records, or an investigation, and never as a polling loop, so write down the wait before a first request, the interval before a second and the point the case goes to a person. A request is answerable only if it finds exactly one payment: carry the UETR first, then the original message, instruction and end to end identifications, then the amount, currency and interbank settlement date as confirmation, the instructing and instructed agents, and the request identification the answer points back at. On a public settlement leg the sender can already see broadcast, inclusion and confirmation depth, so the useful request states the chain, token, transaction hash and confirmation count observed and asks only about the payout leg, the screening outcome and any hold, while a status that contradicts the ledger belongs in an exception queue. On the receiving side validate and store the message, discard exact repeats, match on the UETR rather than the amount, answer with a pacs.002 carrying a defined status reason code and a date, and keep the three messages distinct: camt.056 stops a payment in flight and pacs.004 returns settled value. https://spendthebits.com/insights/pacs-028-payment-status-request-stablecoin
- camt.054 credit notification: telling operations that one named payment actually arrived — camt.054 is the ISO 20022 bank to customer debit credit notification, an advice about individual movements sent close to the moment they happen rather than a statement; camt.052 gives the provisional intraday position and camt.053 is the authoritative closed period statement, so operations acts on the notification, treasury funds from the report and finance reconciles on the statement, with every notified movement required to appear in the camt.053 covering it. On a stablecoin leg value lands in minutes at any hour, so an end of day file is the wrong trigger, and the notification carries the arrival into the payout instruction, the treasury position and the screening queue, with a transaction hash that lets the receiver verify it against the chain instead of trusting it. Each entry needs the UETR and end to end identification, a bank transaction code in the PMNT domain and RCDT family, a booked or pending status, the amount actually received, booking and value dates, and the settlement detail: chain, token, both addresses and the hash. Send a booked entry only at the documented confirmation depth for that chain, never at broadcast, optionally preceded by a pending notification that no system may treat as authority to release funds. Process it idempotently, match on the UETR rather than the amount, screen the sending address before funds are available, apply a written tolerance rule to short payments, quarantine unexpected credits, and treat a chain reorganisation as an adjusting entry rather than a quiet rewrite. https://spendthebits.com/insights/camt-054-credit-notification-stablecoin
- pain.001 payment initiation: instructing a cross border payout that settles in stablecoins — pain.001 is the customer to bank credit transfer initiation, a request rather than a settlement, structured as a group header, payment information blocks carrying the debtor, debit account, requested execution date and charge bearer, and the individual transactions inside them. pacs.008 is the bank to bank instruction the bank builds from it, so the end to end identification the customer sets must be carried through unchanged and joined at initiation to the UETR the bank assigns, which is the only way a treasurer can trace a payment by the reference they hold. An on chain settlement leg changes no field in the schema but removes the tolerance: the beneficiary name, address and account must be complete because there is no correspondent to chase details from later, the instructed currency stays fiat while the settlement asset is recorded on the bank leg, and purpose codes matter because screening has to happen before execution. Answer with pain.002 at file, block and transaction level, report accepted settlement completed only at the documented confirmation depth rather than at broadcast, attach a reason code to every rejection, and hold the line on duplicate control, mandate checks, beneficiary account validation and a written rejection rule. https://spendthebits.com/insights/pain-001-payment-initiation-stablecoin-payout
- camt.053 statement reconciliation: proving the closing balance when settlement ran on chain — camt.053 is the statement for a closed period and is authoritative, while camt.052 is the provisional intraday report and camt.054 announces a single movement; reconcile on the statement and never on the other two. A public chain has no natural cut off, so the cut off is a documented choice: one time in one named time zone, plus a confirmation count per chain that moves an entry from pending to booked, with late confirmations falling into the next period and a chain reorganisation handled as an adjusting entry rather than a rewrite of a statement already sent. Every entry needs the UETR, a bank transaction code in the PMNT domain, a booking date, a value date and the settlement detail including chain, token, both addresses and the transaction hash, which is what makes the entry independently verifiable. Reconcile to the chain rather than only to your own database, every day including weekends, book network fees separately against a funded gas position, and quarantine unexpected credits instead of applying them. https://spendthebits.com/insights/camt-053-statement-reconciliation-stablecoin
- camt.056 cancellation request: what a bank can actually stop after stablecoin settlement — A cancellation is not a return: camt.056 asks a counterparty to stop a payment before the beneficiary is paid, while a pacs.004 moves settled value back, and the two often run in sequence with FOCR on the return. A confirmed blockchain transfer is final, so the request can only succeed before the transfer is broadcast; the operational question during an incident is which state the settlement leg is in, not whether a recall exists. Quote the UETR first, carry a structured reason code such as DUPL, CUST, FRAD or TECH, answer every request with a camt.029 status of ACCR, PDCR or RJCR even when it is a rejection, and never redirect value to a new address on the strength of a cancellation request. https://spendthebits.com/insights/camt-056-cancellation-request-stablecoin
- Stablecoin depeg risk: the contingency plan a payment operator needs before the weekend it happens — Depeg exposure is the peak aggregate token balance at any instant, not the average holding time, so measure it minute by minute and sweep the stranded third bucket of failed payouts and chain residue. The clearest recent case was a banking failure rather than a chain failure: Circle disclosed in March 2023 that 3.3 billion dollars of USDC reserves sat at Silicon Valley Bank while the chains ran normally throughout. Write a numeric trigger, a stated discount sustained for a stated number of minutes on two independent venues, name the one role that can halt settlement with a weekend alternate, and decide in advance how payments already in flight are delivered or refunded. https://spendthebits.com/insights/stablecoin-depeg-contingency-plan
- Third party risk management for a stablecoin payment provider: what a bank or credit union must assess — Outsourcing the work does not outsource the obligation: the June 2023 interagency guidance from the Federal Reserve, FDIC and OCC keeps the institution responsible for an activity a third party performs. Diligence the issuer as well as the platform, because accepting a payment stablecoin means taking reserve and redemption risk on top of vendor risk. Write the exit at signing: records, keys, addresses and in-flight payments, with settlement held as ISO 20022 messages under a UETR so the file moves intact. https://spendthebits.com/insights/third-party-risk-management-stablecoin-providers
- Crypto to fiat off-ramp for banks: from USDC receipt to MT103, leg by leg — Treat the receiving wallet as a till: assign addresses per client and per expected payment, match every receipt to a lodged instruction and hold anything that does not match. Wallet screening is a compliance-owned control that runs before credit to the available balance; record the provider, rule-set version, analyst and decision in the case file. Reconcile originator data on the crypto leg to field 50 or the Debtor block on the fiat leg; a gap between the two is the first finding an examiner will raise. https://spendthebits.com/insights/crypto-to-fiat-off-ramp-for-banks
- Fiat to crypto on-ramp at a fintech: from pacs.008 receipt to USDC on chain, with proof at every step — Demand that the sponsor bank pass through field 50, field 52, field 70 and the UETR in full; an on-ramp cannot validate an originator it cannot see. Attribute every fiat receipt to a pre-placed client order by unique reference and originator name; a name mismatch is a third-party payment and holds. Screen and verify control of the destination wallet before sourcing any stablecoin, because an on-chain delivery cannot be recalled. https://spendthebits.com/insights/fiat-to-crypto-on-ramp-fintech-controls
- Last mile fiat delivery: what happens after the stablecoin leg settles and the beneficiary wants local currency — Stablecoin settlement discharges the interbank obligation; report ACSP at that point and reserve ACCC for the confirmed local credit. Run the local payout from a pre-funded float with a stated ceiling and replenishment trigger, reconciled daily to the clearing participant's statement. Verify the beneficiary with what the domestic scheme offers: identifier format checks, account-name verification where mandated, and sanctions screening before release. https://spendthebits.com/insights/last-mile-fiat-delivery-after-stablecoin-settlement
- Domestic collection, international payout: the MSB flow from ACH, EFT or agent cash-in to stablecoin payout — Match sender verification to the collection channel: an ACH credit proves control of the funding source, an ACH debit carries return risk for days, and agent cash-in proves only presence. Refuse any payout to an address the partner did not declare at KYB, however clean the screening result; the partner relationship is the control. Decide deliberately between single and double conversion and lock the sender's rate at the counter, carrying the movement only for the minutes the on-chain leg takes. https://spendthebits.com/insights/domestic-collection-international-payout-msb
- Exchange house cross-border settlement: what changes when the settlement leg moves to stablecoin — Partner pre-funding falls from days of payouts to the interval between settlements; the trapped liquidity moves into a single stablecoin inventory the exchange house holds itself. The stablecoin leg has no cut-off, so settlements can run several times a day and through the weekend; the binding constraint becomes the partner's local clearing window. Every sender-side and beneficiary-side control stays; the additions are wallet screening, Travel Rule data to the partner as a VASP, a stablecoin selection policy and a custody policy. https://spendthebits.com/insights/exchange-house-cross-border-settlement-stablecoins
- PvP settlement with stablecoins: how atomic FX legs remove Herstatt-style exposure — Payment-versus-payment on a stablecoin rail is atomic only when both legs sit on the same chain and a single transaction releases both. Anything else is near-atomic and has a measurable exposure window. Near-atomic means the window between one leg becoming irrevocable and the other being confirmed is bounded by a time-lock or a written release rule, and is measured in minutes rather than hours. The controls a treasury needs are contractual and operational: a settlement agreement naming the contract addresses, an address whitelist, a confirmation-depth policy, dual control on the fallback path and an intraday one-leg-moved report. https://spendthebits.com/insights/pvp-fx-settlement-with-stablecoins
- Weekend cross-border settlement: what a Saturday or public holiday payment actually needs — A public blockchain settles on Saturday and on public holidays, but the fiat systems on either side of it mostly do not. The design problem is the join between a rail that never closes and rails that close every weekend. Cut-offs should be set per leg, not per payment: an on-chain cut-off that is late or absent, a fiat cut-off that mirrors the local clearing calendar, and a published rule for what happens to instructions received between them. Weekend rotas need named approvers with real limits, a compliance reviewer on call for holds and Travel Rule exceptions, and a treasury contact who can move a buffer under dual control. https://spendthebits.com/insights/weekend-holiday-cross-border-settlement
- How the pacs.002 status report should track an on-chain settlement from submission to finality — The four on-chain states a settlement passes through, submitted, pending, confirmed and failed, map cleanly onto the ISO 20022 transaction status codes ACTC or ACSP, ACSP, ACSC or ACCC, and RJCT. PDNG is reserved for a human hold, not for a transaction waiting on confirmations. A single payment should normally generate two pacs.002 messages, one on acceptance and one on completion, with a third only if it fails or is held. One message per block confirmation is a design error. The transaction hash does not fit in a 35-character reference field, so it belongs in the status reason additional information element or in supplementary data, and the choice must be agreed with the counterparty in writing. https://spendthebits.com/insights/pacs-002-status-reports-stablecoin-settlement
- UETR tracking on chain: one reference that answers both the accounting and the compliance question — The UETR is a 36-character UUID that identifies the payment; the transaction hash identifies the settlement. Joined in one table they answer the accounting question, where is the money, and the compliance question, whose money is it, from a single lookup. The UETR is created once, in the first pacs.008 or pacs.009, and is copied unchanged into every later message: OrgnlUETR in the pacs.002 status report and in the pacs.004 return. A new UETR at any hop breaks the chain. The relationship between UETR and hash is many-to-many, because a retry produces a second hash for one UETR and a batched transfer produces one hash for many UETRs, so the mapping is a join table with a row per transfer event, not a column on the payment. https://spendthebits.com/insights/uetr-tracking-on-chain-settlement
- The head.001 business application header: what it carries and why it matters when settlement is on chain — The head.001 business application header is the envelope, not the letter. It identifies who sent the message, who should receive it, what kind of message it is, and when it was created, and it exists separately from the pacs or camt document it wraps. Its key elements are Fr and To for the sending and receiving institutions, MsgDefIdr for the message definition and version, BizMsgIdr for the unique identifier of this business message, and CreDt for the creation timestamp, which under CBPR+ must be in UTC. The header does not carry the UETR. The audit chain therefore runs from BizMsgIdr to the document's MsgId, then to the UETR, then to the transaction hash, and the mapping must store all four. https://spendthebits.com/insights/head-001-business-application-header-explained
- A chain selection policy for corridor settlement: which blockchain settles which corridor, and how to prove it — The unit of decision is the corridor, not the institution: each corridor gets a primary chain, a tested fallback chain, a named token contract and a confirmation rule. Five criteria cover most corridors: finality time, fee volatility at the peak, native stablecoin liquidity on the chain, verified counterparty support and screening vendor coverage. Two of them are binary disqualifiers. The pacs.008 instruction never names a chain. The chain lives in a routing table keyed by corridor, so a chain change is a routing change, not a message change. https://spendthebits.com/insights/chain-selection-policy-corridor-settlement
- Bank API integration timeline for a stablecoin rail: the sandbox-to-production plan and who signs each gate — Plan by gates, not by dates. The integration is finished when the last named signatory has signed, and each gate has an artefact that proves the phase was completed. Message testing means paired evidence: every pacs.008 sent in the test pack has its pacs.002 status report, any pacs.004 return and the on chain transaction hash filed against the same UETR. Screening callbacks are tested for the unhappy path first: a sanctions hit, a wallet hit and a callback endpoint that is down must all hold the payment rather than let it through. https://spendthebits.com/insights/bank-api-integration-stablecoin-settlement-timeline
- Wallet screening for incoming stablecoin payments: what it checks, when it runs, and what to do on a hit — A wallet screen checks three things: direct listing on a sanctions list, exposure through transaction history to mixers, hacks, darknet markets and ransomware, and clustering that links the address to a known counterparty. It runs at three points: when a counterparty address is registered, before an incoming transfer is credited to the client, and before an outgoing transfer is signed. The result at each point is recorded separately. Direct and indirect exposure are different findings. The policy sets a hop depth and a value share above which indirect exposure becomes a hold, and that rule is written down before the first hit. https://spendthebits.com/insights/wallet-screening-incoming-stablecoin-payments
- IVMS101 explained: the Travel Rule data standard, its elements, and how it maps to ISO 20022 party fields — IVMS101 defines the data, not the transport. It is a shared model for originator, beneficiary and VASP information that any Travel Rule protocol can carry, published by the interVASP joint working group in 2020. The model distinguishes natural persons from legal persons and gives each a structured name, a geographic address, a national identification with a typed code, and a customer identifier, so that two VASPs interpret the same field the same way. FATF Recommendation 16 says which elements are required; IVMS101 says how to encode them. The required set is originator name, account or wallet, and one of address, national identifier, customer number or date and place of birth, plus beneficiary name and account. https://spendthebits.com/insights/ivms101-explained-travel-rule-data
- KYB for corporate senders: onboarding a business client for cross-border payments and what monitoring inherits — KYB for a corporate sender produces four things: a verified entity, verified beneficial owners and controllers, an expected activity profile by corridor, and a risk rating with a review date. Monitoring rules are built from the third. Entity verification means an independent registry check of existence and good standing, the constitutional documents, the registered and operating addresses, licences where the client is itself regulated, and an authorised signatory list. Beneficial ownership follows the 25 percent ownership test plus one control person under the FinCEN CDD Rule and the equivalent Canadian test, with each individual identified, verified and screened for sanctions and PEP status. https://spendthebits.com/insights/kyb-corporate-senders-cross-border
- PEP screening in cross-border payments: how a political connection changes the release decision — A foreign PEP is treated as high risk by default in Canada and by most risk-based programmes; a domestic PEP is high risk only after a documented risk assessment. Enhanced due diligence for a PEP means source of funds, source of wealth, senior management sign-off and a shorter review cycle, not simply a second screening. On a stablecoin settlement the PEP decision must be taken before the on-chain transfer, because there is no recall window after the block is final. https://spendthebits.com/insights/pep-screening-cross-border-payments
- SAR and STR filing for stablecoin transactions: what to report, what on-chain detail to include and when — The trigger for a SAR in the US or an STR in Canada is the same for stablecoin activity as for fiat: known or suspected illicit activity, or reasonable grounds to suspect, not the mere use of a blockchain. A useful on-chain filing names the chain, the token, the transaction hash, the sending and receiving addresses and the fiat equivalent at the time, in the narrative or the designated fields. In the US a SAR is due within 30 calendar days of initial detection, extendable to 60 days if no suspect is identified; in Canada an STR is due as soon as practicable once reasonable grounds to suspect are reached. https://spendthebits.com/insights/sar-str-filing-stablecoin-transactions
- Record keeping requirements for cross-border and virtual currency transfers: what to keep and for how long — Five years is the common retention baseline in the United States and Canada for transfer records, reports and identification records, measured from the transaction or from when the record was created or the relationship ended. For a virtual currency transfer the record must include the originator and beneficiary details, the amount and currency, the fiat equivalent and exchange rate, the wallet addresses and the transaction hash. The ISO 20022 message and the on-chain hash are two halves of one record: the message carries the parties and purpose, the hash proves the settlement. https://spendthebits.com/insights/record-keeping-cross-border-payments-msb
- The FINTRAC Large Virtual Currency Transaction Report: threshold, 24-hour rule, fields and timing — An LVCTR is required when a reporting entity receives virtual currency worth CAD 10,000 or more in a single transaction, or in two or more transactions totalling that amount within 24 consecutive hours from or on behalf of the same person or entity. The report is due within five working days after the day the amount was received, and it is filed electronically through FINTRAC's reporting system. The fields include the virtual currency type and amount, the Canadian dollar equivalent with the exchange rate and its source, the sending and receiving addresses, the transaction identifier, and the conductor, third party and beneficiary details. https://spendthebits.com/insights/fintrac-lvctr-virtual-currency-reporting
- Retail Payment Activities Act registration: what Bank of Canada supervision means for PSPs and their partners — The RPAA requires payment service providers that perform retail payment activities for Canadian end users, or from a place of business in Canada, to register with the Bank of Canada; banks and other prudentially regulated entities are excluded. Registration opened in November 2024 and the substantive obligations, operational risk management and safeguarding of end-user funds, came into force on 8 September 2025. Safeguarding means holding end-user funds in trust or in a segregated account with insurance or a guarantee, so that funds can be returned promptly if the PSP fails. https://spendthebits.com/insights/bank-of-canada-rpaa-psp-registration
- Paying out into the EU in stablecoins from outside it: what MiCA actually requires of you — A non-EU institution that transfers or exchanges crypto-assets for EU clients on a commercial basis is providing a crypto-asset service under MiCA and needs an authorised CASP in the chain; the reverse solicitation exemption is narrow and cannot be engineered. Only e-money tokens issued by an EU-authorised credit institution or electronic money institution with a published white paper may be offered to the public in the EU, which as of mid-2026 admits USDC and EURC and excludes USDT from regulated EU venues. The MiCA transitional period for existing CASPs ended on 1 July 2026 at the latest, and several member states closed it earlier, so there is no longer any grandfathered counterparty to rely on. https://spendthebits.com/insights/mica-casp-eu-stablecoin-payouts
- Which state money transmitter licenses do you need when the value you move is a stablecoin? — FinCEN registration as an MSB is federal and does not license anything; whether a stablecoin transfer needs a state money transmitter license depends on each state's definition of money or monetary value and on its published guidance. States fall into recognisable groups: those that read stablecoins into the existing money transmission statute, those that have a separate virtual currency regime such as New York's BitLicense and California's Digital Financial Assets Law, and those that have published exemptions or no-action positions for pure custody or non-custodial models. The Money Transmission Modernization Act drafted by the Conference of State Bank Supervisors gives a common definitions and examination framework in the states that have adopted it, but its adoption is uneven and its virtual currency treatment still varies by state. https://spendthebits.com/insights/state-money-transmitter-licenses-stablecoins
- Choosing a stablecoin liquidity provider: issuer, exchange, OTC desk or bank, and what goes in the agreement — The four counterparty types, issuer direct, exchange, OTC desk and bank partner, differ mainly in who holds your funds during conversion, how the price is formed and what settlement timing you can hold them to. Issuer-direct minting and redemption at par is the anchor rate; every other provider is priced as a spread to it, and you should be able to see that spread on every fill. Due diligence is about the provider's regulatory status, banking, custody arrangements, reserve exposure and operational resilience, evidenced by documents rather than by a slide deck. https://spendthebits.com/insights/choosing-stablecoin-liquidity-provider
- Same-day FX conversion in stablecoin settlement: when the rate is fixed, who bears the move, how to prove it — A cross-currency stablecoin settlement has up to three rates, local currency to dollar, dollar to stablecoin and stablecoin to destination currency, and each must have a fixing time, an owner and a record. Fix the customer rate at the moment you can hedge or fill it, quote with a short validity window, and either carry the move between quote and fill on your own book or pass it through with the customer's agreement; never leave it unassigned. Same-day execution is achievable because the stablecoin leg settles in minutes, so the constraint moves to the local fiat rails and your liquidity provider's cut-off calendar. https://spendthebits.com/insights/same-day-fx-conversion-stablecoin-settlement
- Reconciliation breaks in stablecoin settlement: a taxonomy, the treatment for each, and the ageing report — A stablecoin settlement reconciliation runs across three records, the chain, the payments subledger and the general ledger, and a break is any item that does not match across all three within the tolerance. The recurring break types are unmatched inbound, wrong chain or wrong asset, partial amount, duplicate, dust, fee asset and timing, and each has a standard treatment that can be written down and followed without judgement in most cases. Every break type needs a named owner, a time limit measured in business days and an escalation route; breaks that outlive their limit are the ones a reviewer will pull first. https://spendthebits.com/insights/reconciliation-breaks-stablecoin-settlement
- Stablecoin custody for MSBs: self custody, qualified custodian or regulated wallet provider? — A licensed MSB has three workable custody models: self custody with hardware keys, a qualified custodian such as a chartered trust company or bank, and a regulated wallet provider running threshold signing under the MSB's own policy. The right answer for most MSBs is a split, not a single choice: a small operating float in a policy-controlled wallet sized for the day's payouts, and everything above that in cold storage or with a custodian. Recovery, not theft, is the most common failure in self custody. If one officer holds the only backup, the firm has a single point of failure whatever the hardware says. https://spendthebits.com/insights/stablecoin-custody-options-msbs
- The B2B2B payments model: how a bank offers stablecoin-settled cross-border payments under its own brand — In a B2B2B payments model the bank keeps the customer relationship, the account, the KYB file and the pricing decision. The settlement provider supplies the rail, the screening tooling and the message plumbing, and never faces the business client directly. KYB is not shared. The bank performs it under its own BSA or FINTRAC programme, and the provider consumes a customer identifier and the Travel Rule data, not the passport scans. Liability follows the licence. The bank is liable to its client for the payment obligation; the provider is liable to the bank under a service agreement with service levels and indemnities, and can be examined as a bank service provider. https://spendthebits.com/insights/b2b2b-payment-model-banks-business-clients
- B2B2C remittance fintech: what the consumer app owns and what the stablecoin settlement layer provides — In a B2B2C remittance model the consumer fintech owns the customer: KYC, the consumer disclosures, the licence or registration in each sending jurisdiction, complaints and refunds. None of that can be outsourced to the settlement layer. The settlement layer provides the institutional plumbing: stablecoin settlement between the fintech and the payout partner, sanctions and wallet screening on each transfer, Travel Rule data exchange and the final local-currency payout to a bank account. A consumer payment becomes a local payout in five steps: collection in the send currency, conversion to a regulated stablecoin, an on-chain settlement leg, an off-ramp at the destination and a local clearing credit. Each step needs a named owner and a status event. https://spendthebits.com/insights/b2b2c-remittance-fintech-stablecoin-rails
- Neobank cross-border payments: launching international transfers without a correspondent relationship — A neobank cannot usually obtain a correspondent account because it is not a bank, and its sponsor bank rarely wants to extend its own correspondent lines to the programme. Stablecoin settlement replaces the correspondent leg with an on-chain transfer between regulated counterparties. The sponsor bank still matters. It holds the customer deposits, approves the product, owns the BSA programme the neobank operates under, and will need to approve the settlement provider as a third party before a single payment moves. Every international payment has three legs: an on-ramp from the customer's fiat balance into stablecoin, an on-chain settlement leg, and an off-ramp into the destination currency through a licensed payout partner. Each leg has an owner, a cut-off and a failure mode. https://spendthebits.com/insights/neobank-cross-border-payments-stablecoins
- Remittance corridor selection: a scoring framework for launching stablecoin settlement corridor by corridor — Remittance corridor selection has two gates and five scores. The gates are regulatory clarity at both ends and a live, licensed payout partner; a corridor that fails either is not scored, it is deferred. Demand should come from the institution's own data, such as existing customer nationalities, inbound salary sources and support tickets, and from public sources such as the World Bank's Remittance Prices Worldwide database, never from a guess about a diaspora. Local payout reach means the share of likely beneficiaries who can be credited on a domestic rail within the delivery promise, not the number of banks a partner lists on a slide. https://spendthebits.com/insights/remittance-corridor-selection-framework
- Swift just delayed the November 2026 ISO 20022 deadline. Here are the dates that still stand — On 27 August 2026 Swift applied a controlled extension to Standards Release 2026. Every payments related change due on 14 November 2026, including the removal of unstructured postal addresses, is deferred, and Standards Release 2025 stays in force until a replacement goes live. The core migration is not delayed because it already happened. The MT to ISO 20022 coexistence period for cross border payment instructions ended on 22 November 2025, Fedwire moved on 14 July 2025, CHIPS in April 2024, TARGET2 and CHAPS in 2023. Market infrastructures are following Swift. The Bank of England deferred its entire November 2026 RTGS release on the same day, and Federal Reserve Financial Services has moved its planned November 2026 Fedwire release to November 2027. https://spendthebits.com/insights/swift-iso-20022-november-2026-deadline-delayed
- 21 banks are building one stablecoin for 2027. Should your institution wait for it? — The consortium announced on 1 September 2026 is a statement of intent with a launch target in the first half of 2027. Nothing settles on it today, and consortium projects in payments have a long history of slipping. Its arrival would validate the model, not replace it. A bank issued dollar token on public chains is the same settlement mechanism institutions already use with USDC and USDT, backed by a different issuer. Tokenised deposits and stablecoins are being built for different jobs. The DBS and Citi weekend payment on Swift's Digital Ledger on 5 September 2026 moved bank money between members of a closed network. A stablecoin moves value to anyone who can hold a wallet. https://spendthebits.com/insights/bank-consortium-stablecoin-should-you-wait
- The CLARITY Act failed in the Senate. Here is what actually changes for banks and MSBs moving money on stablecoins — The vote on 15 September 2026 stalled market structure legislation, not stablecoin legislation. The GENIUS Act was signed in July 2025 and its implementing rules are still moving through Treasury, the OCC, FinCEN and OFAC on their own timetable. What stays unresolved is the line between the SEC and the CFTC over digital assets that are not payment stablecoins. For an institution that settles in USDC or USDT and never touches those assets, that gap changes little in practice. The calendar is now the constraint. The Senate is expected to leave Washington in early October for the midterm elections, so a second attempt this year would need a deal that did not exist on the floor this week. https://spendthebits.com/insights/clarity-act-fails-senate-what-changes
- USDC treasury operations at a bank: custody, sweeps, reconciliation and audit — Holding USDC is a credit decision before it is an operations decision. The bank takes issuer risk, reserve risk and redemption risk, and those belong in the framework that governs any other short dated exposure. Treat the operating wallet like a till and custody like a vault. Sweeps and draw downs should run off a written trigger, not a judgement call made each morning. Fund the fee asset as deliberately as the USDC. A transfer needs the native asset of the chain to pay the network fee, and an empty fee wallet queues every payment behind it. https://spendthebits.com/insights/usdc-treasury-operations-bank
- Credit union international payments: serving business members without a correspondent relationship — A credit union rarely fails at international payments for technical reasons. It fails because correspondent access is priced on volume it does not have. A correspondent relationship provides four things: an account in the destination market, payout reach, a messaging path and a compliance counterparty. All four have to be replaced, not only the account. Stablecoin settlement removes the account and the pre funding behind it. It does not remove the message. ISO 20022 pacs.008, pacs.009, pacs.002 and pacs.004 still carry the meaning an auditor reads. https://spendthebits.com/insights/credit-union-international-payments
- pacs.004 returns after stablecoin settlement: what the message must carry — A pacs.004 is a return, not a cancellation. A cancellation request travels as a camt.056 and is resolved by a camt.029. The pacs.004 is what moves settled value back. A blockchain transfer cannot be reversed. A return after stablecoin settlement is a new transfer in the opposite direction, with its own hash, its own screening and its own record. The message must join the two payments. It carries the original references and the original UETR, the returned settlement amount, the charges that explain any difference, and a structured reason code. https://spendthebits.com/insights/pacs-004-returns-stablecoin
- GENIUS Act reserve requirements: what issuers hold and what a counterparty should verify — A permitted payment stablecoin issuer must back every token one for one with permitted reserve assets. The GENIUS Act names the qualifying categories, and anything outside that list does not count. Permitted reserves are short dated and liquid: cash, central bank deposits, insured bank deposits, short dated Treasury bills, short tenor repurchase agreements and government money market funds. Corporate credit and other digital assets do not qualify. Reserves may not be rehypothecated except in narrow cases, no interest may be paid to holders, and holder claims rank ahead of other creditors if the issuer fails. https://spendthebits.com/insights/genius-act-reserve-requirements
- MSB examination readiness: what a first BSA or FINTRAC exam asks for — An examination does not test whether a compliance programme exists. It tests whether it ran on a named date for a named customer, and whether you can prove it. The four programme requirements are the spine of every US examination: written policies and internal controls, a designated compliance officer, ongoing training, and independent testing. The risk assessment is the hinge. Controls that do not trace back to a dated, approved risk assessment read as generic, and generic is the most common finding. https://spendthebits.com/insights/msb-examination-readiness
- Nostro reduction with stablecoins: how much a mid-size bank can actually retire — Stablecoins retire part of a nostro book, not all of it. The honest unit of analysis is one corridor at a time, not the whole balance sheet. The best candidates are outbound corridors with modest volume, unpredictable timing and a reliable local off ramp. They hold the most idle cash per payment made. Minimum balances written into a correspondent agreement, intraday liquidity balances and currencies with no compliant ramp all stay. Those are obligations, not funding choices. https://spendthebits.com/insights/nostro-reduction-with-stablecoins
- Stablecoin settlement finality vs Swift gpi: what a treasurer can rely on — Finality is a legal question, not a speed question. The test is when a transfer can no longer be reversed, and by whom. Swift gpi improved tracking and service levels, but finality still attaches in the underlying settlement systems, and a payment can still be recalled or returned by pacs.004. On a public blockchain the transfer and the settlement are the same event, so finality is strong at the ledger and conditional at the edges: issuer controls and the fiat off ramp both have their own rules. https://spendthebits.com/insights/stablecoin-settlement-finality-vs-swift-gpi
- Cross-border payment compliance management: the operating model for banks and credit unions — Cross-border payment compliance management is an operating model, not a longer control list. Most institutions already own every control individually. The seam that fails most often sits between the team that builds the payment message and the team that screens it. Name one record of truth for party data. Thresholds differ by jurisdiction. FATF sets a 1,000 USD or EUR threshold for virtual asset transfers, the US Bank Secrecy Act travel rule applies at 3,000 dollars, and the EU applies no de minimis to crypto-asset transfers. https://spendthebits.com/insights/cross-border-payment-compliance-management
- ISO 20022 integration challenges: a phased migration plan for banks and credit unions — The hard part of ISO 20022 is rarely the XML. It is the core banking fields, screening rules and reconciliation logic that the richer message touches. Swift ended coexistence for financial institution payment messages on 22 November 2025, and MT101 payment initiation plus structured addresses follow on 14 November 2026. Truncation is the quiet failure mode. Data that arrives structured and is stored as free text cannot be recovered downstream. https://spendthebits.com/insights/iso-20022-integration-challenges
- Strategies for MSB De-risking Solutions Through Enhanced Compliance and Stablecoins — Proactive compliance, not reactive, is key for MSBs to mitigate correspondent banking de-risking. Adopting ISO 20022 messaging standards and the FATF Travel Rule enhances transparency and trust with financial institutions. Regulated stablecoin settlement offers a compliant and efficient alternative for cross-border payments with on-chain auditability. https://spendthebits.com/insights/msb-de-risking-solutions
- Unpacking OCC and Fed Stablecoin Guidance: What It Means for US Banks and Credit Unions — Recent OCC and Fed guidance permits US banks and credit unions to engage in stablecoin-related activities under existing regulatory frameworks. Financial institutions must prioritize robust risk management, compliance, and operational resilience when exploring stablecoin settlement. The absence of specific stablecoin legislation necessitates careful interpretation of existing banking laws for new digital asset activities. https://spendthebits.com/insights/occ-fed-stablecoin-guidance
- Decoding Beneficial Ownership for MSBs: The Corporate Transparency Act and Stablecoin Payments in 2026 — The Corporate Transparency Act requires most U.S. reporting companies, including many MSBs, to disclose beneficial ownership information to FinCEN. This shift places a direct reporting burden on MSBs themselves, moving beyond traditional customer due diligence requirements. Non-compliance with CTA can result in significant civil and criminal penalties, emphasizing the need for robust internal processes. https://spendthebits.com/insights/beneficial-ownership-msb-cta
- Navigating Cross-Chain Stablecoin Compliance: A Guide for Financial Institutions and MSBs Amidst New US Regulations — Consistent compliance across multiple blockchains is crucial for stablecoin payments under new US regulations. Implementing robust KYB, KYC, KYT, and Travel Rule solutions across diverse chain architectures is a core challenge. ISO 20022 message types provide a critical standard for interoperable compliance data in stablecoin transactions. https://spendthebits.com/insights/cross-chain-stablecoin-compliance
- Universal Compliance Control (UCC): Securing Cross-Chain Stablecoin Settlement with Uniform Regulatory Adherence — Cross-chain stablecoin settlement offers efficiency but introduces complex compliance challenges. Fragmented regulatory landscapes and varying blockchain protocols demand a unified compliance approach. Universal Compliance Control (UCC) standardizes compliance enforcement across different blockchain networks. https://spendthebits.com/insights/ucc-cross-chain-settlement
- pacs.009 Stablecoin Settlement: Transforming Interbank Operations for 2026 — pacs.009 stablecoin settlement enables real-time interbank transfers with immediate finality. This approach provides on-chain auditability, significantly enhancing transparency and compliance. It helps financial institutions reduce liquidity bottlenecks and operational costs associated with traditional correspondent banking. https://spendthebits.com/insights/pacs-009-stablecoin-settlement
- Optimizing Working Capital with Stablecoin Settlement for Institutional Treasuries — Working capital stablecoin settlement significantly reduces the time and cost associated with traditional cross-border payments. By leveraging regulated stablecoins, institutional treasuries can free up trapped capital and improve liquidity management. ISO 20022 messaging standards ensure rich data transfer and seamless integration with existing financial operations. https://spendthebits.com/insights/working-capital-stablecoin-settlement
- How ISO 20022 Messaging Facilitates Efficient Tokenized Securities Settlement — ISO 20022 provides a standardized language for tokenized securities settlement across traditional and blockchain systems. Specific message types like sese.023 and pacs.008 enable rich data exchange for digital assets. Combining ISO 20022 with public blockchains allows for atomic settlement with regulated stablecoins. https://spendthebits.com/insights/iso-20022-tokenized-securities
- Unlocking Liquidity: How Real-Time Treasury Stablecoins Transform FX Management — Real-time treasury stablecoins provide immediate, atomic settlement for cross-border transactions, reducing settlement risk and improving working capital efficiency. The inherent transparency and auditability of blockchain-based stablecoin settlement streamlines reconciliation and compliance processes. Adopting a real-time stablecoin strategy requires careful consideration of regulatory frameworks, stablecoin selection, and robust integration with existing systems. https://spendthebits.com/insights/real-time-treasury-stablecoins
- Achieving Blockchain Compliance Interoperability Across Disparate Networks — Blockchain compliance interoperability ensures consistent regulatory rule enforcement across diverse DLTs. Rising compliance costs and evolving regulations make interoperable solutions critical for financial institutions. Oracle-based systems provide a robust method for off-chain compliance checks and on-chain enforcement. https://spendthebits.com/insights/blockchain-compliance-interoperability
- pacs.008 vs MT 103: Elevating Cross-Border B2B Payments with ISO 20022 — ISO 20022's pacs.008 messages provide significantly more structured data compared to SWIFT MT 103. Enhanced data in pacs.008 improves compliance screening, reduces manual errors, and accelerates cross-border settlement times. A phased approach, focusing on data mapping and system upgrades, is crucial for a successful ISO 20022 migration. https://spendthebits.com/insights/pacs-008-vs-mt-103-cross-border-payments
- GENIUS Act compliance checklist — what payment stablecoin issuers must do (licensing, 1:1 reserves, par redemption, monthly disclosure, no issuer-paid interest) and what institutional users should verify before settling on a stablecoin; federal rulemaking still in progress as of mid-2026. https://spendthebits.com/insights/genius-act-compliance-checklist
- MSB licensing in the US and Canada — US: FinCEN MSB registration plus per-state money transmitter licences; Canada: FINTRAC MSB registration under the PCMLTFA (plus Revenu Québec in Québec) and a foreign-MSB regime for offshore firms serving Canadians. https://spendthebits.com/insights/msb-license-us-canada-guide
- How to get an MSB license in the USA — two separate exercises: (1) free federal FinCEN registration on Form 107 via BSA E-Filing, due within 180 days of first meeting the MSB definition, renewed every two years — an AML registration that authorises nothing; (2) a state money transmitter licence in nearly every state (Montana the long-standing exception), each with its own application/investigation fee (low thousands), surety bond (tens of thousands to several hundred thousand of coverage) and minimum tangible net worth, filed through NMLS. Typical multi-state timeline 9–18 months; all-in programme cost commonly passes US$1m. Roughly 29,400 MSBs on the FinCEN register; the Money Transmission Modernization Act adopted in whole or part by ~31 states as of early 2026. Foreign-located firms doing business substantially in the US must register and appoint a US agent for service of process. https://spendthebits.com/insights/how-to-get-msb-license-usa
- MSB registration in Canada with FINTRAC — Canada is a registration regime, not a licensing one: no fee, no statutory minimum capital, no staffing threshold. Regulated activities are FX dealing, money transferring, issuing/redeeming money orders, virtual currency exchange and transfer, and crowdfunding platform services. Registration is refused or revoked where the compliance programme (appointed officer, written policies, risk assessment, training, biennial effectiveness review, KYC/reporting/Travel Rule) is absent — FINTRAC escalated revocations through 2026, including 23 on a single day in March. Québec additionally requires an Autorité des marchés financiers licence. Foreign firms directing services at persons in Canada must register as a foreign MSB (FMSB). The real bottleneck is banking access, not registration. https://spendthebits.com/insights/msb-license-canada-fintrac
- VASP vs MSB: what is the difference? — VASP is the FATF Recommendation 15 category (exchange between virtual assets and fiat, exchange between virtual assets, transfer, safekeeping/administration, participation in an issuer's offer/sale), adopted into national law jurisdiction by jurisdiction. MSB is a US Bank Secrecy Act classification (money transmitters, FX dealers, cheque cashers, money-order issuers, prepaid access). The term VASP does not appear in US statute — the same activity is regulated as money transmission. EU equivalent is the CASP under MiCA. Most stablecoin payment firms are both at once; both perimeters carry the Travel Rule (FATF R16, ~US$/EUR 1,000 for virtual assets, US$3,000 for conventional funds transfers). Open edges: DeFi control tests, unhosted wallets, and payment-stablecoin-specific treatment. https://spendthebits.com/insights/vasp-vs-msb-difference
- The CLARITY Act, explained for banks and MSBs — the US market-structure bill (SEC/CFTC split, digital-commodity definition, intermediary registration, custody segregation); House-passed 294–134, stalled short of 60 Senate votes as of July 2026 over ethics, DeFi and stablecoin-yield disputes; not yet law — institutions should build to regulated-payments standards now. https://spendthebits.com/insights/clarity-act-explained-banks-msbs
- CLARITY Act + GENIUS Act: the US regulatory stack — GENIUS (law) governs the instrument: licensed issuers, full reserves, par redemption, no issuer-paid interest; CLARITY (pending) would govern the market around it: registration, segregation, disclosure; together they turn stablecoin settlement into a regulated payment. https://spendthebits.com/insights/clarity-act-genius-act-stablecoin-regulation-stack
- CLARITY Act readiness checklist — ten steps banks, credit unions and MSBs can take before the bill passes: inventory digital assets touched, provisionally classify each with dated reasoning, segregate customer from institutional assets, pin down custody and key management, extend the AML programme explicitly to digital assets, document disclosures, name accountable owners, assess venues/counterparties, make records examiner-ready, rehearse failure cases (depeg, frozen address, custodian outage). Not law as of July 2026; every item is already good practice for a regulated payments institution. https://spendthebits.com/insights/clarity-act-readiness-checklist
- The Travel Rule for stablecoins — FATF R16 applies to VASP/stablecoin transfers like wires; originator/beneficiary data must travel WITH the transfer above the ~USD/EUR 1,000 threshold. https://spendthebits.com/insights/travel-rule-for-stablecoins
- KYC, KYB and KYT explained — KYC verifies individuals, KYB verifies entities/ownership, KYT monitors transactions; cross-border stablecoin flows need all three. https://spendthebits.com/insights/kyc-kyb-kyt-explained
- Sanctions screening for cross-border payments — screen originator, beneficiary and on-chain wallet exposure in-flight, before instant settlement is irreversible. https://spendthebits.com/insights/sanctions-screening-cross-border-payments
- Choosing MSB AML compliance software — buyer's checklist: KYC/KYB, KYT monitoring, sanctions screening, Travel Rule, case management/SAR-CTR, examiner-ready audit, settlement integration. https://spendthebits.com/insights/msb-aml-compliance-software-checklist
- Transaction monitoring (KYT) best practices — risk-based rules, behavioural baselines, on-chain analytics, alert tuning, escalation/SAR filing, model governance. https://spendthebits.com/insights/transaction-monitoring-best-practices
- Stablecoin regulation: what banks and MSBs need to know — global themes converge on reserves/redemption, issuer licensing, AML/CFT and the Travel Rule; treat stablecoin flows under existing AML obligations. https://spendthebits.com/insights/stablecoin-regulation-banks-msbs
- What is a VASP? — a Virtual Asset Service Provider exchanges/transfers/custodies/issues virtual assets for others and carries AML + Travel Rule obligations. https://spendthebits.com/insights/what-is-a-vasp
- What is a money service business (MSB)? — a non-bank firm doing money transmission, currency exchange or instrument issuance/cashing, regulated for AML; many are also VASPs. https://spendthebits.com/insights/what-is-an-msb
Industry & cost:
- Swift Hackathon 2026: SpendTheBits' StableNet named a Technical Challenge finalist — Swift named StableNet, the settlement and compliance product built by SpendTheBits, a finalist in the Technical Challenge track of the Swift Hackathon 2026 (theme: scaling digital assets through standards); winners announced October 1, 2026 at Sibos Miami on the Innotribe Stage. Submission: Universal Compliance Control (UCC), which gates on-chain stablecoin settlement behind a valid signed attestation — an on-chain settlement gate that will not clear a transfer without one, paired with a fail-closed off-chain oracle running sanctions, PEP, FATF Travel Rule (IVMS101) and KYT checks. Tested on live public devnets on both Solana and an EVM chain using unmodified USDC; attestations carried via ISO 20022 payment and securities messaging, and settlements project as CBPR+ pacs.008/pacs.009 messages (UETR-tracked, XSD-valid) with pacs.004 returns on rejection. Live testing surfaced ten industry standards gaps that still need closing. https://spendthebits.com/insights/stablenet-swift-hackathon-2026-finalist
- The ISO 20022 migration deadline for banks — SWIFT completed the core cross-border payment migration (MT102/103/201/203 → MX) on 22 November 2025; legacy messages are now rejected, not delivered. A second deadline of 14 November 2026 covers MT101 payment-initiation traffic (must migrate to pain.001v9 via FINplus) and ends support for fully unstructured postal addresses in CBPR+ messages — both enforced as hard rejections, not warnings. https://spendthebits.com/insights/iso-20022-migration-deadline-2026
- Proof of reserves for stablecoins, explained — a point-in-time attestation (usually agreed-upon procedures, not a full financial-statement audit) confirming reserve assets equal or exceed circulating token supply on a given date. Reserve composition (cash/short-dated Treasuries vs. commercial paper) matters as much as the ratio; on-chain supply is independently verifiable, off-chain reserves are not, so credibility rests on the reporting firm's reputation and frequency. https://spendthebits.com/insights/proof-of-reserves-stablecoins-explained
- GENIUS Act vs MiCA: comparing US and EU stablecoin regulation — both require licensed issuance, full reserves and redemption rights, via different architectures: a dedicated US federal payment-stablecoin statute vs. the EU's broader MiCA framework (EMTs/ARTs). MiCA in force since Dec 2024, transitional regime closes 1 July 2026 in most member states; €540m+ in fines issued by March 2026 (incl. a single €62m penalty), only 19 EMT issuers/29 tokens authorised; non-compliant tokens like USDT delisted from EU exchanges. GENIUS Act enforcement comparatively early-stage. https://spendthebits.com/insights/genius-act-vs-mica-stablecoin-regulation
- What happens if you operate as an MSB without a license — 18 U.S.C. § 1960 makes unlicensed money transmission a federal felony (up to 5 years) independent of state penalties (civil fines often compounding daily, plus separate state criminal statutes in most states). Usually discovered via a banking relationship (correspondent/sponsor bank onboarding checks), not a regulator investigation. Consent orders are public record and follow the firm into every future banking relationship; self-disclosure is consistently treated more favourably than being caught. https://spendthebits.com/insights/penalties-for-operating-without-msb-license
- MSB surety bonds, explained — a three-party guarantee (state requires, MSB buys, surety backs) protecting consumers/the state if an MSB fails its obligations, not the MSB itself. Coverage (face value) set per state, often scaling with volume — tens of thousands to several hundred thousand dollars; the premium actually paid is a small % of that, underwritten on the applicant's own credit/financials. A claim doesn't discharge the MSB's liability — the surety has a right to recover from the MSB after paying out. A lapsed bond is treated as equivalent to unlicensed status. https://spendthebits.com/insights/msb-surety-bond-explained
- How to register as a VASP — no single global process; each FATF-aligned jurisdiction runs its own regime (MiCA CASP in the EU, FCA registration in the UK, state MSB licensing + FinCEN in the US). Universal prerequisites: a documented AML/CFT programme (KYC/KYB, wallet-address sanctions screening, monitoring, named compliance officer) and a working Travel Rule mechanism, both built BEFORE filing. Fit-and-proper background checks on directors/beneficial owners/compliance officer are usually the slowest step. Registration in one country confers no recognition elsewhere. https://spendthebits.com/insights/how-to-register-as-a-vasp
- VASP license requirements by country — US: money transmission (state-by-state + FinCEN), no distinct VASP category. EU: MiCA CASP authorisation, passports EU-wide once granted by one member state. UK: FCA registration under the MLRs, notably high rejection/withdrawal rate in practice. Singapore: Payment Services Act via MAS, tiered by volume. UAE: multiple parallel regimes by emirate/free zone (Dubai VARA, Abu Dhabi Global Market) — not one unified licence. No cross-recognition between regimes outside narrow bloc-level passporting (e.g. MiCA within the EU). https://spendthebits.com/insights/vasp-license-by-country
- Thunes vs Tango AML vs StableNet — not substitutes but three layers: Thunes is a payout aggregator network (single API into bank accounts, mobile wallets and stablecoin wallets across ~140 countries via direct local partners, as the company states in mid-2026) which solves reach but leaves pre-funding and FX-spread economics in place; Tango AML is remittance/compliance software for MSBs (KYC, PEP and sanctions screening, monitoring, pattern detection, reporting, CRM) which does not move money; StableNet is the settlement + compliance layer (SWIFT MT / ISO 20022 in, on-chain finality in seconds, KYC/KYB/KYT, sanctions and Travel Rule data attached to the payment) which attacks trapped liquidity and days-in-transit. Compare by binding constraint — reach, examination posture, or pre-funding cost — and expect a combination rather than one winner. https://spendthebits.com/insights/thunes-vs-tango-aml-vs-stablenet
- How banks and credit unions benefit from stablecoin payments — three benefits: releasing working capital immobilised in pre-funded nostro accounts (pre-funding shifts from permanent per-corridor balances to on-demand liquidity), 24/7 settlement so weekend and after-hours payments do not wait for the next banking day, and the ability for community banks and credit unions to serve remittance and SMB cross-border demand that currently leaks to non-bank operators. Also lowers the marginal supervision cost of MSB relationships that de-risking removed. Gating factor is controls (custody, counterparty, reserve diligence, screening/Travel Rule, reconciliation, failure playbooks), not technology. https://spendthebits.com/insights/stablecoin-payments-for-banks-and-credit-unions
- How long do international payments take? — correspondent SWIFT: one to five business days; SWIFT gpi: minutes to 24 hours for most payments; stablecoin settlement: seconds to minutes on-chain, 24/7 — end-to-end time is governed by cut-offs, compliance holds and on/off-ramps. https://spendthebits.com/insights/how-long-do-international-payments-take
- Are stablecoins safe for business payments? — assess reserve quality, depeg history, operational and compliance risk; GENIUS-era licensed, fully reserved payment stablecoins with par redemption materially reduce the classic risks. https://spendthebits.com/insights/are-stablecoins-safe-for-business-payments
- How to choose a stablecoin payment provider — a 12-point checklist: regulatory standing, custody model, compliance stack (KYC/KYB/KYT, sanctions, Travel Rule), settlement finality, liquidity/ramps, messaging interoperability, uptime and audit. https://spendthebits.com/insights/how-to-choose-stablecoin-payment-provider
- Stablecoin treasury management for MSBs — size float per corridor, rebalance on triggers not calendars, diversify issuers/chains, and keep reserves in redeemable, attested stablecoins. https://spendthebits.com/insights/stablecoin-treasury-management-msbs
- What is settlement risk? — the risk of paying away principal without receiving the counter-value (Herstatt risk, 1974); solved domestically by RTGS and in FX by CLS PvP; atomic on-chain settlement removes the gap for stablecoin payments. https://spendthebits.com/insights/what-is-settlement-risk
- Stablecoin adoption in 2026 — supply passed roughly $250B during 2025 and kept growing; transfer volumes now rival card networks on some measures; GENIUS Act licensing pulled banks and PSPs into issuance and settlement (figures hedged, as of early 2026). https://spendthebits.com/insights/stablecoin-adoption-statistics-2026
- What the CLARITY Act means for MSBs and cross-border payments — the bill would put the venues, custodians and instruments around MSB stablecoin flows inside a supervised market structure, directly attacking the ambiguity that drives bank de-risking; prepare with clean licensing, an AML programme extended to digital assets, and rails that carry compliance data with the payment. https://spendthebits.com/insights/clarity-act-msb-cross-border-payments
- Why banks de-risk MSBs — de-risking is driven by the cost/opacity of supervising MSB flows; transparent, screened stablecoin rails lower that cost. https://spendthebits.com/insights/why-banks-de-risk-msbs
- Replacing correspondent banking: what it actually takes — a real replacement must preserve compliance, structured messaging, counterparty data, multi-rail reach and auditability, not just speed. https://spendthebits.com/insights/replacing-correspondent-banking
- Real-time cross-border payments for banks — requires 24/7 settlement, liquidity at the moment of payment, in-flight compliance, ISO 20022 messaging and clear finality. https://spendthebits.com/insights/real-time-cross-border-payments-for-banks
- Freeing trapped liquidity (nostro/vostro) — pre-funded correspondent balances trap working capital; real-time settlement lets value move on demand without standing balances everywhere. https://spendthebits.com/insights/eliminating-nostro-vostro-prefunding
- How much does an international wire transfer really cost? — four charges, not one: the outgoing wire fee (US$35–50 at a major US bank, the only one disclosed up front), the exchange-rate markup (1–3%, invisible because it is priced into the rate and the only charge that scales with transfer size), intermediary/lifting fees deducted in flight by each correspondent (US$15–30), and the receiving bank's inbound charge (US$10–25) — commonly US$70–115 all-in on a US$1,000 transfer. World Bank Remittance Prices Worldwide (Q1 2026), total cost of sending US$200: banks ~14.55%, money transfer operators ~8.8%, global average ~6.2%, digital-first providers ~1%, stablecoin rails under 1%; the UN SDG 10.c target of 3% is not on track. Benchmark on landed amount versus mid-market rate, not on the quoted fee, and price float and exception rates alongside fees. https://spendthebits.com/insights/international-wire-transfer-cost
- Cutting FX cost in cross-border payments — most FX cost hides in the spread, not the fee, and compounds across correspondent hops; reduce hops, settle near the point of need, demand rate transparency. https://spendthebits.com/insights/cutting-fx-cost-cross-border-payments
Technology:
- The best blockchain for cross-border payments — XRP Ledger (3–5s finality, sub-cent fees, payments-native), Ethereum (deepest stablecoin liquidity, higher/variable fees), Solana (high throughput, improving reliability), Stellar (payments-focused, anchor network); choose per corridor, or orchestrate multi-chain. https://spendthebits.com/insights/best-blockchain-for-cross-border-payments
- FedNow and RTP vs stablecoin rails — FedNow (2023) and RTP (2017) are US-domestic instant systems and stop at the border; stablecoin rails extend instant, 24/7 settlement cross-border with compliance attached. https://spendthebits.com/insights/fednow-rtp-vs-stablecoin-rails
- SWIFT to stablecoin migration — SWIFT carries the message, stablecoins carry settlement; migrate corridor-by-corridor using ISO 20022. https://spendthebits.com/insights/swift-to-stablecoin-migration
- ISO 20022 and stablecoins — the structured ISO 20022 data model maps cleanly onto compliant on-chain transfers; it is the bridge between institutional messaging and settlement. https://spendthebits.com/insights/iso-20022-stablecoin-payments
- USDC vs USDT for institutional settlement — choose on reserves/attestation, redemption reliability, regulatory acceptance, chain liquidity and concentration risk; supporting both removes single-issuer risk. https://spendthebits.com/insights/usdc-vs-usdt-institutional-settlement
- Multi-rail payment orchestration — route each payment across correspondent, card, local and stablecoin rails by cost, speed and compliance, with uniform controls. https://spendthebits.com/insights/multi-rail-payment-orchestration
- Settlement finality in stablecoin payments — finality is when a payment is irrevocable and funds are usable; set a per-network confirmation policy plus the token's redemption model. https://spendthebits.com/insights/settlement-finality-explained
- On-ramps and off-ramps — converting fiat<->stablecoin at the edges is the hardest, most regulated part; evaluate ramp coverage corridor by corridor. https://spendthebits.com/insights/fiat-onramp-offramp-institutions
- Stablecoin remittance infrastructure: build vs buy — building means owning custody, multi-chain, liquidity, compliance, messaging and perpetual upkeep; buying wins on speed and compliance assurance. https://spendthebits.com/insights/stablecoin-remittance-infrastructure-build-vs-buy

## Comparison
- StableNet vs a standalone AML/compliance tool: the AML tool screens and monitors only; StableNet adds real-time settlement and SWIFT MT/MX messaging, with compliance attached to the payment. https://spendthebits.com/compare/tangoaml-alternative
- StableNet vs correspondent banking: seconds vs days, ~87% lower cost, fewer intermediaries, with compliance and auditability preserved. https://spendthebits.com/why

## Proof points & recognition
- Two-time winner of Ripple's CBDC Innovate competition (2022 & 2023) for comprehensive, interoperable CBDC/stablecoin settlement. Verify: https://dev.to/ripplexdev/ripples-cbdc-innovate-awards-150000-to-6-winners-for-novel-cbdc-apps-mho
- Circle Alliance Program member (USDC ecosystem). Verify: https://partners.circle.com/partner/spendthebits
- Integrations/partnerships include Buckzy Payments, Wow Finstack and Phaze.
- Press & recognition (independently verifiable sources): https://spendthebits.com/newsroom

## Leadership
- Jaskaran (Jay) Kambo — CEO & Founder. Contact: Jay@spendthebits.com
- John Deaton — Chief Legal Officer & Board Member; nationally recognised crypto attorney and former US Senate candidate.

## Pages
- Home: https://spendthebits.com/
- Platform: https://spendthebits.com/platform
- Solutions: https://spendthebits.com/solutions
- Use cases & payment flows: https://spendthebits.com/use-cases
- Remittance & AML for MSBs: https://spendthebits.com/solutions/remittance-msb
- Why StableNet (vs correspondent banking + ROI calculator): https://spendthebits.com/why
- Insights (21 articles): https://spendthebits.com/insights
- Glossary: https://spendthebits.com/glossary
- TangoAML alternative (comparison): https://spendthebits.com/compare/tangoaml-alternative
- Newsroom (press & recognition): https://spendthebits.com/newsroom
- Company & FAQ: https://spendthebits.com/company
- Trust Center: https://spendthebits.com/trust

## Contact
- General: hello@spendthebits.com
- CEO (Jay Kambo): Jay@spendthebits.com
- Website: https://spendthebits.com