1M1money
crate::transaction::compliance::rfi::controller::openapi

POST /v1/customers/{customer_id}/rfi-cases

Changed on

Request

Path parameters

customer_idstring required

Customer ID

Headers

Idempotency-Keystring required

Required. Create a UUID for each new submission. Reuse it only when retrying the exact same request.

X-OM-Content-SHA256string nullable

Use this only for an HMAC-authenticated multipart FILE request. Set it to UNSIGNED-PAYLOAD when your HTTP client builds the multipart body internally. In this mode, HMAC does not cover the multipart body. Omit the header when you sign the complete serialized multipart body, and do not send it for JSON requests.

Request body

Example request

{
  "subject": {
    "id": "53f0273e-24c6-11f0-ad3e-02f7cd56c66d"
  }
}

Response

Information added to an existing case, or the exact request was already processed

case_idstring required

RFI case business ID.

case_classstring required

TRANSACTION or RECIPIENT; matches subject.type.

rfi_status'ACTION_REQUIRED' | 'PENDING_REVIEW' | 'ANSWERED' | 'REJECTED' | 'CLOSED' required

Overall customer-facing RFI case status.

created_atstring required
updated_atstring required

Example response

{
  "case_id": "TC-WXYZ-2345",
  "case_class": "TRANSACTION",
  "subject": {
    "type": "TRANSACTION",
    "id": "53f0273e-24c6-11f0-ad3e-02f7cd56c66d",
    "transaction_type": "FIAT_PAYOUT_THIRD_PARTY"
  },
  "requirements": [
    {
      "requirement_id": "RQ-WXYZ-2345",
      "submissions": [
        {
          "submission_id": "RS-WXYZ-2345",
          "document_type": "INVOICE",
          "file_name": "invoice.pdf"
        }
      ]
    }
  ]
}

Changes