Know where every claim stands, without calling the payer.
Look up any claim's status, or get a webhook the moment adjudication changes. When a payer rejects or asks for follow-up, your billing team gets a plain-language reason and suggested fix, not a raw payer code.
$Claim paid · $420Remittance detail attachedStatus your billing team can read
Example result states, as returned by the API. Illustrative data.
Claim received by the payer and queued.
In adjudication with the payer.
Claim adjudicated: $420 paid, remittance detail attached.
Date of birth doesn't match the payer's record. Correct DOB and follow up with the payer.
What you get
Poll or subscribe
Call GET /v1/claims/:id on demand, or receive a webhook when the status changes.
Plain-language reasons
Rejection and follow-up codes come back with an explanation and a suggested fix your team can act on.
Remittance detail
Payment and remittance data linked to each claim, in the same standardized schema, so billing doesn't read raw remittance files.
One schema, every payer
The same status fields regardless of which payer adjudicates the claim.
Inside the EHR
Status lands where your billing team already works, through the Payerkart EHR adapter.
Logged and scoped
Every status request is recorded with who made it and when. Keys are scoped and revocable.
Payer codes, translated
Five common rejections, as the payer sends them and as your staff see them in Payerkart.
| Payer code | What the payer sends | What Payerkart shows staff | Suggested fix |
|---|---|---|---|
AAA 72Eligibility | Invalid or missing member ID | The payer doesn't recognise the member ID that was sent. | Re-check the card (prefixes and suffixes are often dropped), or re-scan it, then run eligibility again. |
AAA 71Eligibility | Birth date doesn't match payer records | The date of birth in the EHR doesn't match what the payer has on file. | Confirm the date of birth with the patient. Check you sent the patient's details, not the subscriber's. |
AAA 75Eligibility | Subscriber not found | The payer can't find anyone matching the name, ID and date of birth sent. | Check name spelling and payer selection. Try the subscriber's details if the patient is a dependent. |
CARC 27Claim | Expenses incurred after coverage terminated | The plan had ended before the date of service. | Re-verify eligibility for that date and ask the patient for current insurance before billing again. |
CARC 22Claim | Covered by another payer (coordination of benefits) | The payer thinks another plan should pay first. | Update primary and secondary coverage with the patient, then bill the primary plan. |
Codes from the X12 eligibility (AAA) and claim adjustment reason (CARC) code sets. Wording is a plain-English summary. Always check your payer's companion guide.
Claim status FAQ
Which claim statuses does Payerkart report?
Where a claim stands with the payer: submitted, in review or adjudication, paid, or denied, with remittance detail linked to the claim once it is paid.
How do we get notified when a claim status changes?
Poll the claim status endpoint, or subscribe to a webhook that fires when the payer's adjudication status changes.
What happens when a payer rejects a claim?
The payer's code is translated into a plain-language explanation and a suggested fix, for example that the date of birth is missing or doesn't match the payer's records.
Does Payerkart submit claims?
No. Payerkart tracks the status of claims you have already sent through your existing billing workflow. Its scope is eligibility verification and claim status tracking.
Stop chasing claim status by phone
Book a demo to walk through your workflow and get sandbox access. No payer contracts to negotiate before your first request.