Skip to content
PPAI-ETMSDeveloper Portal

Land Transportation Franchising and Regulatory Board

PPAI-ETMS: the electronic transmission & monitoring system for Passenger Personal Accident Insurance

PPAI-ETMS is LTFRB's central registry and electronic verification infrastructure for Passenger Personal Accident Insurance (PPAI) covering public utility and for-hire vehicles across all 18 regions. Accredited insurers, pools and management companies transmit certificates of cover electronically, from their own systems, via a single machine API; LTFRB gets searchable, near-real-time visibility into what is covered.

Start integrating API reference

Who must transmit

Any organization accredited by LTFRB to issue PPAI coverage is responsible for transmitting it electronically, via the machine API, from its own systems:

Insurance companies

Issue PPAI certificates directly, or as a pool member. Always the “issuing insurer” of record.

Accredited pools

A pool has a lead insurer and member insurers. The lead (or an assigned management company) may transmit on a member's behalf. Not used at launch, but supported by the platform.

Management companies

Assigned by a pool to transmit and manage PPAI records for its members, without being an insurer itself.

Launch insurers: PAMI, CENTERSTAR, SCCI.

How insurers integrate

There is exactly one way to transmit PPAI certificates: the machine API, called directly from your own systems. There is no insurer web portal, no manual entry form, and no bulk file upload — every certificate, amendment and cancellation goes through the same signed, auditable API call.

One machine API

OAuth2 client-credentials + HMAC-SHA256 request signing on every call to /api/v1. See the integration guide for the exact auth flow and signing algorithm, with working code samples in five languages.

Read the integration guide

Credentials issued by LTFRB

API credentials are not self-service. Your organization requests them from LTFRB, LTFRB issues (and can rotate or revoke) them from the admin portal, and delivers them to you securely.

How to request credentials

Sandbox before production

Test your integration end-to-end against the staging environment first — same API, isolated data, clearly watermarked — before requesting production credentials.

Sandbox onboarding

Transmission flow

Every API call funnels through the same pipeline, so behavior is identical and predictable for every certificate.

  1. 1

    Insurance issuance

    An accredited insurer, pool lead, or management company issues a PPAI certificate of cover.

  2. 2

    Electronic transmission

    The certificate is sent to LTFRB via the machine API, signed with your API credentials — never on paper, and with no manual or bulk-file channel.

  3. 3

    Validation

    PPAI-ETMS checks required fields, formats, transmit authority, and cross-references LTFRB/LTO vehicle data (levels L1-L4).

  4. 4

    Registration

    Valid transmissions are registered with an LTFRB reference; flagged ones are registered too, with a visible warning for review.

  5. 5

    LTFRB visibility

    LTFRB staff can search the record instantly by any of the four vehicle identifiers, policy number, or COC number.

Status glossary

PPAI-ETMS tracks two independent statuses: a transmission status (what happened to the submission) and a coverage status (whether the vehicle is currently covered, derived at read time).

Transmission status

  • RECEIVEDAccepted into the pipeline; validation has not finished yet.
  • VALIDATINGL1-L4 checks are running.
  • ACCEPTEDPassed all checks and was registered with no open flags.
  • FLAGGEDRegistered, but a vehicle-mismatch or identifier-conflict flag is open for LTFRB review.
  • REJECTEDFailed L1-L3 validation, is a duplicate/already-registered submission, or the vehicle already has in-force coverage with another insurer. Nothing was written to the registry.

Coverage status

  • ACTIVEToday is within the coverage window and it is not expiring soon.
  • UPCOMINGCoverage has not started yet (today is before the effective date).
  • EXPIRINGWithin the configurable expiring window (default 30 days) of the expiration date.
  • EXPIREDToday is after the expiration date.
  • CANCELLEDThe insurer cancelled the certificate. Nothing is deleted — the record remains for audit.
  • SUPERSEDEDAn older version of a record that has since been amended.

About "ACCEPTED". ACCEPTED means the PPAI record was accepted as an electronic transmission to LTFRB. It does not constitute an LTFRB guarantee of the legal validity of the underlying insurance policy. This disclaimer appears on every acknowledgment.

Ready to integrate?

Read the integration guide for the auth flow and signing algorithm, then request sandbox credentials from LTFRB to start testing.

Integration guide Sandbox onboarding