Payment notice and acknowledgement

The payer's notice that money has moved against an approved claim, and the provider's acknowledgement. The only exchange that carries actual money rather than an adjudicated figure.

The notice​

Sent on /v1/paymentnotice/request, workflow 30 initiated, 31 processed, 33 settled.

The bundle​

Elements​

1. Task​

NRCeS profile: Task.

2. PaymentNotice​

NRCeS profile: PaymentNotice.

3. PaymentReconciliation​

NRCeS profile: PaymentReconciliation.

The Organization entries are shaped as in the chapters that introduce them.

The acknowledgement​

Sent on /v1/paymentnotice/on_request, workflow 30 echoed; 17 under PMJAY.

The bundle​

Elements​

1. Task​

NRCeS profile: Task.

The Organization entries are shaped as in the chapters that introduce them.

Rules​

1. The notice​

A Task coded deliver in ndhm-task-codes whose input references the PaymentNotice. PaymentNotice.amount is the net that reaches the account. PaymentReconciliation carries the payment date, the UTR and one detail[] line per money type.

2. The arithmetic​

Net plus the deductions equals the adjudicated benefit, not the submitted amount. Run the check on every notice and flag a case that fails it.

3. The acknowledgement​

A Task coded status in financialtaskcode, completed, with an output paymentack and the claim number as a second output. It confirms receipt, not agreement.

4. Three notices​

30, 31 and 33, each with its own correlation id. The bank reference arrives on 33. Keep the path for the acknowledgement configurable per payer.

PMJAY​

The generic bundle above is what every payer takes, IRDAI-regulated insurers and TPAs included. PMJAY takes it with the changes and requirements below.

What changes in the bundle​

The notice​

Systems PMJAY binds differently​

The acknowledgement​

The PMJAY bundle has the same resources, elements and systems as the generic one.

What PMJAY specifies​

• Deduction lines use the scheme's own codes, such as RF, beside the Payment line.
• The notice names the claim under https://hcx.pmjay.gov.in/v1/preauthorization.
• Before 33 the UTR field can carry a scheme reference rather than a bank reference. Store it; reconcile against the bank only on 33.

What PMJAY requires​

• Acknowledge each notice on 17.
• Keep the UTR from 33; the shortfall window opens only once 33 is acknowledged.

Use cases, APIs and data elements​

C9 Send payment notice (payer)​

The money, on a new thread of its own, with the reconciliation itemised by type: approved, claimed, tds, servicetax, advance, recovered, penality. The bank's UTR rides on the settled notice.

Request headers

Workflow codes

Data elements

NRCeS profiles: PaymentReconciliation.

B7 Acknowledge payment notice (provider)​

The receipt for a payment notice, as a Task on this endpoint. The notice arrives on a new thread of its own; a generic payer takes the acknowledgement with the notice's 30 echoed, PMJAY with 17.

Request headers

Workflow codes

Data elements

NRCeS profiles: PaymentReconciliation.

D13 Acknowledge the payment notice (pmjay)​

Three notices may arrive: 30 when the transfer is initiated, 31 when the bank processes it, 33 when it settles with the UTR. The reconciliation splits the amount into what was paid and what was deducted as tax. Keep the UTR; it is the reference for any dispute.

Request headers

Workflow codes

Data elements

NRCeS profiles: PaymentReconciliation.