Insurance and takaful cards on a phone: how they work
On this page
When something goes wrong, a policyholder needs four things fast: the policy number, what is insured, the last day of cover and the number to ring. A policy card puts them on the phone already in their hand. You enter those facts and you keep them true. The policy document is still the contract, a claim is still made with the insurer or takaful operator, and the card is not proof of cover: it shows what you entered, and only your own signed-in team can scan it.
Who to ring first
The policy page opens with the assistance and claims lines, then the details the desk will ask for.
Picture someone whose car has stopped on the highway, or who is standing at a clinic's counter. They need a number to ring, and whoever answers will ask which policy it is.
native.cards puts both in a block on the policy page headed "If something happens". The first row is Call assistance, with what the line is for beside the number. Under it come Call claims, Email claims and Start a claim online, each shown only if you gave it. Then a line reads "Have this ready when you call:", followed by the policy number, the policyholder, what is insured, the vehicle registration and the date cover runs to. The policy number and the registration each have a copy button.
Example, with made-up details: Honda City 1.5 V. Comprehensive. WXY 1234. Covered until 31 March 2027. Excess RM 400 per claim. Call assistance: 24-hour roadside assistance.
We found no study of whether a card like this gets help to people sooner, so we make no such claim. The case for it is practical. The details are in one place, on the phone the person will use to make the call.
Ring each number from a mobile before you enter it, and note what the desk asks for. If it wants something the page does not list, your card and your call script disagree, and a customer will find that out at the roadside. If you leave the help lines blank, the page tells the policyholder that your business "hasn’t added an assistance or claims line to this policy. Use their contact details below."
The 2027 base plan
A standardised base medical plan is due in early 2027. Our reading: who to ring is then what differs.
Bank Negara Malaysia's page on the base medical and health insurance/takaful (MHIT) plan says it "is set to be available for purchase in early 2027". The plan is voluntary, and the page says it "offers a standardised package of benefits across participating insurers and takaful operators (ITOs)". Which companies will offer it is not yet known: "The list of participating ITOs will be announced in due course."
One reading of that, which is ours and not the Bank's: when the benefits read the same from one company to the next, what differs for the policyholder is practical. Whose line do I ring, and where do I start a claim? Those are the details a card holds.
Packages and policies
A package holds what its policies share. Each policy is then issued one at a time, with no import.
Policies belong to a card program of the kind Insurance credential. Inside it you set up packages, then issue policies under them.
A package holds what its policies share: a Name, the Insurer or takaful operator, the Cover in words, Where it applies, a link to the Package documents, and the help lines. The form calls those "The numbers a policyholder needs at the roadside or the clinic, one tap away on their policy": an Assistance phone, What the line is for, a Claims phone, a Claims email and a Claims page.
A policy holds what is one person's: the Policyholder, Who or what is insured, the Cover type, a Vehicle registration "Only for a vehicle policy", the Excess, and a link to the Policy document. The policy number is your own if you choose Use my own. Period of cover takes a start date and 6 months, 1 year or Until a date, so every policy has a last day.
Three things to know before you start:
- Policies are issued one at a time, by an owner or admin, to a person who has joined your program with an email address and a 6-digit code. There is no import, and nothing links native.cards to a policy system.
- The Cover box is read by the policyholder. Its own prompt says: "What is covered, in plain words. The policy document remains the full terms." With the documents linked, the page adds under it: "This is a summary. The documents hold the full terms, limits and exclusions."
- native.cards sells no policy and collects no premium or contribution. It holds no claim form and no claim status. Make a claim leads to your own claims phone, email or web page.
Keeping the card true
The page reads your entry, not the insurer's system, so renewals and cover that stops early are yours to enter.
- Cover active, with “Covered until” a date
- Final 30 days: a countdown, Ask to renew
- Two weeks before the end: one email
- After the last day: “Cover ended”
The page shows Cover active and "Covered until" with the date, for as long as the dates you entered say so. It reads your entry, not the insurer's system. That makes three moments yours to manage.
The last day. In the final 30 days the page stops saying Cover active and counts down instead, for example "Ends in 12 days". It offers Ask to renew, which opens an email or a call to the contact you gave. The policyholder is emailed once in the two weeks before the end. Your overview lists these policies under Ending soon. After the last day, in the form's words, "The policy shows as expired". The page then reads "Cover ended" and offers Ask about renewing.
A renewal. Open the policy, choose Change details and move the Last day, with 6 months longer or 1 year longer if that suits. To renew several at once, tick them and choose New last day. The policy keeps its number and its history.
Cover that stops early. A policy cancelled in mid-term, or one that lapses because it was not paid for, is the case to plan for. Nothing in native.cards knows about it. The page goes on saying Cover active until someone presses Suspend or Cancel policy. Suspending shows the policyholder "Paused by" and your name, and Reinstate undoes it. Cancelling is permanent and emails them.
By kind of issuer
Insurers, agencies and employers each have a question to settle first, and all should ask compliance.
| Who issues the card | What to settle before the first one |
|---|---|
| An insurer or a takaful operator | Who keeps the cards in step with your policy system, since nothing does it for you. The page's labels read Policy number and Policyholder and cannot be reworded today, which matters if you speak of a certificate and a participant. |
| An agency | The card goes out in your name, with the company you enter as Insurer or takaful operator named beneath. Ask that company whether it agrees to this, and to its cover being summarised by you. You hold a copy; the insurer holds the record. Decide what you do when a client moves to another agent. |
| An employer's benefits desk | On a group policy the employer and the people covered are different parties. The form asks for a Policyholder and for Who or what is insured on every card, so decide what goes in each. Cancel a leaver's card the day they leave. |
Whichever you are, ask your own compliance people what a summary of cover may and may not say. This Article is general information, not advice.
Who can open it
The page is private and only your signed-in team can scan its code. It shows your entry and is not proof of cover.
The policy page is private. The policyholder opens it signed in with their email address, and there is no public page for a stranger to scan.
The page does offer a code, under "Show that you’re covered". Its note says who it is for: your "staff can scan your code to check your cover is current. Nothing is used by showing it." Your own signed-in team reads it with the dashboard's Scanner. A hospital, a workshop or a police officer cannot, so do not tell policyholders that the card proves their cover. That stays the job of the documents the insurer issues.
Where you have Apple Wallet or Google Wallet turned on, the policyholder can add the policy to their Wallet. That card carries the short facts your design includes, such as the policy number, what is insured, the last day and the assistance number.
Everything typed into a policy is personal data about a named person. Keep health details out of the free-text boxes, and see Your members' personal data: what the law expects.
Do this next
Before the first policy, name who keeps the cards true
Write two names on one line: who suspends or cancels a card on the day cover stops early, and who moves the last day when a policy is renewed. Give each a deputy. Check that all of them are owners or admins on your native.cards account, because nobody else can make those changes.
If you cannot fill in that line, wait. A card that says Cover active after the cover has gone is worse than no card.
Sources 1
Written by native.cards, . Found a mistake? The publishing policy says how to tell us.