Actions206
- Accessory Actions
- Actual Content Actions
- Alternative Actions
- Appointment Actions
- Appointment Crew Actions
- Contact Actions
- Contact Person Actions
- Contract Actions
- Cost Actions
- Crew Actions
- Crew Availability Actions
- Crew Rate Actions
- Equipment Actions
- Equipment Assigned Serial Actions
- Equipment Sets Content Actions
- Extra Input Field Actions
- Factor Actions
- Factor Group Actions
- File Actions
- File Folder Actions
- Folder Actions
- Invitation Actions
- Invoice Actions
- Invoice Line Actions
- Leave Mutation Actions
- Leave Request Actions
- Leave Type Actions
- Ledger Code Actions
- Payment Actions
- Project Actions
- Project Crew Actions
- Project Equipment Actions
- Project Equipment Group Actions
- Project Function Actions
- Project Function Group Actions
- Project Request Actions
- Project Request Equipment Actions
- Project Type Actions
- Project Vehicle Actions
- Purchase Order Actions
- Purchase Order Cost Actions
- Purchase Order Global Cost Actions
- Quote Actions
- Rate Actions
- Rate Factor Actions
- Repair Actions
- Serial Number Actions
- Status Actions
- Stock Location Actions
- Stock Movement Actions
- Sub Rental Actions
- Sub Rental Equipment Actions
- Sub Rental Equipment Group Actions
- Subproject Actions
- Subtask Actions
- Supplier Actions
- Task Actions
- Task Assignment Actions
- Task Status Actions
- Tax Class Actions
- Time Registration Actions
- Time Registration Activity Actions
- Vehicle Actions
Payment → Update
AI-generatedSummary
Updates an existing Rentman payment by ID, sending only the fields you set (amount, date, remark) in the request body to /payments/{id}.
Inputs
- paymentId (required) — ID of the payment to update; used in the request URL /payments/{id}.
- updateFields — Collection of optional fields to change: Amount (number), Date (date/time), Remark (multi-line text). Only the fields you add are sent in the body.
- requestOptions — Node settings: batching (items per batch, default 50, and interval in ms, default 1000), ignore SSL issues, proxy URL, and timeout (default 10000 ms).
Output shape
The API response for the updated payment, returned as a single item. The source pack shows only the compiled stubs, so the exact response shape is not visible.
The HTTP method is not shown in the provided properties or source. The operation is declarative, so the request is built from routing definitions. If no update fields are added, the request body is empty.
Examples
Example 1: Correct the amount of a recorded payment
Set Payment ID to the payment's ID, then add Update Fields > Amount with the corrected value.
Example 2: Add a note and change the date on a payment
Set Payment ID, then add Update Fields > Date and Remark.