Insurance Card OCR API

4.8/5

(30+ reviews)

Insurance card OCR API that reads any US health insurance card

Turn a phone photo or scan of a member's card into structured JSON in seconds. Member ID, group number, payer ID, Rx BIN and PCN, copays and dependents, with a confidence score on each value.

No credit card required

SOC 2 Type II & GDPR

Insurance card OCR API reading member ID, group number, Rx codes and copays from a US health card into JSON

Trusted by finance and product teams at

Why insurance card data slows down intake

Every payer prints its own layout, with member ID, group number and Rx codes in different places, front and back. Staff retype each card, and one wrong digit fails the eligibility check.

Card received

Photo from a patient portal or a front desk scan.

Manual keying

Member ID, group and Rx codes typed into the PMS.

Friction

Long IDs and look-alike codes invite typos.

Eligibility check

Coverage verified with the payer before the visit.

Friction

One wrong digit and the check comes back empty.

Claim rework

Denied claims sent back to be corrected.

Friction

Denials land weeks after the visit.

Record updated

Finally in the system, one card at a time.

RESULT

[X] minutes of manual entry per card, and [X]% of claims denied for registration errors.

See how Mindee fixes it

Plan

company_name, plan_name, issuer_80840

Member

member_name, member_id, enrollment_date

Group & payer

group_number, payer_id

Pharmacy (Rx)

rx_bin, rx_pcn, rx_grp, rx_id

Copayments

copayments[].service_name, copayments[].service_fees

Dependents

dependents

response.json

{

"company_name": { "value": "Blue Harbor Health" }, "plan_name": { "value": "Choice PPO Gold" }, "issuer_80840": { "value": "80840 9140461006" },

"member_name": { "value": "Jordan Carter" }, "member_id": { "value": "BHX928374651" }, "enrollment_date": { "value": "2026-01-01" },

"group_number": { "value": "GRP-0047210" }, "payer_id": { "value": "60054" },

"rx_bin": { "value": "610014" }, "rx_pcn": { "value": "MEDDPRIME" }, "rx_grp": { "value": "RX4521" }, "rx_id": { "value": "BHX928374651" },

"copayments": [ { "service_name": { "value": "primary_care" }, "service_fees": [ { "value": 25 } ] }, { "service_name": { "value": "emergency_room" }, "service_fees": [ { "value": 250 } ] } ],

"dependents": [ { "value": "Emma Carter" }, { "value": "Noah Carter" } ],

}

Ready to post, not just to read.

Dates come back in ISO 8601, copays as numbers, and every field carries a confidence score and its position on the card.

Built for cards in a patient's hand, not on a flatbed

Phone photos taken at the front desk, glare on a laminated card, front and back in one upload. The model was trained on the cards patients actually carry.

Six health insurance cards from different payers flowing through Mindee into one JSON schema

Any payer, one schema

National carriers, regional plans, employer cards: the same JSON comes back whatever the layout, with no template to build per payer.

Front and back of a health insurance card merged into one result with member ID and Rx codes

Front and back in one upload

Member data on the front, pharmacy codes on the back. Send both sides as one file and get a single result for the card.

Copay box on a health card returned as a list of services with their fees

Copays returned as data

Primary care, specialist, urgent care and ER copays come back as a list of services with their fees, ready for cost estimates.

Intake scan with an ID card and a health insurance card, each detected, classified and extracted

ID and insurance card on one scan

Front desks often copy the photo ID and the insurance card on one page. Each card is found, classified and read by the right model.

PDF / JPEG / PNG / WEBP / TIFF / HEIC, Front & back in one upload, Any payer layout, Phone photos & scans, ID & insurance card on one scan

Insurance card OCR accuracy you can measure, field by field

Measured on real member cards, not curated samples. Run the same benchmark on your own cards during the free trial.

96.6%

Field-level accuracy on member fields

Member ID, group, payer

93.8%

Accuracy on pharmacy fields

Rx BIN, PCN, group, ID

0.8s

Median time per card

Front and back, synchronous call

A confidence score on every field

Set your own threshold. Fields above it flow straight to your systems; anything below lands in a review queue, with the exact spot on the health insurance card highlighted. Définissez votre propre seuil. Les champs au-dessus partent directement dans vos systèmes ; les autres rejoignent une file de vérification, avec leur emplacement exact mis en évidence sur votre health insurance card. Define tu propio umbral. Los campos que lo superan pasan directamente a tus sistemas; los que quedan por debajo van a una cola de revisión, con la ubicación exacta resaltada en health insurance card.

Auto-approve the health insurance cards you can trust Aprueba automáticamente health insurance cards de confianza Validez automatiquement les health insurance cards fiables

Send only real exceptions to a human

Document AI features, better than OCR

Prepare, classify and extract. Mindee delivers high-accuracy extraction for every document format, so you can automate workflows with speed and high reliability.

Prototype in minutes, go live with the API

Start with a no-code workflow to prove the value on your own health insurance cards, then move the same model into your product. Commencez par un workflow no-code pour prouver sa valeur sur vos propres health insurance cards, puis intégrez le même modèle dans votre produit.

What teams build with insurance card OCR

The same API powers very different products. Here is where it usually starts.

Rated 4.8/5 by developers and operations teams

4.8

on G2

4.9

on Capterra

quote

Mindee works reliably and delivers good performance. The OCR data is accurate, and the API is stable. It works like a charm.

on Capterra

quote

Mindee is a web based tool that help us in scanning and reading different type of documents like identity cards, invoices, proposal plans etc and extract all the information with its AI and then it provides all the information and data associated with these documents a structured way.

on G2

quote

Mindee is an integrated document processing platform backed by reliable AI technology. The service has an intuitive and user-friendly interface and provides highly accurate results extracting data from various document types, especially financial receipts and invoices, which are relatively complex for efficient data extraction and automation.

on G2

FAQ about Mindee's Insurance Card OCR API

Can't find what you're looking for? Our team answers within one business day.

About health insurance card OCR À propos de l’OCR pour les health insurance card

How do you read a US health insurance card?

A US health insurance card usually shows the insurer’s name and plan type (HMO, PPO, EPO…), the member’s name and member ID, the group number, and the copays for common visits. Prescription details (Rx BIN, Rx PCN and Rx Group) are used by pharmacies, and the back often lists the payer ID, the claims address and customer service phone numbers. Mindee extracts all these fields from a photo of the front and back of the card and returns them as structured JSON. Healthcare providers can then fill in patient records and insurance information without manual typing.

What’s the difference between the member ID, policy number and group number?

The member ID (sometimes called the policy number or subscriber ID) identifies the individual covered by the plan. Dependents often share the subscriber’s ID, with a different suffix. The group number identifies the plan the member belongs to, usually through their employer. Both are needed for eligibility checks and claims, and mixing them up is a common source of errors at patient intake. Mindee returns each one as a separate, clearly labeled field, whatever the insurer’s wording or card layout.

Does Mindee work with cards from every insurer?

Yes. Every insurer uses its own card design and terminology, whether it’s Aetna, Blue Cross Blue Shield, Anthem, Cigna, UnitedHealthcare, or Medicaid and Medicare Advantage plans. Mindee doesn’t rely on templates, so it handles these different layouts and returns the same output structure for every card. Patients can simply take a photo of their card on their phone during online check-in, and your team receives data that is ready for eligibility verification. This reduces front-desk work and helps prevent claim denials caused by incorrect insurance information.

Is Mindee HIPAA compliant?

Health insurance cards contain protected health information (PHI), so how it is processed matters. Mindee could be HIPAA compliant and can sign a Business Associate Agreement (BAA) with covered entities and business associates. It is mainly focused on SOC 2 Type II certified, and data is encrypted in transit and at rest. You stay in control of data retention, so you can keep only the fields you need in your own systems.

About Mindee

Is my data secured and protected during the conversion process?

Yes, your data is highly secured and protected during the entire conversion process. As an enterprise-grade OCR solution, Mindee takes data privacy very seriously. Here are the key security measures in place:

  • Certified compliance: Mindee's infrastructure is SOC 2 Type II certified and fully GDPR compliant, ensuring strict industry standards for data protection.
  • Encryption: All documents and extracted data are fully encrypted both in transit (during the API call) and at rest.
  • Data localization: You have control over where your data is processed, with the option to host and process your data on either EU or US servers.
  • Strict privacy: Mindee respects data confidentiality. Your processed documents are not shared with third parties, and your private data is not used to train global AI models.

In short, your sensitive documents are processed in a secure, isolated environment and remain completely under your control.

Is Mindee's OCR API free to use?

We provide a 14 days free trial so you can fully test any of our OCR models — no credit card required. After this, we offer different pricing tiers depending of the volume of pages processed and the features you might need. See the pricing page for more information.

What file formats are supported for JSON conversion?

The supported document formats are:

  • PDF (application/pdf) – While technically a document format rather than an image, it is natively supported for all extraction models.
  • JPEG / JPG (image/jpeg)
  • PNG (image/png) – Must be non-animated.
  • WebP (image/webp)
  • TIFF / TIF (image/tiff) – Both single-page and multi-page TIFFs are supported and processed similarly to PDFs.
  • HEIC (image/heic) – Apple's High-Efficiency Image Container format.

‍

📌 Important technical limitations to keep in mind:

To ensure the OCR pipeline runs smoothly and successfully returns your JSON, make sure your files adhere to the following constraints:

  • Maximum file size: 100 MB per file.
  • Maximum page count: Up to 200 pages per document.
  • File state: The files cannot be encrypted, and PDFs must not be password-protected.

Ready to stop keying insurance cards at intake?

Send your first card to the API in minutes, with a full team of engineers dedicated to document processing behind it.

14-day free trial

No credit card required