A changed order costs more than the existing authorization

Preserve the original order beside the agreed revision

Retain the original items, delivery choice, total and currency. Record exactly what changed and how the revised total was calculated, with the revised item, shipping, discount and tax components as recorded by the store. Do not replace the original total so that the reason for the increase disappears.

Keep the customer’s agreement to the revised items, delivery terms and total in the authorized order or support system. A request for a different delivery option does not by itself document agreement to a price the customer has not seen. A staff edit is the merchant’s record of an action, not evidence that the customer approved it.

This agreement concerns what the merchant proposes to supply and charge. It does not enlarge the amount held by the card authorization or establish which payment operation the provider permits. Treat order approval and payment capability as two facts that both need evidence.

Compare the revision with the payment that actually exists

Use the payment reference attached to the original order to locate the current provider record. Retain the authorized amount, currency, state, any capture already made and the applicable capture deadline. If the record has expired, been canceled or already been captured, it no longer describes the simple case of increasing an untouched open authorization.

Compare the revised total with the authorized amount only when both use the same currency and amount representation. The difference is the increase in the order price; it is not automatically the amount to put into a second payment request. That depends on what happens to the original authorization and which collection path is supported.

If staff have already attempted an action after the revision, check its actual provider result before choosing another. An order note that says payment was requested is not a successful collection record. Preserve attempted, pending and completed actions separately so another operator does not act on an outdated total or payment state.

Confirm the capability at both provider and integration level

Stripe’s authorization-and-capture documentation says default capture takes the authorized amount. Capturing above that amount is documented only for certain eligible online card payments. That is a bounded capability, not a rule that changing an order total increases every authorization. It does not establish eligibility for this merchant, payment or gateway.

The decision needs a documented answer for the actual payment: whether a higher capture is available, what amount and deadline limits apply, and whether the installed integration supports that operation. Record the provider account, payment method, currency and gateway version relevant to that answer. General API documentation alone does not show that a store plugin exposes the same feature.

If a higher capture is unavailable or unconfirmed, ask the approved provider which supported action is required and what must happen to the original authorization. Identify whether any further customer participation is needed. Do not invent a second charge, cancellation sequence or limit workaround. The provider’s answer should describe a complete route that accounts for the original payment as well as the revised amount.

Authorize one collection plan and reconcile its outcome

Name the merchant owner allowed to approve the payment action and the operator permitted to perform it. Before action, the record should show the customer-approved revised total, current payment state, documented supported route and treatment of the original authorization. A blank capability or approval field means the increased amount has not yet been cleared for collection.

If a proposed plan captures the original amount first and collects something later, evaluate that exact plan before proceeding. Stripe says a smaller capture normally releases the remainder and most payments permit only one capture; retaining a remainder requires supported multicapture. A first capture is therefore not a neutral step that preserves every later choice. Do not use it simply to buy time while deciding how to collect more.

After the authorized operation, compare the actual amount collected and currency with the agreed revised total. Retain each provider reference and any still-open authorization separately. Only the confirmed payment result supports a paid status for the revised amount; an edited order total or a submitted request does not. If the attempt fails or remains unresolved, preserve that outcome and route it to the named owner before another action.

For a Prism checkout-review consultation, summarize the website, research-only products, platform and the gap between the agreed revision and authorized amount. Leave customer records, card details and payment credentials out of the public form. Any investigation or implementation scope, responsibilities, fees and terms are confirmed before work. Email follow-up does not book an appointment, purchase work or submit a processing application.

Revised-amount approval map

Complete this for one actual order revision. Store evidence references privately and use no card data or private payment links here. Order approval, payment capability and authority to act are separate checks; an unknown entry leaves the collection plan unresolved.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.