Create and manage an order in the Clover REST API including applying a tip adjustment after payment authorization
domain: docs.clover.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an OAuth access token for the merchant as described in the Clover OAuth flow, then POST to /v3/merchants/{mId}/orders to create a new order with line items
Add order line items by POSTing to /v3/merchants/{mId}/orders/{orderId}/line_items with the item details and applicable modifiers
Authorize a payment by using the Clover Payments API or integrated payment hardware; retain the paymentId from the authorization response
After the customer signs or approves, send a tip adjustment by PATCHing /v3/merchants/{mId}/payments/{paymentId} with the updated tipAmount to capture the final tip
Confirm the order state by GETing /v3/merchants/{mId}/orders/{orderId} and verifying that totalAmount, tipAmount, and paymentState reflect the completed transaction
Handle idempotency by storing the Clover-generated orderId on your side before any capture or tip adjustment to avoid duplicate submissions on retry
Known gotchas
Tip adjustments must be submitted before the payment batch closes; the window varies by merchant processor configuration
The tipAmount in a PATCH to a payment must be the absolute tip value, not an incremental addition on top of an existing tip
Modifying an order after a payment is captured may require voiding and re-creating the payment in some processor configurations
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?