Document Intelligence · Cards
Capture card number, cardholder name and expiry from a photo of a credit card, with masking built in for every sensitive field.
Overview
What the Credit Card OCR API does
FinHub's Credit Card OCR API reads an uploaded card image and extracts card number, cardholder name, expiry date and issuing network, returning masked values by default to keep PAN-equivalent data out of your logs and screens. Every call captures consent and writes to a tamper-evident audit log, aligned to DPDP and payment-data handling norms.
Inputs
- Card image (front, PDF or photo)
- Mask level (full / last-4, optional)
- Consent artifact ID
Returns
- Card number
- Cardholder name
- Expiry date
- Issuing network
- Field-level confidence scores
POST /v1/ocr/credit-card
How it works
Three steps to a verified result
Upload the card image
Send a front-facing card image with a consent artifact and your preferred masking level over a single authenticated call.
We extract and mask fields
FinHub's OCR models locate card number, name, expiry and network, applying masking before the response leaves our systems.
Get a decision-ready record
Receive structured, masked card data with confidence scores, ready for card-linking or issuance flows — sealed to your audit trail.
Use cases
Where teams use Credit Card OCR
- Card-linked onboarding for fintech and payments apps
- Card issuance and reissuance workflows
- Expense management and card-on-file capture
- Card fraud investigation document capture
FAQ
Credit Card OCR API — FAQs
Common questions about FinHub's Credit Card OCR API.
By default, the card number is masked to the last four digits; you can request a different masking level, and access to unmasked values is controlled by your consent and audit policy.
More verification APIs
Explore related APIs
Ready to add Credit Card OCR to your flow?
Book a demo and see the API return a verified result on your own test data in minutes.