The Fraud Problem in Canadian MCA Lending
Fraud is not a theoretical risk in the merchant cash advance industry — it is a daily reality. Canadian MCA lenders lose significant capital each year to applicants who misrepresent their financial position, fabricate documentation, or exploit gaps in the underwriting process. As the Canadian MCA market has grown, so has the sophistication of the fraud tactics targeting it.
Understanding these tactics — and deploying verification methods that can counter them — is essential for any lender that wants to protect its portfolio.
Common Fraud Tactics in MCA
Doctored PDF Statements
The most prevalent form of MCA fraud is the submission of altered bank statements. Using readily available PDF editing tools, bad actors can modify transaction amounts, add fictitious deposits, remove NSF transactions, or inflate account balances. The edits can be remarkably convincing — matching fonts, formatting, and layout of genuine statements from major Canadian banks like RBC, TD, BMO, and Scotiabank.
Synthetic Statements and Fabricated Accounts
Some fraudsters go beyond editing and create entirely synthetic bank statements using templates or specialized software, depicting a fictional business with fabricated transaction history. These are often paired with fake business registrations and manufactured void cheques. Because the entire document is constructed rather than modified, there are no original artifacts to compare against — making detection through document analysis alone extremely difficult.
Stacking
Stacking occurs when a merchant takes multiple cash advances from different lenders simultaneously, often without disclosing existing positions. The merchant may submit the same (or slightly modified) bank statements to several lenders, securing more capital than their cash flow can support. When the combined holdback amounts exceed the business's ability to pay, defaults cascade across all positions.
Stacking is particularly insidious because each lender sees a file that looks reasonable in isolation. The full picture typically only emerges after default.
Identity-Based Fraud
In some cases, the person applying for the advance is not the actual business owner, or the business itself is a shell entity created specifically to obtain advances. These schemes often involve stolen or synthetic identities paired with fabricated banking documents.
Why PDF Review Alone Is Not Enough
Many Canadian MCA lenders rely on a combination of manual PDF review and automated document analysis (OCR, metadata checks, font analysis) to detect fraud. While these methods catch some altered documents, they have fundamental limitations:
- Metadata can be stripped. Experienced fraudsters know to clean PDF metadata before submission, removing editing traces.
- Font and formatting analysis is fallible. High-quality edits using the correct fonts and spacing can pass automated checks.
- There is no live data to compare against. A PDF is a static artifact. Even if it is genuine at the time of download, it cannot tell you what the account looks like right now.
- Synthetic statements have no "original" to detect. If the document was never a real bank statement to begin with, there are no inconsistencies between the original and a modified version — because there is no original.
Document analysis can tell you whether a PDF has been edited. It cannot tell you whether the underlying data is real. That distinction is the gap that fraudsters exploit.
How Live Portal Verification Closes the Gap
Live portal verification — whether conducted via a live call or an async screen recording — addresses the fundamental weakness of PDF-based review: it shows you the actual banking data, in the actual banking portal, in real time.
Authenticity Is Inherent
When an applicant logs into their RBC or TD online banking portal and navigates to their account summary, the data displayed is coming directly from the bank's servers. It has not passed through the applicant's PDF editor. It has not been downloaded, modified, and re-uploaded. It is the canonical source of truth for that account's financial data.
A screen recording of this navigation captures the entire interaction — the login screen showing the bank's URL, the account dashboard loading with real-time data, the transaction history populating as the applicant scrolls. Fabricating this level of detail convincingly is orders of magnitude more difficult than editing a PDF.
Real-Time Data Versus Static Snapshots
A recorded portal session shows live balances and recent transactions that reflect the account's actual state at the time of recording. If an applicant submitted a PDF showing a $50,000 average balance but the portal recording reveals a current balance of $3,200 with multiple recent NSF transactions, you have immediately identified a material discrepancy.
Immutable Audit Trails
When a screen recording is captured and stored through a purpose-built verification platform, it creates an immutable artifact with clear timestamps and chain of custody. Unlike handwritten notes from a phone call or screenshots taken during a live session, the recording is a complete and uneditable record of exactly what was shown. This audit trail is valuable not only for fraud prevention but also for regulatory compliance and dispute resolution.
AI-Guided Steps Ensure Completeness
One of the challenges with any portal verification — live or recorded — is ensuring the applicant shows the right screens. A skilled fraudster on a live call might rush through certain sections or distract the underwriter. Guided recording platforms address this by providing step-by-step instructions that direct the applicant to specific screens: account summary, three months of transaction history, account details, and other critical data points.
Exact Balance, for example, offers a guided recording mode where the applicant is walked through each required screen with clear instructions. The platform can even use AI-powered evaluation to confirm that each step was completed correctly before allowing the applicant to proceed, ensuring that nothing critical is skipped or obscured.
Practical Fraud Detection with Async Verification
Here are specific things to look for when reviewing a portal verification recording:
- URL bar: Confirm the browser shows the correct bank URL (e.g., easyweb.td.com for TD, secure.bmo.com for BMO). Look for the HTTPS indicator.
- Portal navigation: Watch for natural loading times and page transitions. A real banking portal has slight delays as data loads from the server. A pre-recorded fake may show unnaturally smooth transitions.
- Account holder name: Verify the name displayed in the portal matches the applicant and business name on the application.
- Transaction consistency: Cross-reference visible transactions with the PDF statements submitted. Material discrepancies are an immediate red flag.
- Multiple accounts: Check whether the portal shows other accounts (e.g., loan accounts, lines of credit) that suggest undisclosed debt obligations.
- Date and time: The portal typically shows the current date and time, confirming the recording is recent.
Building Fraud Resilience Into Your Process
No single verification method is foolproof. The strongest fraud prevention comes from layering multiple approaches: PDF document analysis to check for obvious edits, portal verification to confirm live data, and cross-referencing both against the application details. Canadian MCA lenders who adopt this layered approach will find themselves catching fraud that would have slipped through a PDF-only review process.
The cost of fraud in MCA lending is not just the lost principal — it is the operational time spent on collections, the opportunity cost of capital tied up in defaulted positions, and the erosion of portfolio performance metrics. Investing in stronger verification is investing in the long-term health of your lending operation.