Skip to main content
Commerce Security Authority
Category: Fraud Detection Analytics

Circular Transactions

Also known as: Circular Trading, Circular Deals, Round-Tripping
Simply put

Circular transactions involve moving money repeatedly through a series of accounts or companies so that funds often return to where they started. This cycling can create the appearance of legitimate business activity or genuine cash flow when little or no real economic exchange has taken place. The pattern is often used to disguise the true source or purpose of funds or to make financial records look healthier than they are.

Formal definition

Circular transactions describe the repeated movement of funds through a chain of accounts, shell entities, or related parties that ultimately returns value to the originating account or party, frequently without corresponding movement of goods or genuine economic substance. In this context, related patterns include circular trading, where goods are ostensibly bought and sold through shell companies without actual delivery, and round-tripping, where two or more entities execute a series of offsetting transactions to manufacture the appearance of legitimate business activity or revenue. Such patterns are commonly flagged as indicators in money-laundering typologies, funnel-account analysis, and credit or underwriting reviews of bank statements, where cash flows may appear artificially consistent or inflated. Detection typically relies on transaction-flow and network analysis to identify cycles and offsetting flows; these methods are indicative rather than conclusive and can produce both false positives, such as legitimate intercompany settlement, and false negatives, so findings should be corroborated with additional evidence. The specific legal, regulatory, and network-rule consequences of identified circular transactions vary by jurisdiction and context and are out of scope for this definition.

Why it matters

Circular transactions matter because they can make financial records appear healthier or more active than the underlying economic reality supports. When funds cycle through a series of accounts, shell entities, or related parties and ultimately return to their origin, they can manufacture the appearance of legitimate business activity, revenue, or consistent cash flow where little or no genuine exchange has occurred. This distortion undermines the reliability of the very documents that lenders, underwriters, and investigators depend on, and it can conceal the true source or purpose of funds.

The pattern surfaces across several distinct contexts. In money-laundering typologies and funnel-account analysis, cycling funds can obscure the origin of illicit proceeds. In circular trading, goods are ostensibly bought and sold through shell companies without actual delivery of those goods. In round-tripping, two or more entities execute a series of offsetting transactions to create the appearance of legitimate business activity or revenue. Each of these variations exploits the assumption that recorded movement of money reflects real economic substance.

For teams reviewing bank statements during credit or underwriting decisions, a borrower's records that look almost too perfect can be a signal worth scrutinizing, since cash flows may appear artificially consistent or inflated. It is important to treat detection outputs as indicative rather than conclusive: legitimate activity such as intercompany settlement can resemble circular flows, and genuinely evasive schemes can evade pattern-based checks. The specific legal, regulatory, and network-rule consequences of identified circular transactions vary by jurisdiction and context.

Who it's relevant to

Fraud Analysts and Financial Crime Investigators
Analysts working money-laundering typologies and funnel-account cases use transaction-flow and network analysis to identify cycles and offsetting flows that may indicate circular transactions. Because these signals are indicative rather than conclusive, analysts should treat detected cycles as leads to corroborate with additional evidence rather than as findings on their own.
Credit and Underwriting Teams
Teams reviewing borrower bank statements may encounter cash flows that appear artificially consistent or inflated, where numbers that look too perfect can point to round-tripping or other circular patterns. This matters for assessing whether reported revenue and cash flow reflect genuine economic activity, while keeping in mind that legitimate intercompany settlement can resemble the same pattern.
Compliance and AML Officers
Circular transactions are commonly flagged as red flags in money-laundering typologies and round-tripping analysis. Compliance teams should understand how these patterns manufacture the appearance of legitimate activity, and recognize that the specific legal, regulatory, and network-rule consequences of identified circular transactions vary by jurisdiction and context.
Merchant Risk and Onboarding Teams
Teams assessing merchants and related parties may see circular trading through shell companies, where goods are ostensibly bought and sold without actual delivery. Awareness of these offsetting, no-substance flows helps inform risk review, while acknowledging that detection methods carry both false-positive and false-negative trade-offs.

Inside Circular Transactions

Circular Transaction Pattern
A sequence of transactions in which funds appear to move between accounts, merchants, or cards and return, in whole or in part, to the originating party, creating the appearance of legitimate commercial activity where little or no genuine economic purpose exists.
Originating and Terminating Party Overlap
A defining element in which the ultimate recipient of funds is the same entity, or a closely related entity, as the original payer, often obscured through intermediary accounts, related merchant IDs, or affiliated cardholders.
Intermediary Layering
The use of one or more intermediate accounts, processors, or merchants to break the direct link between source and destination, which may complicate transaction monitoring and attribution.
Transaction Velocity and Repetition
Repeated, high-frequency movements of similar amounts among a limited set of participants, which detection systems may flag as anomalous relative to expected merchant or cardholder behavior.
Fraud and Abuse Context
Circular transactions may be associated with schemes such as transaction laundering, merchant collusion, chargeback or refund abuse, artificial sales inflation, or money movement intended to obscure the source or purpose of funds; the specific intent varies by case.
Cardholder and Sensitive Authentication Data Considerations
Investigating circular activity typically relies on transaction metadata and cardholder data such as PAN (often truncated or masked). Sensitive authentication data, including full track data, CAV2/CVC2/CVV2/CID, and PINs or PIN blocks, must not be stored after authorization even when encrypted, so analysis should not depend on retaining it.

Common questions

Answers to the questions practitioners most commonly ask about Circular Transactions.

Are circular transactions always evidence of fraud or money laundering?
No. While circular transaction patterns—where funds move through a series of accounts and return toward their origin—can be an indicator of money laundering, bust-out schemes, or transaction laundering, the pattern alone does not establish intent or illegality. Legitimate activity such as refunds, reversals, intercompany settlements, testing, or normal commercial relationships between related parties can produce similar loops. Circularity is a signal that may warrant review, not proof of wrongdoing. Detection controls that flag such patterns carry false-positive risk, so findings should be corroborated with additional context before action is taken.
Is detecting circular transactions the same thing as PCI DSS compliance?
No. Detecting circular transactions is a fraud-monitoring and anti-money-laundering concern focused on transaction behavior and fund flows, whereas PCI DSS governs the protection of cardholder data and sensitive authentication data within an environment. The two address different objectives. A transaction-monitoring capability that identifies circular patterns is not a PCI DSS control in itself, and implementing one does not by itself satisfy or affect PCI DSS validation. Any monitoring system that handles cardholder data would, however, still need to be assessed for scope under the applicable PCI DSS requirements; confirm specifics against the current published standard.
What data points are typically needed to identify circular transaction patterns?
Analysis generally relies on relationship and flow attributes rather than sensitive authentication data. Useful elements can include counterparty or account identifiers, transaction timestamps and sequencing, amounts, merchant and acquirer identifiers, and directionality of funds. Where card data is involved, teams should favor tokenized or truncated representations of the PAN so that pattern analysis does not require storing or exposing full cardholder data. The choice of representation affects PCI DSS scope depending on how it is implemented and validated.
How should teams tune detection to balance false positives and false negatives?
Tuning is a trade-off with no universally correct setting. Tightening thresholds—such as loop length, time window, or minimum recurrence—can reduce false positives but may miss slower or more distributed circular activity, raising false negatives. Loosening them does the reverse and can overwhelm analysts with benign refund-and-reversal loops. Effective programs typically calibrate against reviewed historical cases, segment by merchant category and expected behavior, and document the rationale for chosen thresholds so that detection performance can be re-evaluated as patterns evolve.
How can legitimate circular activity be distinguished from suspicious loops during investigation?
Investigators generally enrich a flagged loop with context: the business relationship between counterparties, whether the flow corresponds to documented refunds or intercompany settlements, the consistency of amounts and timing, and any prior history for the accounts involved. Corroborating evidence helps separate normal operational loops from potential transaction laundering or bust-out behavior. Because a single indicator is rarely conclusive, findings are typically reviewed alongside other risk signals before escalation.
Where does circular-transaction monitoring fit relative to network and card brand rules?
Circular-transaction monitoring is an internal risk-management and, where applicable, anti-money-laundering practice. It operates alongside, but is separate from, card brand and network rules that govern chargebacks, liability shift, and permissible transaction conduct. Those rules vary by region and change over time, so any action taken on suspected circular activity—such as holding funds or terminating a merchant relationship—should be aligned with the applicable network requirements and the organization's own contractual and legal obligations rather than driven by the detection signal alone.

Common misconceptions

Any repeated payment between the same two parties is a circular transaction indicating fraud.
Legitimate recurring commerce, refunds, corrections, and normal business relationships can produce repeated flows. Circular patterns are distinguished by funds returning to the originating or a related party with little genuine economic purpose, and even then they may require further investigation before intent is established. Detection controls carry false-positive and false-negative trade-offs.
Detecting circular transactions is a defined PCI DSS requirement.
PCI DSS focuses on protecting cardholder data and the environments that handle it, not on adjudicating the economic legitimacy of transactions. Monitoring for suspicious money movement is generally driven by anti-money-laundering obligations, card brand and network rules, and acquirer risk programs, which are separate from PCI DSS. Any related control should be confirmed against the current published standard rather than assumed from a fixed requirement number.
Tokenizing or encrypting the PAN eliminates the ability to detect circular transactions.
Tokenization, encryption, truncation, and masking transform or reduce data differently and are intended to protect stored data, not to defeat pattern analysis. Correlation across transactions can often still be performed on tokens, masked values, or other metadata, depending on implementation, though the labels alone do not determine the effect on analysis or on PCI DSS scope.

Best practices

Correlate transactions using tokenized or truncated identifiers and transaction metadata rather than retaining sensitive authentication data, which must not be stored after authorization even when encrypted.
Model expected behavior per merchant, account, and cardholder so that circular patterns are evaluated against a baseline, and tune thresholds to balance false-positive and false-negative rates rather than treating every repeated flow as suspicious.
Investigate overlaps between originating and terminating parties, including related merchant IDs, affiliated accounts, and intermediary layers, before drawing conclusions about intent.
Coordinate with anti-money-laundering, acquirer risk, and compliance teams, since suspicious money movement obligations are governed by AML rules and card brand and network requirements that vary by region and change over time.
Use qualified findings that describe activity as consistent with a circular pattern pending review, avoiding absolute claims of fraud until corroborating evidence supports the conclusion.
Document monitoring logic, data sources, and known limitations so that detection controls can be reviewed, and verify any related data-protection controls against the current published PCI DSS version rather than an assumed requirement number.