Map ISO 20022 pain.002 Customer Payment Status Report codes to internal payment states

domain: iso20022.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. After submitting a pain.001 Customer Credit Transfer Initiation batch, expect an asynchronous pain.002 response reporting group-level and/or transaction-level status.
  2. Parse the Group Status applying to the whole file/batch separately from individual Transaction Status entries applying to specific instructions within it — a single pain.002 can carry both.
  3. Map the status-reason codes you receive (e.g., ACCP, ACSC, ACSP, PDNG, RJCT) to your internal payment lifecycle states, treating RJCT specially since it always carries a reason code.
  4. For rejections, read the associated status-reason information to drive customer-facing error messages and decide whether to auto-retry or require manual correction.
  5. Reconcile each pain.002 back to its originating pain.001 batch and instruction using the shared Original Message ID / Original End-to-End ID references rather than matching on amount alone.

Known gotchas

Related routes

Build and submit an ISO 20022 pain.001 customer credit transfer initiation file to a bank for batch payment origination
iso20022.org · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans