Payment Message

Overview

Payment Message is a structured electronic communication that carries a payment instruction, status, investigation request, return, recall, or related financial information between systems or institutions. Its schema defines required elements, identifiers, parties, amounts, currencies, dates, and status or reason data. The relationship with Payment Reason Code matters because one payment can appear as multiple requests, events, provider references, and ledger entries.

Its boundary with Payment Messaging Layer must remain explicit so related records do not collapse into one status. Operationally, its schema defines required elements, identifiers, parties, amounts, currencies, dates, and status or reason data; validation and business rules determine whether the receiver can accept and act on it. Important risks include malformed fields, duplicate delivery, incompatible versions, missing identifiers, ambiguous status, unauthorized alteration, and treating receipt as settlement. The record should retain message identifier, message type and version, sender, receiver, creation time, business references, payload hash, validation result, acknowledgements, and linked payment states.

Payment Message should remain distinct from Payment Messaging Layer, Payment Reason Code, and Payment State Version, because each can represent a different stage, record, control, or financial outcome. The message is evidence of communication, not proof that funds moved, settled, or became final.

Useful measures include acceptance rate, rejection rate, duplicate rate, end-to-end latency, unmatched-message count, and time to resolve exceptions. Tests should cover normal traffic, edge cases, partial failure, and downstream financial evidence.

Controls should validate schemas and business rules, authenticate the sender, preserve message integrity, apply idempotency, correlate replies, and maintain versioned mappings. Controls should preserve original payloads, correlation and causation identifiers, delivery attempts, validation results, consumer acknowledgements, and any replay or dead-letter action.