Diversified Check Studio logoDiversified Check Studio
FeaturesPricingResourcesKnowledge Center
About
Contact
Sign inCreate account
Legal Center

Legal Center

MICR & Bank Information Handling Policy

How MICR and bank information is handled within the check printing workflow.

Effective Date
August 3, 2026
Last Revised
August 3, 2026
Version
1.0

1. Purpose

Bank account numbers, routing numbers, and the MICR line are the most sensitive information in the check printing workflow. This policy explains how that information is collected, protected, displayed, used, and retained.

2. What We Mean by Bank Information

  • Routing number, also called the ABA transit number.
  • Account number.
  • Check number and check number sequence.
  • Auxiliary on-us and on-us field content.
  • Bank name and bank address associated with the account.
  • The assembled MICR line and its symbol placement.

3. Source of the Information

Bank information is provided by the customer. It is entered manually, imported, or extracted from an image the customer uploads through the Check Capture wizard.

We do not obtain bank information from financial institutions, credit bureaus, or data brokers, and we do not verify with a bank that an account exists or that the customer may draw on it.

4. Protection in Storage

  • Account numbers and other sensitive values receive application-level AES-256-GCM encryption before being written to the database, in addition to platform encryption at rest.
  • Records are scoped to the owning account through row level security.
  • Access within an account is governed by role based permissions.
  • Uploaded capture images and assets are stored in private buckets and are served through short-lived authorized links.

5. Protection in Display

Account numbers are masked in lists and detail views by default. Revealing a full value is an explicit action that is permission-controlled and recorded in the audit log.

Check designs necessarily display the full MICR line, because that is the purpose of the document. Preview and print surfaces should be treated as sensitive.

6. Routing Number Validation

The software validates the structure and checksum of a routing number and may compare it against reference directory data. A passing checksum confirms only that the number is well formed. It does not confirm that the number belongs to your bank, your account, or your check.

7. MICR Construction

The software assembles the MICR line using the E-13B character set, with transit, on-us, amount, and dash symbols placed according to standard structure, and applies clear-band spacing rules for the region at the bottom of the check.

Where the software identifies a spacing, character, or clear-band condition that may impair reading, it presents a warning. Warnings are advisory. The customer remains responsible for the final line.

8. Bank Verification Requirement

Before a design is used in production, the customer must confirm the MICR line against a sample check issued by, or approved by, the financial institution, and must confirm the routing and account numbers with the institution directly.

The software cannot detect a transposed digit that still satisfies a checksum, an account closed by the bank, or an institution-specific on-us convention.

9. Printing Requirements

Correct magnetic reading depends on hardware and consumables that we do not control. Customers should use magnetic ink or MICR toner where their financial institution requires it, print at actual size with scaling disabled, use appropriate check stock, and validate placement with a calibration test print.

Details appear in the Production Readiness Policy and the Check Printing Compliance Notice.

10. Use of Bank Information

Bank information entered by a customer is used only to render designs, produce print output, prevent duplicate check numbers, and maintain the customer's own records. It is not used for marketing, is not sold, and is not shared with third parties except the service providers necessary to host and operate the platform.

11. No Payment Processing

Diversified Check Studio does not transmit payment instructions, does not originate ACH entries, does not hold funds, and does not communicate with clearing systems. Producing a check does not create, verify, or fund a payment.

12. Retention and Deletion

Bank account records are retained while the account is active and are removed with the account, subject to the retention rules in the Data Retention and Deletion Policy. Where a bank account is referenced by print history, the record may be archived rather than deleted so that historical print records remain accurate.

13. Customer Responsibilities

  • Enter bank information only for accounts you own or are authorized to draw on.
  • Limit which users may view, edit, or reveal bank account values.
  • Store printed checks and blank stock in a physically secure location.
  • Dispose of misprints and voided output securely.
  • Notify your financial institution immediately if you suspect check fraud.

14. Changes to This Policy

This policy may be revised. The Last Revised date and version number will be updated when it changes.

15. Contact

Questions about MICR and bank information handling may be directed to:

Diversified Check Studio
A product of Diversified SaaS, Inc.
Diversified SaaS, Inc. is a wholly owned subsidiary of Diversified Universal LLC.
6212 US Highway 6, Suite 184
Portage, IN 46368-5057
Email: CustomerService@DiversifiedCheckStudio.com
Phone: 1 (833) 990-7297
WhatsApp: 1 (833) 990-7297

Questions about this document?

CustomerService@DiversifiedCheckStudio.com1 (833) 990-7297WhatsApp

On this page

Sections will appear when this policy is published.

Related documents

  • Security Overview
  • Check Printing Compliance Notice
  • Routing Directory Information Notice
Diversified Check Studio logoDiversified Check Studio

Design and print real checks from your browser.

1 (833) 990-7297WhatsApp

Politics

© 2026 Diversified Universal LLC. All rights reserved.

Product

  • Features
  • Pricing
  • Compare software
  • Release notes Soon
  • API documentation Soon

Resources

  • All resources
  • MICR education
  • Knowledge Center
  • FAQ
  • Blog Soon
  • Tutorials Soon

Company

  • About
  • Contact
  • Legal Center
  • Educational licenses Soon
  • Partner program Soon
  • Affiliate program Soon