Send RFI

Send a Request for Information (RFI) for a payment or debit request. The delivery method (RTP or FedNow) is automatically determined based on the paymentId. The service validates the paymentId, confirms that the delivery method is either RTP or FedNow, validates the request body, and then sends the RFI request to the payment service. Validation rules:

  • At least one of MissingInformation or IncorrectInformation must be provided.
  • InitiatingPartyName is required
  • Status reason codes must be from the allowed list as per guideline standards of each clearing.
  • When code is NARR, additionalInfo is required
  • The payment delivery method must be RTP or FedNow (automatically detected from the payment).
  • Payment IO type must be 'IN' (incoming) or 'OUT' (outgoing)
  • For incoming CREDIT payments: delivery method must be RTP or FedNow.
  • For incoming DEBIT requests: delivery method must be RTP only.
  • For outgoing CREDIT Payments: payment status must be one of the following: PROCESSED, REVERSAL_ACCEPTED, REVERSAL_PARTIALLY_ACCEPTED, REVERSAL_REJECTED, RETURNED*
  • Outgoing DEBIT Requests are not allowed for RFI operations (same direction of RFI is not allowed)
  • Incorrect information codes must match the payment’s delivery method (RTP or FedNow).
SecurityoAuth2
Request
path Parameters
paymentId
required
string

Unique payment identifier. The delivery method (RTP or FedNow) is automatically determined from this payment.

Request Body schema: application/json
Array of objects (MissingStatusReasonInfo)

List of missing information items being requested. Allowed codes: MS01, NARR (same for both RTP and FedNow)

Array of objects (IncorrectStatusReasonInfo)

List of incorrect information items being requested. Allowed codes depend on payment delivery method:

  • RTP: IN01, IN04, IN06, IN15, IN19, IN38, IN39, MM20, MM21, NARR
  • FedNow: IN03, IN13, IN14, IN39, IN07, IN08, IN38, IN06, IN16, IN02, IN15, MM35, MM20, MM21, NARR, MM31, MM32, MM27, MM28, MM29, MM30, MM25, MM26 Codes are validated against the payment's delivery method.
initiatingPartyName
string <= 100 characters

Name of the party initiating the RFI request. This field is required.

Responses
200

Successfully processed request

400

Bad Request - Invalid input parameters or validation errors

401

You are not authorized to access the resource

403

Accessing the resource you were trying to reach is forbidden

404

The resource you were trying to reach is not found

405

Method Not Allowed - The HTTP method is not allowed for this endpoint

500

Internal server error

503

Service unavailable

default

Successfully processed request

post/v1/rfi/{paymentId}
Request samples
application/json
{
  • "missingInformation": [
    ],
  • "incorrectInformation": [
    ],
  • "initiatingPartyName": "ABC Corporation"
}
Response samples
application/json
{
  • "message": "Request for Information has been sent successfully",
  • "paymentId": "126791",
  • "deliveryMethod": "FEDNOW",
  • "timestamp": "2025-12-03T10:51:29.4687354+05:30"
}