Customer Portal & Mobile App — Host-to-Host Integration

Insurance • Self‑service policies, claims, bills, documents, and provider access (no SLA section)

Purpose of Host-to-Host

Core Data Objects

Example API Endpoints

GET /auth/sso/start
Initiate OIDC SSO (PKCE) when embedded in partner app
POST /auth/token/refresh
Refresh short‑lived tokens; rotate keys
GET /customer/policies
List policies & renewal info scoped to logged‑in user
GET /policies/{id}/documents
Download e‑policy, invoices, schedules
POST /claims
Create FNOL with photos, geotag, and contact
GET /claims/{id}/status
Timeline of tasks and settlement progress
POST /payments/initiate
Pay invoice (auto‑debit/card/VA); return redirect/OTP
POST /payments/notify
Bank/PG callback for payment result
GET /providers/eligibility
Check benefit eligibility at selected provider
POST /support/tickets
Open service ticket with attachments

Sample FNOL Request

POST /claims
{
  "policyNo":"POL-2025-009812",
  "type":"MOTOR",
  "lossDate":"2025-08-12T10:22:00+07:00",
  "location":{"lat":-6.200, "lng":106.816},
  "photos":["base64:image1","base64:image2"]
}

Reference Flows

SSO & Device Binding
  • Partner app launches /auth/sso/start (OIDC + PKCE)
  • Consent captured; device bound to user
  • Short‑lived JWT returned; refresh via /auth/token/refresh
Digital Policy & e‑Documents
  • User views policy list → selects policy
  • Downloads e‑policy/CoC/invoice with access logs
  • Optional watermarks + anti‑sharing tokens
Start a Claim
  • User posts FNOL with photos & geotag
  • System validates coverage & opens claim
  • Push notification confirms claim number
Pay a Bill
  • User chooses method → /payments/initiate
  • Bank/PG handles OTP → /payments/notify
  • Receipt & policy status updated instantly
Provider Eligibility (Health)
  • User selects provider → /providers/eligibility
  • Result shows coverage, copay, limits
  • Show digital member card for cashless access

Security & Controls

Monitoring & Audit

What You Get