Obtain the original authorization's PSP reference after the initial check-in or rental hold is created.
Send a technical adjustment request to the Adyen Modifications API using the original PSP reference, providing the new amount that reflects the updated estimated total.
Specify the adjustment type as 'authorisationAdjustment' (not a capture or cancel); the network-level behavior is an incremental auth or auth reversal depending on whether the amount increases or decreases.
Await the modification result asynchronously via webhook; the webhook contains whether the adjustment was accepted or refused by the issuer.
If the adjustment is refused (issuer does not support the operation for that card type), decide whether to re-authorize for the full estimated amount or proceed with the original authorization and capture within its limits.
At checkout, capture the final settled amount using a standard capture modification against the original (or adjusted) authorization.
Known gotchas
Not all issuers support authorization adjustments for all card brands — Visa and Mastercard have specific rules about which merchant category codes (MCCs) qualify for incremental or adjustment authorizations.
Authorization adjustments do not reset the authorization expiry clock; if the stay is long, you may still need to perform a fresh authorization before the original one expires.
The Adyen adjustment API is distinct from the Capture API — sending a capture with a higher amount than authorized is overcapture (a different operation) and may be rejected or result in a downgrade.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp