Skip to main content
PATCH
Update a payment

Authorizations

api-key
string
header
required

Headers

Melio-Entity-Id
string
required

Entity the request operates on — an entity id (ent_<uuid>) or me (the partner's sole entity).

Path Parameters

paymentId
string
required

Body

application/json

Fields that can be changed on a payment before it begins processing. All fields are optional; only supplied fields are updated.

amount
integer

Minor units (cents). Amount changes may be rejected (400) when the partner is not configured to allow them or when the payment spans multiple bills.

deductionDate
string<date>

The debit/schedule date

deliveryPreference
enum<string>

See CreatePaymentRequest.deliveryPreference. The preference's rail must match the payment's receiving account; fast variants remain subject to the per-payment eligibility check and are rejected with 400 when ineligible.

Available options:
standard-ach,
same-day-ach,
rtp,
standard-check,
express-check,
overnight-check,
domestic-wire,
instant-domestic-wire,
virtual-card,
instant-virtual-card
noteToSelf
string

Payer-private memo, never shown to the recipient

noteToRecipient
string

Note shown to the payment recipient

externalId
string

Your own unique identifier for the resource. Unique per partner per resource type (reusing one returns 409 DUPLICATE_EXTERNAL_ID). Distinct from the Idempotency-Key header, which dedupes the request rather than identifying the resource.

Maximum string length: 255
Pattern: ^[A-Za-z0-9_-]+$
metadata
object

Free-form string key/value pairs stored and returned verbatim, never interpreted by Melio. Up to 50 keys; each key 1 to 40 chars and may not contain square brackets ([ ], reserved for the metadata[key] filter); value ≤100 chars. Filterable via metadata[key].

Response

The updated payment.

fees
object[]
required

The fees charged for this payment, as recorded by the fees service. Includes both the originator-side and receiver-side fees; use chargeTo on each item to tell them apart. Always present — an empty array when no fees have been recorded yet (e.g. a freshly created payment).

id
string

Opaque payment id (pay_)

externalId
string

Your own unique identifier for the resource. Unique per partner per resource type (reusing one returns 409 DUPLICATE_EXTERNAL_ID). Distinct from the Idempotency-Key header, which dedupes the request rather than identifying the resource.

Maximum string length: 255
Pattern: ^[A-Za-z0-9_-]+$
amount
integer
currency
string
originatingAccountId
string

Internal originating account id (acct_)

receivingAccountId
string

External receiving account id (acct_)

deductionDate
string<date>
deliveryPreference
enum<string>

Effective delivery preference. Reflects the faster variant when one was applied, otherwise the receiving rail's normal-speed value.

Available options:
standard-ach,
same-day-ach,
rtp,
standard-check,
express-check,
overnight-check,
domestic-wire,
instant-domestic-wire,
virtual-card,
instant-virtual-card
deliveryDate
string<date>
status
enum<string>

While a payment is being reviewed it is reported as scheduled; there is no separate review status.

Available options:
scheduled,
in-progress,
completed,
failed,
canceled
noteToSelf
string

Payer-private memo, never shown to the recipient

noteToRecipient
string

Note shown to the payment recipient

metadata
object

Free-form string key/value pairs stored and returned verbatim, never interpreted by Melio. Up to 50 keys; each key 1 to 40 chars and may not contain square brackets ([ ], reserved for the metadata[key] filter); value ≤100 chars. Filterable via metadata[key].

createdAt
string<date-time>
updatedAt
string<date-time>