Skip to main content
POST
Send a status request reminder
This API is in preview and subject to change.

Overview

Chases a claim non-receipt (camt.027) that the beneficiary bank has not answered. The reminder goes out as a pacs.028 status request. Under the EPC SCT rulebook a camt.027 expects a camt.029 within 10 banking business days. After that you may push a status request as a reminder, provided the payment is still within 13 months of its debit date. The path parameter is the ID of the claim, not of a reminder. The response is the claim itself, with the new reminder added to claimNonReceiptDetails.reminders. Reminders are never returned as standalone entries by the search or list endpoints — read them through the claim they belong to. Do not create a second claim non-receipt for the same payment instead of sending a reminder. A payment can have only one pending outbound claim at a time; see Create investigation.

When you can send one

Banking business days follow the calendar of the payment’s debtor bank.
Rather than testing these yourself, read reminderEligibility on Get investigation. It returns eligible, a reason when it is false, and availableFrom with the first date a reminder becomes possible when the reason is TOO_EARLY. Search and list responses omit it.
reason and availableFrom are null when eligible is true.

After sending

The reminder is dispatched at the next SEPA Credit Transfer clearing cycle, and sentAt is set on it once it leaves. From then on:
  • It resolves when the beneficiary bank answers the claim with a camt.029 — a reminder is never resolved on its own.
  • It moves to REJECTED if the clearing system rejects the pacs.028, or if it cannot be dispatched.
  • A positive clearing acknowledgement updates delivery only. The reminder stays pending, because acknowledgement by the clearing system is not an answer from the beneficiary bank.
You can send a further reminder 5 banking business days after the last one, for as long as the claim stays pending and the payment is within the 13-month window.

Errors

Example error response

Path Parameters

id
integer<int64>
required

Claim non-receipt investigation ID

Response

Reminder sent; the parent claim non-receipt is returned with the reminder embedded

createdAt
string<date-time>
required

Timestamp when the investigation was created

createdBy
string
required

User or system that created the investigation

direction
enum<string>
required

Investigation direction (INBOUND or OUTBOUND)

Available options:
OUTBOUND,
INBOUND
id
integer<int64>
required

Investigation ID

messageId
string
required

Investigation message ID

schema
enum<string>
required

Message schema identifier

Available options:
SEPA,
INST
status
enum<string>
required

Current investigation status

Available options:
PENDING,
RESOLVED,
REJECTED
type
enum<string>
required

Investigation type

Available options:
CLAIM_NON_RECEIPT,
PAYMENT_STATUS_REQUEST
claimNonReceiptDetails
object | null

Claim non-receipt investigation details, present for CLAIM_NON_RECEIPT type

delivery
object | null

Investigation message delivery status information from CSM

referencedTransactionId
integer<int64> | null

Referenced transaction ID

reminderEligibility
object | null

Whether a pacs.028 reminder can be sent for this claim right now, and if not, why

resolution
object | null

Resolution details, present when the investigation has been resolved

statusHistory
object[] | null

Investigation status change history, included when retrieving a single investigation

transactionDetails
object | null

Original transaction details referenced by the investigation

updatedAt
string<date-time> | null

Timestamp when the investigation was last updated

Last modified on September 3, 2026