"Stored cards in a wrap shop: scope approval is not payment consent"
"Source","https://bluefinchadvisors.com/blog/wrap-shop-stored-card-change-order-consent"
"Basis","This planning scenario uses the values entered. It is not an industry benchmark or a quote."

"Inputs","Value","Unit"
"Original approved project total","5600","currency"
"Newly approved scope changes","450","currency"
"Payments already applied","2800","currency"
"Documented remaining charge permission","2500","currency"

"Results","Value","Unit"
"Revised unpaid job balance","3250","currency"
"Amount beyond documented permission","750","currency"
"Documented remaining permission","2500","currency"

"Calculation detail","Value","Unit"
"Approved project after changes","6050","currency"
"Prior payments","2800","currency"

"Assumptions"
"Starting values are examples, not market benchmarks or payment quotes."
"Use one currency and a consistent before-tax basis. Work out taxes and program-specific adjustments separately."

"Result notes"
"No result authorizes a charge or validates consent wording."
"A saved token, issuer approval, or approved scope change does not replace appropriate permission for the specific payment."

"Sources"
"Stripe: consent for saving and reusing payment methods","https://docs.stripe.com/payments/save-and-reuse"
"PCI SSC: verification codes cannot be stored after authorization","https://www.pcisecuritystandards.org/faqs/1280/"
"Mastercard: merchant surcharge rules and debit exclusions","https://www.mastercard.us/en-us/business/overview/support/merchant-surcharge-rules.html"
"Stripe: separate authorization and capture","https://docs.stripe.com/payments/place-a-hold-on-a-payment-method"