Remote deposit capture (RDC) is a deposit channel that lets a business or consumer scan a paper check and send the image to a bank for deposit, instead of carrying the check to a branch. The legal basis is the Check Clearing for the 21st Century Act (Check 21), which the Federal Reserve notes was signed on October 28, 2003 and took effect on October 28, 2004. Check 21 made an image-based substitute for the paper item legally usable, and that is what turned a flatbed scanner or a phone camera into a deposit window.
​

Checks are shrinking but still large. The Federal Reserve Payments Study top-line data counts 9.2 billion check payments worth $24.45 trillion in 2024, down from 17.0 billion in 2015. Value has held up far better than count, which means the checks that remain are often larger business payments. That is the population RDC serves: accounts receivable teams, property managers, nonprofits, municipalities, and any business whose customers still mail paper.
​

This guide walks through the full RDC flow, from scan to funds availability, then covers the main deployment types, the fraud and duplicate-presentment risks regulators focus on, and how RDC compares with a bank lockbox and with moving customers to electronic payments entirely.
​

Remote deposit capture is a bank service that accepts a digital image of a check, plus data read from its magnetic ink line, as a deposit. The depositor keeps the paper original. The bank then clears the item electronically as an image, so the check never physically travels. Businesses use scanners; consumers usually use a banking app.
​

Federal banking examiners describe RDC in plain terms. The FFIEC guidance on RDC risk management, first issued January 14, 2009 and republished by the FDIC with a revision on June 2, 2026, treats RDC as a deposit delivery system in which a customer scans a check or monetary instrument and transmits the digitized image to the institution. The 2026 revision removed references to reputation risk and kept the focus on operational, legal, and compliance risk.
​

Two regulatory terms matter for understanding what an RDC deposit actually is. Regulation CC defines an electronic check as an electronic image of, and information derived from, a paper check that is sent to a receiving bank under an agreement and meets industry standards. The same section defines a substitute check as a paper reproduction showing the front and back of the original with a full MICR line. Most RDC deposits move between banks as electronic checks. The substitute check is the paper fallback that Check 21 made legally equivalent to the original.
​

RDC is not the same as an eCheck or an ACH debit. An ACH payment starts electronic and never has a paper item behind it, as covered in Eco's guide to ACH vs wire transfers. RDC starts with paper and converts it. That distinction drives almost every risk and control discussed below, because a physical original keeps existing after the deposit is made.
​

Remote deposit capture works in five stages: the depositor captures images and MICR data, the bank software validates the item, the bank accepts the deposit, the item clears between banks as an image, and funds become available under the bank's hold policy. The depositor then retains and eventually destroys the paper check.
​

The depositor endorses the check, often with a restrictive endorsement such as "For mobile deposit only" that the bank requires, then scans the front and back. A desktop check scanner reads the MICR line magnetically or optically while imaging. A phone app captures images through the camera and reads the MICR line with optical character recognition. The software also reads or asks for the amount, so the bank can compare the keyed figure against the courtesy and legal amounts on the check.
​

Before the deposit is accepted, the bank's RDC platform checks that the image is usable: legible, correctly cropped, not skewed, endorsed, and complete. It also checks the routing number against valid bank identifiers and compares the item against recent deposits to flag possible duplicates. Items that fail are rejected back to the depositor for a rescan or a branch deposit.
​

Once accepted, the item posts to the account as a pending deposit. Business platforms usually group items into batches, which gives treasury staff a deposit total to reconcile against the remittance documents that arrived with the checks. This is where RDC ties into downstream work like cash application automation, since each check image and its remittance stub can be matched to an open invoice.
​

The depositary bank bundles items into an image cash letter and sends it to the paying banks, either directly, through a private image exchange, or through the Federal Reserve. The Federal Reserve's check services let banks send and receive image cash letters electronically through FedForward and handle returns through FedReturn. If a paying bank cannot accept images, the collecting bank can print a substitute check, which the Fed's Check 21 FAQ says is legally equivalent to the original when it accurately represents the check and carries the legend "This is a legal copy of your check."
​

Regulation CC sets maximum hold periods, and RDC deposits are generally not treated as made in person. Under 12 CFR 229.10, the first $275 of certain check deposits must be available the next business day, and for items like cashier's checks and government checks deposited other than in person to an employee, the deadline stretches to the second business day. Many banks set their own RDC-specific holds and daily limits on top of this, so a business should read its RDC agreement rather than assume branch timing.
​

After deposit, the paper check stays with the depositor. The bank agreement typically specifies a retention window during which the original must be stored securely, then requires destruction, for example by cross-cut shredding. The FFIEC guidance lists retention and destruction protocols among the core RDC controls, because a stored original is the raw material for a second deposit.
​

Remote deposit capture comes in three main forms. Desktop or merchant RDC uses a dedicated scanner at a business location. Mobile RDC uses a smartphone camera and banking app. Bank-hosted or outsourced capture, including lockbox with image output, shifts scanning to the bank or a processor. Each form trades volume capacity against convenience and control.
​

Desktop RDC is the original business form. A company installs a single-feed or multi-feed check scanner connected to a PC and logs into the bank's web platform. Multi-feed scanners can process a stack of checks in one pass, which suits businesses that receive dozens or hundreds of checks a day. Because the scanner reads the MICR line directly, image quality and data accuracy are generally higher than with a phone camera. Banks usually assign business customers a daily and per-item deposit limit based on underwriting.
​

Mobile RDC moved the same concept into banking apps. It serves consumers and small businesses with low check volume, and it is the version most people mean by "mobile deposit." Limits tend to be lower, holds may be longer for new accounts, and the endorsement rules are stricter. For a business, mobile RDC is useful for field staff, such as a contractor collecting a check at a job site, but it is a poor fit for high-volume receivables.
​

Some businesses never scan at all. A lockbox service receives mail at a bank-controlled address, opens envelopes, images checks and remittance stubs, deposits the items, and returns a data file. Other businesses outsource scanning to a third-party processor. These models are not RDC in the narrow sense, since the business is not capturing the image, but the output is the same: an image-based deposit plus data for reconciliation.
​

The main risks of remote deposit capture are duplicate presentment, where the same check is deposited twice, and check fraud, including counterfeit, altered, and stolen items. Regulators also flag operational risk from weak image quality or poor device security, legal risk from warranties and indemnities, and compliance risk under the Bank Secrecy Act.
​

Because the depositor keeps the paper, the same check can be deposited through RDC and then again at a branch, at an ATM, at a second bank, or cashed at a check casher. Some duplicates are honest mistakes, such as a staff member rescanning a batch. Others are deliberate. Regulation CC allocates the loss: under 12 CFR 229.34(f), a depositary bank that accepts an image without receiving the original must indemnify a bank that later accepts the original for deposit if the loss arises because the check was already paid. In practice, the RDC bank then looks to its business customer under the RDC agreement. The Federal Reserve markets FedDetect specifically to give banks early notice of potential duplicate checks.
​

Check fraud is the risk that has grown most visibly. The Financial Crimes Enforcement Network reported on September 9, 2024 that in the six months after its 2023 alert on mail theft-related check fraud, it received 15,417 Bank Secrecy Act reports from 841 financial institutions covering more than $688 million in suspicious activity. Stolen checks are often washed, altered, or counterfeited, then deposited remotely because RDC avoids a teller who might look at the paper. For the payee business, the relevant risk is usually outgoing checks being stolen and deposited elsewhere, while for the depositing business it is accepting a bad check and seeing it returned after goods ship.
​

RDC places bank capture equipment in a customer's office. The FFIEC guidance states that institutions should use effective methods to authenticate customers and that single-factor authentication may not be enough for internet-based services. Unsecured scanners, shared logins, and paper checks left in unlocked drawers all create exposure. Stored images and originals also contain nonpublic personal information, which the guidance flags as a data protection concern.
​

An RDC depositor makes warranties through its agreement, and banks make warranties to each other under Regulation CC and Check 21. When a substitute check causes a consumer loss, Check 21 gives the consumer an expedited recredit right. The Fed's FAQ explains that if a bank cannot resolve a valid claim within 10 business days, it must refund up to $2,500 plus interest, with the remainder due by the 45th calendar day. On the compliance side, RDC can let a customer deposit from anywhere, which complicates Bank Secrecy Act monitoring of who is depositing and from where.
​

Effective remote deposit capture controls combine bank-side underwriting and limits with depositor-side process discipline. Banks vet customers, cap deposits, and run duplicate detection. Businesses restrict scanner access, reconcile every batch, secure and destroy originals on schedule, and use restrictive endorsements so a scanned check is harder to redeposit elsewhere.
​

The FFIEC guidance lists the core bank-side controls: customer due diligence before granting RDC, appropriate deposit limits, retention and destruction protocols, duplicate detection, and training for both staff and customers. It also notes that customer awareness and education are effective deterrents to theft and unauthorized access.
​

On the business side, the controls look like standard treasury segregation of duties:

Reconciliation is where many duplicate deposits get caught before the bank sees them. If each check is tied to a remittance record and an invoice, a second scan shows up as an unexpected overpayment. Eco's guide to remittance advice formats and reconciliation covers how that matching works across payment types.
​

Remote deposit capture suits businesses that receive a manageable number of checks at their own offices and want same-day deposits without branch trips. A lockbox suits high check volume, since the bank handles mail, scanning, and data capture. Moving customers to ACH, wires, or cards removes paper entirely and eliminates most check-specific fraud and duplicate risk.
​

The direction of travel is clear in the data. The Fed's top-line figures put checks at 4 percent of noncash payments by number in 2024, against 39.7 billion ACH payments worth $104.06 trillion. The Fed's July 1, 2026 release of the 2025 study confirmed that check payments continued to decline by both number and value. For most finance teams, RDC is a bridge: it makes the remaining checks cheaper and faster to process while the business nudges payers toward electronic rails.
​

That nudge is not always possible. Some customers, such as government agencies, insurers, and older B2B accounts, keep paying by check regardless of invoice instructions. For those payers, RDC or a lockbox remains the practical answer. For everyone else, a comparison of payment rails helps decide which electronic option to offer in place of a paper check.
​

A business sets up remote deposit capture by applying through its bank's treasury management team, passing an underwriting review, signing an RDC agreement that sets limits and retention rules, installing an approved scanner or app, and training staff on endorsement, scanning, reconciliation, and destruction procedures before the first live deposit.
​

Underwriting is the step that surprises some businesses. Because the bank is extending credit when it makes funds available before a check has finally cleared, and because it carries the Regulation CC indemnity for duplicate items, it reviews the customer's financials, industry, deposit history, and expected check volume. That review sets the daily and per-item limits. A new business with no deposit history may start with low limits that rise over time.
​

The RDC agreement deserves a careful read. Key terms include the cutoff time for same-day credit, hold periods, the retention window for originals, required endorsement wording, liability for duplicates and returned items, and whether the bank can audit the business's RDC environment. The FFIEC guidance expects banks to have contractual rights covering these points, so a business should assume they will be enforced.
​

Finally, measure whether RDC is working. Useful internal metrics include days from check receipt to deposit, rejected image rate, returned item rate, and any duplicate deposit incidents. If volume grows past what staff can scan comfortably, a lockbox often becomes the better choice. If returned items and fraud attempts rise, it may be time to push harder on electronic payment adoption.
​

Remote deposit capture raises recurring questions about legality, hold times, what happens to the paper check, and how RDC fits with electronic payments. The short answers: it is legal under Check 21 and Regulation CC, holds depend on the bank within federal maximums, originals must be kept then destroyed, and RDC complements rather than replaces electronic payments.
​

An image exchanged between banks by agreement is an electronic check under Regulation CC. A printed substitute check is legally equivalent to the original if it meets the Check 21 requirements, including an accurate image and the required legal copy legend.
​

No. That is duplicate presentment. Under 12 CFR 229.34(f) the RDC bank indemnifies a bank that later takes the original, and RDC agreements pass that liability to the depositor.
​

Generally not. RDC is built around US checks with MICR lines that clear through the US image exchange system described in the Federal Reserve's check services. Foreign items usually need to go through a bank's collection process.
​

For finance teams that are cutting check volume, the logical next step is moving recurring payers onto faster electronic settlement. Eco, which builds stablecoin payment infrastructure, is one option some businesses evaluate for cross-border and treasury flows once paper is no longer the constraint.
​