Premium receipts sit apart from policy status in LIC's own online servicing material, and that split matters for a My LIC export or API build. A finance team may only need receipt reconciliation. A CRM migration may need status, nominee and address fields. A lending workflow may need policy loan signals.
OpenBanking Studio builds the authorized interface layer for that exact mix: the client names My LIC and the records they need, and we turn the consented surfaces into a usable API, source package and documentation.
The access path for LIC policy records
The practical route is authorized interface integration against the My LIC and LIC customer-servicing flows the policyholder is allowed to use. LIC's portal pages name policy status, online premium payment, online loan request, NEFT registration, address change and bonus information as customer services. We model those surfaces as separate resources rather than scraping one combined dashboard.
| Route | Reachable records | Effort and durability | Studio setup |
|---|---|---|---|
| Consented My LIC / customer portal protocol mapping | Policy status, premium payment state, receipts, loan request context, NEFT registration and profile service events. | Best fit for live operational sync. We version request shapes and token or cookie handling during the build. | We prepare the auth-flow report, request contract, retry policy and audit log for each consented account path. |
| e-Insurance Account record mapping | Repository-held policy list, status, commencement, maturity or expiry, nomination, assignment, endorsement, address data and policy bond copies where present. | Useful when the policyholder has repository records that need to sit beside My LIC activity. | We normalize eIA fields into the same policy object while keeping source provenance in every response. |
| Native receipt and statement export handling | Online payment receipts and transaction-status downloads, including renewal premium, advance premium and loan payment types. | Good for backfill and audit packs. Less suitable as the only route for current status. | We build parsers, checksum checks and duplicate detection so receipt archives can seed the API history. |
| Account Aggregator consent where available in the workflow | Insurance information shared through RBI's AA ecosystem when the relevant insurer or repository participates as a Financial Information Provider. | Strong consent semantics, but coverage depends on the actual participant path used in the project. | We map consent purpose, expiry, revocation and FI data envelopes into the OpenAPI contract. |
For My LIC, we usually start with the policyholder-facing LIC service flows because those are where premium receipts, loans and address changes meet the live account. AA or eIA sources are added when they are part of the same consented record trail.
Policy fields worth turning into endpoints
| Data domain | Origin inside the LIC experience | Granularity | Integrator use |
|---|---|---|---|
| Policy status | LIC Customer Portal policy-status service; mirrored into My LIC account servicing. | One record per policy, with status and servicing flags confirmed during build. | CRM enrichment, renewal workflows and policy-lifecycle dashboards. |
| Premium receipts | LIC's Online Payment Receipts area, described under My App → Basic Services. | Receipt per payment event, with transaction date and payment type. | Accounting reconciliation, tax packs and customer-support evidence. |
| Loan servicing | Portal services for online loan request plus loan interest or repayment receipt flows. | Policy-linked loan event and payment status. | Credit assessment, repayment reminders and exception monitoring. |
| NEFT and bank servicing | NEFT registration and bank-detail update surfaces in the customer service path. | Account-level registration state, not raw bank credentials. | Payout readiness checks and servicing-case triage. |
| Bonus and fund changes | Bonus information and, where available, ULIP fund switch services. | Policy-level value or instruction state. | Portfolio reporting and advisor review screens. |
| eIA repository record | IRDAI insurance repository account, when the policy has been credited to an e-Insurance Account. | Policy list, status, nomination, assignment, endorsement, address and bond document reference. | Unified insurance vaults and cross-insurer household views. |
India consent and insurance-data controls
Insurance policy servicing in this market sits under the Insurance Regulatory and Development Authority of India for insurers and insurance repositories. IRDAI describes an e-Insurance Account as a repository account where a policyholder's insurance portfolio can be held digitally, including policy status, commencement, maturity or expiry, nomination, assignment, endorsement, address details and policy bond access.
The RBI Account Aggregator framework supplies a consent-based route for financial information sharing where the relevant institution participates, and public government material names insurance companies and insurance repositories among eligible Financial Information Providers. For a My LIC project, the dependable basis is still the policyholder's or enterprise customer's consented access to the records in scope. We keep consent purpose, expiry, revocation, data minimization and audit logs in the integration design.
No bypass language belongs here. The work is documented, authorized or user-consented interface integration for interoperability.
Build package for a My LIC connector
- OpenAPI contract for policy status, premium receipts, loan events, NEFT registration state and eIA-derived policy records.
- Runnable source in Python or Node.js for consented session handling, receipt retrieval, policy-status sync and backfill from exported receipt files.
- Auth-flow and protocol notes covering token or cookie lifetime, consent evidence, device/session boundaries and error cases confirmed during implementation.
- Automated tests using fixtures for paid premium receipts, lapsed or revived policy states, loan-payment events and duplicate receipt imports.
- Interface documentation for field naming, retention rules, masked bank-service fields and source provenance per returned object.
Source-code delivery starts from $300 and is paid after delivery once you are satisfied; hosted API access is also available on a pay-per-call basis with no upfront fee. A normal My LIC build takes 1–2 weeks. Send the target records and destination system through the contact page.
Example policy receipt contract
This sketch shows the kind of app-specific API surface we confirm during the build. Field names are final only after live protocol mapping and fixture tests.
GET /v1/my-lic/policies/{policyNumber}/premium-receipts?from=2026-04-01&to=2026-07-09
Authorization: Bearer <consented-session-token>
200 OK
{
"policy_number": "masked-or-tokenized",
"holder_ref": "obs-customer-7612",
"receipts": [
{
"receipt_id": "lic-rct-2026-06-14-001",
"payment_type": "renewal_premium",
"transaction_date": "2026-06-14",
"receipt_source": "online_payment_receipts",
"amount": {"currency": "INR", "value": "confirmed_during_build"},
"email_delivery_seen": true,
"policy_status_after_payment": "confirmed_during_build"
}
],
"sync": {
"source": "my_lic_customer_service_flow",
"consent_expires_at": "2026-08-08T09:30:00Z",
"next_check_after": "2026-07-10T02:00:00Z"
}
}Engineering notes from the LIC surface
Receipt handling needs its own idempotency rule. LIC material says receipts may be printed online, emailed, retrieved by transaction status, or sent after bank confirmation when a debit succeeds but an error page appears. We treat those as one payment fact with several evidence paths, so a retry does not create duplicate premiums.
Policy servicing and repository records are not the same object. We keep a source tag on every policy attribute: My LIC account flow, LIC Customer Portal surface, receipt archive or eIA repository. That lets a downstream system show why a maturity date came from a policy bond while a payment receipt came from the mobile servicing path.
Some LIC services are event-shaped rather than balance-shaped. NEFT registration, address change and ULIP fund switch are handled as status transitions with timestamps and audit notes, not as free-text profile dumps.
Interface evidence to capture
The app store screenshots supplied for this page are useful for navigation labels and user-journey framing, but endpoint contracts still come from authorized traffic capture and consented account testing.
Research trail for this page
Checked on 2026-07-09: the Google Play listing for My LIC, LIC's policy status and customer portal services, LIC's premium receipt and payment-channel guidance, and IRDAI's insurance repository and e-Insurance Account material. OpenBanking Studio integration desk notes, 9 July 2026.
Adjacent insurance apps and portals
LIC Digital is LIC's older customer app family and matters when historic servicing flows still point users there.
HDFC Life exposes policy servicing, renewal-premium payment and customer-account journeys that often need the same receipt-normalization pattern.
ICICI Prudential Life is a life-insurance account app where premium payment and policy statement export are common integration targets.
SBI Life Easy Access sits in the same Indian life-insurance servicing category, with policy and premium events that can be unified with LIC records.
Max Life customer servicing adds another insurer-specific policy vocabulary for multi-insurer dashboards.
Tata AIA Life Insurance is relevant for policyholder apps that combine service requests with premium and policy status records.
Bajaj Allianz Life brings insurer-servicing data that needs careful source labels when mixed with repository records.
Policybazaar is an insurance marketplace where purchased-policy and renewal flows may sit beside insurer-owned records.
CAMSRep and NSDL e-Insurance Account relate to repository-held policy portfolios rather than a single insurer app.
Questions My LIC integrators raise
Can the build separate premium receipts from policy status?
Yes. LIC describes online payment receipts as a Customer Portal surface under My App, Basic Services and Online Payment Receipts, while policy status is a separate portal service. We model those as separate resources so accounting teams can reconcile paid premiums without treating the whole policy record as a receipt.
How do e-Insurance Account records affect a My LIC integration?
IRDAI describes e-Insurance Accounts as repository-held portfolios that can include policy status, commencement details, maturity or expiry details, nomination, assignment, endorsement, address details and policy bonds. Where those records are part of the consented workflow, we map them separately from My LIC servicing events.
Can loan and NEFT servicing be included with policy exports?
Yes, when those surfaces are in scope for the consenting account. LIC's portal material lists online loan request, NEFT registration, address change, bonus information and fund switch services, so the integration can expose each as its own endpoint or scheduled export.
What should a My LIC project specify before build work starts?
Name the LIC records you want to consume, such as premium receipts, policy status, loan interest, NEFT registration or eIA fields. Access, consent records and retention limits are handled with you during the project rather than turned into a front-door checklist.
App profile
My LIC is listed for package com.lic.customer.superapp and is described as an online platform for LIC customers to manage policies, receive notifications for pending actions and purchase personalized policies in one place. The supplied icon and screenshots come from Google Play CDN assets. The app name and Life Insurance Corporation context are used here only to describe an interoperability target.