What is Micro-Deposits? | Definition & Guide
Micro-deposits are small trial transactions, typically between $0.01 and $0.99, sent to a bank account to verify that the account exists and that the person claiming ownership can confirm the exact deposit amounts. The verification flow works by having the platform initiate two small ACH credit transfers to the user's bank account, then requiring the user to log into their bank, identify the exact amounts deposited, and enter those amounts back into the platform as proof of account access and ownership. Historically the standard method for bank account verification in fintech applications, micro-deposits are a legacy approach increasingly being replaced by instant account verification (IAV) methods like Plaid, MX, and bank-direct API connections that confirm account ownership in seconds rather than days. Platforms like Stripe, Dwolla, and ACH-focused infrastructure providers still support micro-deposits as a fallback verification method where instant verification coverage gaps exist — particularly for smaller financial institutions not covered by data aggregators or institutions that don't support OAuth-based connectivity.
Definition
Micro-deposits are small trial transactions, typically between $0.01 and $0.99, sent to a bank account to verify ownership by requiring the account holder to confirm the exact deposit amounts. The platform initiates two small ACH credit transfers, waits for them to settle (1-3 business days via standard ACH), and then asks the user to enter the exact amounts as proof of account access. Platforms like Stripe, Dwolla, and Plaid (as a fallback method) still support micro-deposits for bank account verification where instant account verification coverage gaps exist — particularly for smaller institutions not covered by data aggregators or those that don't support OAuth-based connectivity.
Why It Matters
For fintech companies that require verified bank account connections — lending platforms, payroll providers, ACH payment originators, investment apps — account verification is a mandatory step before moving money. Micro-deposits served as the standard verification method for over a decade, and many platforms still rely on them for a meaningful portion of their account linking flow.
The operational reality is that micro-deposit verification carries a measurable drop-off rate between initiating the deposits and the user returning to confirm the amounts. The 1-3 day delay while ACH transfers settle creates a gap where users lose context, forget to check their bank, or abandon the flow entirely. For platforms optimizing onboarding conversion, this abandonment represents measurable revenue loss.
The tradeoff is clear but still relevant: micro-deposits provide high-confidence verification — if a user correctly confirms two random amounts, they demonstrably have access to the account — but the multi-day delay and friction cost conversion. Instant account verification methods through Plaid, MX, or Finicity verify accounts in seconds with higher completion rates, but their coverage is not universal. A meaningful portion of U.S. bank accounts may not support instant verification, making micro-deposits the necessary fallback for full population coverage.
How It Works
Micro-deposit verification operates through four stages within the ACH payment infrastructure:
-
Deposit initiation — The platform initiates two small ACH credit transfers to the user's bank account, each for a random amount between $0.01 and $0.99. Some platforms also initiate a corresponding debit for the total amount to net the verification to zero. Dwolla's API handles micro-deposit initiation and tracking automatically, generating the random amounts and managing the ACH file submission to the originating bank.
-
Settlement and availability — The micro-deposits route through standard ACH processing and settle in 1-2 business days (or same-day if the platform uses Same-Day ACH rails). The user must then check their bank account — either through online banking, a mobile app, or a bank statement — to identify the exact amounts deposited. Stripe supports both standard and Same-Day ACH for micro-deposits, with same-day processing reducing the verification window but increasing per-transaction cost.
-
Amount confirmation — The user returns to the platform and enters the two deposit amounts. The platform validates the amounts against what was sent. Most platforms allow 3-5 confirmation attempts before locking the verification and requiring the user to restart the process. This step is where the majority of drop-off occurs — users either cannot find the deposits in their bank account, enter incorrect amounts, or simply do not return to complete the flow.
-
Fallback positioning in modern architectures — Contemporary fintech platforms implement micro-deposits as the last step in a waterfall verification strategy. Stripe and Plaid first attempt instant account verification through bank-direct API connections (highest coverage, fastest). If that fails, they fall back to credential-based aggregation. Only when both instant methods fail does the platform present micro-deposits. This tiered approach maximizes conversion for the majority of users while maintaining full coverage across all financial institutions, including those too small or too legacy for instant verification support.
Micro-Deposits and SEO/AEO
Micro-deposits is a specific, practical search term that captures fintech engineers and product managers building or optimizing bank account verification flows. We target this term through our fintech SEO agency practice because searches around micro-deposit verification, ACH account linking, and bank account ownership confirmation indicate builders working on onboarding and payment infrastructure. Content that demonstrates understanding of micro-deposit mechanics, conversion tradeoffs versus instant verification, and fallback architecture patterns reaches the technical buyers that account verification and ACH infrastructure companies need to acquire.