Should pacs.028 be sent after every payment?

Usually no. It works best as a targeted exception tool, not as blanket traffic.

What makes pacs.028 useful?

Clear timeout, escalation, and reconciliation rules around the original payment case.

pacs.028.001.05 — Kahilingan ng kalagayan ng bayad sa pagitan ng mga institusyong pinansyal pacs.028.001.05 — Kahilingan ng kalagayan ng bayad sa pagitan ng mga institusyong pinansyal

Field	Halaga
Pangalang ISO	FIToFIPaymentStatusRequestV05
Katayuan ng rehistrasyon	Registered
Taon	2019
Bersyon	5

Pangkalahatang-ideya Pangkalahatang-ideya

The pacs.028 message asks another institution for the status of an earlier payment. It is a targeted status query for delayed, unclear, or missing payment updates.

Last reviewed against primary sources on 23 March 2026. ISO 20022 catalogue reference date: 2025-02-27; source links are listed below.

Mga pangunahing elemento ng datos Mga pangunahing elemento ng datos

GrpHdr — Group Header with message identification and creation timestamp
TxInf — Transaction Information identifying the payment to enquire about
OrgnlGrpInf — Original Group Information referencing the source message
OrgnlInstrId — Original Instruction Identification from the source payment
OrgnlEndToEndId — Original End to End Identification for traceability

Konteksto ng negosyo Konteksto ng negosyo

Lets teams ask for status on a payment that is still in flight
Helps operations teams investigate delayed or missing payments
Works with pacs.002 when a passive status update is not enough
Fits exception handling and SLA monitoring

Key data elements and business context
Mga pangunahing elemento ng datos	Konteksto ng negosyo
GrpHdr — Group Header with message identification and creation timestamp	Lets teams ask for status on a payment that is still in flight
TxInf — Transaction Information identifying the payment to enquire about	Helps operations teams investigate delayed or missing payments
OrgnlGrpInf — Original Group Information referencing the source message	Works with pacs.002 when a passive status update is not enough
OrgnlInstrId — Original Instruction Identification from the source payment	Fits exception handling and SLA monitoring
OrgnlEndToEndId — Original End to End Identification for traceability	The sending institution asks the receiving institution for the status of one payment. The answer usually comes back in pacs.002.

Konteksto ng CBPR+ at schema Konteksto ng CBPR+ at schema

Replaces older manual status-enquiry patterns
Links the request to the original payment identifiers
UETR and gpi tracking can reduce how often teams need to send it
Often appears in automated payment-operations tooling

Daloy ng mensahe Daloy ng mensahe

The sending institution asks the receiving institution for the status of one payment. The answer usually comes back in pacs.002.

Primary references Primary references

Mga kaugnay na mensahe Mga kaugnay na mensahe

Message type	Description	Pangkalahatang-ideya
`pacs.002.001.12`	Ulat ng kalagayan ng pagbabayad sa pagitan ng mga institusyong pinansyal	The pacs.002 message reports the status of an earlier payment instruction. It tells another institution whether the payment was accepted, rejected, pending, or settled.
`pacs.008.001.13`	Credit transfer ng kliyente sa pagitan ng mga institusyong pinansyal	The pacs.008 message is the main customer credit-transfer instruction between banks. It carries party, amount, and remittance data.
`pacs.009.001.10`	Credit transfer sa pagitan ng mga institusyong pinansyal	The pacs.009 message moves funds between banks on their own behalf. It supports funding, cover payments, and liquidity management.