Passport Verification API
Check the available passport record behind a submitted file number and date of birth, and use the structured result in travel, forex, hiring or non-resident onboarding.
Overview
An Indian passport is among the strongest identity documents a customer can present, and it is often the only one available when that customer is overseas. It also turns up wherever the stakes are high, such as foreign exchange, cross-border onboarding and hiring for roles that involve travel. The Passport Verification API takes the file number and the applicant's date of birth and returns the available record in structured form. That covers applicant details, the application type and date, and the current status of the record. Available fields vary by data source and by the individual record. A passport carries sensitive personal data. Make every request with the holder's informed consent and for an authorized business purpose, and use the response only for that purpose.
- Category
- KYC Services
- Coverage
- India. What is available depends on the underlying record and your service contract.
- Input
- Passport file number, paired with the applicant's date of birth
- Output
- Structured applicant, application-type, date and record-status details, where available
- Typical users
- Travel and visa services, forex and remittance providers, banks and brokerages, employers and staffing platforms, insurers
- Coverage note
- India. Available fields vary by data source, by the individual record and by your service contract.
The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.
Reference in progress
The request and response reference for this endpoint is not published yet.
Everything below this block is the live catalog record for this service, and it is accurate. The platform’s published API contract does not include this service yet, so there is no request or response detail to document. Rather than fill these sections with a plausible example, the page lists what is missing:
- Endpoint URL and method
- The host, path and HTTP verb for this service.
- Authentication
- How a request identifies itself, and where credentials come from.
- Request parameters
- Field names, types, which are required, and validation rules.
- Response schema
- The success body, field by field, with a real example.
- Error codes
- What each failure means and which are worth retrying.
- Rate limits
- Request ceilings, and what happens at the ceiling.
No sample payload, URL, response body, error code, rate limit or latency figure appears anywhere on this site unless it has been supplied and attributed. Each item in this list is removed only when its own detail arrives; none of them is held back to wait for the rest, and none is ever placed beside a guess in the meantime.
Use cases
- Travel: confirm traveler identity before a booking is confirmed or a visa file is lodged
- Forex and remittance: verify the identity behind a cross-border transaction
- Banking and brokerages: onboard non-resident customers with no local address proof
- Hiring and staffing: run an identity check on candidates for roles that involve travel
- Insurance: verify identity on travel and international health cover applications
- Real estate: check non-resident buyers and overseas tenants before a file proceeds
What this service does
Checks the record behind the booklet
Reading the data page tells you what is printed. Verification reports whether a record consistent with the submitted details can be found in the available data, and what standing it has. Businesses that accept a passport as proof of identity usually want both, which is why the check pairs naturally with document OCR.
For customers who are not in the room
Non-resident onboarding, cross-border hiring and remittance flows share a problem. The customer cannot present the document in person and may hold no local address proof. A passport is often the only anchor identity record available.
Structured fields your flow can act on
The response returns the available applicant, application and status details in a consistent structure. A mismatch can route to a correction step and a clean match can pass through. The fields present differ by data source and by the individual record.
Consent first, and use kept to the purpose
A customer onboarding remotely is often handing over the only identity document they hold, and passport details are sensitive personal data. Capture consent before the request, and use the response for the stated purpose only. Keep it no longer than that purpose needs, and keep every check attributable to the person who ran it.
How a check runs
Take the file number and consent
Read the file number and date of birth from the document itself. Capture informed consent for the check, together with the purpose you are running it for.
Pre-fill from the document image
Trim whitespace and standardize letter case before you submit. Where you are capturing the document image anyway, reading the printed fields first and pre-filling the form removes most of the typing errors that cause avoidable failures.
Send the passport details
Submit the details through the API. The request is processed against the available passport records under your service contract.
Read the applicant and status fields
The available applicant, application-type, date and status details come back as structured fields your onboarding logic can act on. Which of them are present varies by data source and by the individual record.
Pass, correct, or review
Pass a matching record through, and send a details mismatch back for correction while the customer is still in the flow. Route a no-record result to manual review instead of an automatic decline.
Questions
- What is a passport verification API?
- An interface that checks submitted passport details against the available passport record from inside your own application, instead of reviewing each document by hand. The available applicant and status information comes back as structured fields.
- Which number do I need, the file number or the booklet number?
- The file number recorded against the passport application, together with the applicant's date of birth. Customers often reach for the booklet number instead. Show them where the file number appears on the document, and on the acknowledgment issued when the application was made.
- What information sits in a passport verification response?
- Depending on the available record, the response can carry the applicant's name and date of birth. It can also carry the application type, the application date and the current status of the record. Available fields vary with the data source and with the record.
- Does this confirm the physical passport booklet is genuine?
- No. The check reports whether a record consistent with the submitted details can be found in the available data. Where your process requires inspection of the physical document, or a face comparison between the document photograph and the person presenting it, those stay separate steps.
- Can I use passport verification for non-resident onboarding?
- Yes, and that is one of the more common uses. Where a customer is overseas and cannot produce a local address document, the passport is often the anchor identity record the rest of the file rests on. The same consent and authorized-use requirements apply.
- What happens when no passport record is found?
- Treat it as a prompt to look again. A no-record result can follow from a mistyped file number, a record that is not currently available, or a very recent application. Route it to manual review and give the customer a way to supply an alternative document.
Catalog entry last updated .