---
title: "Update Expected Payment [deprecating Aug 2024]"
method: PATCH
path: "/expected_payments/{id} (legacy)"
---

# Update Expected Payment \[deprecating Aug 2024\]

`PATCH /expected_payments/{id} (legacy)`

## Request

- Base URL: `https://app.moderntreasury.com/api`
- URL: `https://app.moderntreasury.com/api/expected_payments/{id} (legacy)`
- Auth: HTTP basic

This is the legacy approach of updating Expected Payments, see the latest documentation here: https://docs.moderntreasury.com/platform/reference/create-expected-payment

## Request body

- object
  - `amount_upper_bound` integer
  - `amount_lower_bound` integer
  - `direction` string
  - `internal_account_id` string
  - `type` string
  - `currency` string
  - `date_upper_bound` string, date: Format is YYYY-MM-DD
  - `date_lower_bound` string, date: Format is YYYY-MM-DD
  - `description` string
  - `statement_descriptor` string
  - `metadata` string, json
  - `counterparty_id` string
  - `remittance_information` string

## Changes

- **2026-11-03** `e31c6638c72e`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/modern-treasury/apis/modern-treasury-api/changes/expected_payments/:id%20%28legacy%29/patch.md)

---

[API](https://skmtc.dev/modern-treasury/apis/modern-treasury-api.md) - [All operations](https://skmtc.dev/modern-treasury/apis/modern-treasury-api/llms.txt) - [OpenAPI document](https://skmtc.dev/modern-treasury/apis/modern-treasury-api/revisions/e31c6638c72e?raw)