Payment controls and records

A discounted total falls below the minimum charge

A positive balance still requires a payment, and that payment can fall below the minimum for the provider, currency arrangement and method. A genuinely zero-due order has a different payment requirement. Compare the final amount actually submitted with the applicable documented minimum; do not compare only the product price or assume one threshold covers all currencies. For Stripe Checkout, read the actual payment_status as well as the amount: no_payment_required is distinct from paid and unpaid. A small failed payment does not become a no-payment order merely because collecting it is inconvenient.

For: A research-only merchant investigating a small positive checkout amount rejected after a discount.

Updated 2026-10-01

Establish what remained after the discount

Open the real order calculation and the matching payment request. Record the final amount due after the discount and every remaining total component, including shipping or tax where present. A fully discounted product line does not establish that the whole order is zero. Keep the displayed amount and the submitted amount separate until their currencies and units agree.

Stripe documents API amounts in currency minor units, including zero-decimal currencies and specific exceptions. Do not apply a universal multiply-by-one-hundred rule to interpret the request. If the integration submitted an incorrectly scaled amount, resolve that amount mismatch before concluding that the intended price is below the minimum. The minimum comparison must use the amount the provider actually received, interpreted under the documented currency rules.

Compare on the provider’s minimum basis

Stripe’s supported-currencies documentation makes the minimum dependent on settlement currency and currency conversion, with payment-method exceptions. The currency displayed to the buyer is therefore only part of the comparison. Record the presentment currency, the settlement currency used for the payment, and the applicable minimum entry and conversion condition from the provider’s documentation.

A numerical comparison is meaningful only when both sides use the same basis. If conversion is involved and the records do not establish the relevant converted amount or applicable rule, mark the comparison unresolved. Do not substitute a remembered exchange rate or a minimum from another settlement currency. Likewise, record a method exception only when its documented scope includes this payment method.

A matching provider error can support a minimum-charge diagnosis. A generic checkout failure alone cannot. If the amount satisfies the applicable minimum but the attempt still fails, the minimum is not a sufficient explanation; preserve the returned error and investigate that result. For another provider, use that provider’s documentation rather than importing Stripe’s limits.

Separate a zero-due result from a failed positive charge

The cited Stripe Checkout Session reference distinguishes payment_status values paid, unpaid and no_payment_required. It also separates payment_status from the Session’s own status: a complete Session can still have payment processing in progress. A completion screen or a complete Session is therefore insufficient evidence that the charge succeeded or that no payment was needed.

For this investigation, compare the matching Session’s amount and payment_status with the order’s genuine final balance. A zero-due order and a corresponding no-payment result answer a different question from a positive amount rejected under a minimum. Do not manually relabel the latter as paid or no_payment_required to make the store proceed.

These field distinctions come from the captured 2026-08-26.preview API reference. Identify the actual integration and API version before assuming a plugin exposes or handles the same fields. The status is evidence about that Session, not a universal instruction to release an order.

Choose the next action from the comparison

If the positive amount is correctly calculated and below the applicable minimum, the merchant has an offer-design decision to resolve through its approved setup. Preserve the issued discount and the failed attempt while deciding how the promotion should work. Do not add an undisclosed fee, split payments to evade a limit, or silently treat an outstanding balance as waived. A genuine decision to change an offer must be reflected accurately in its terms and order total.

If a settlement basis or method exception is unknown, the useful provider question names the amount, currencies, method and exact unresolved rule. If the submitted amount is wrong, the useful checkout question identifies the calculation or currency representation that diverged. This gives the responsible person a specific gap to resolve without making another charge merely to see what happens.

For a Prism checkout-review consultation, describe the website, research-only products, observed minimum-charge message and comparison you need help organizing. Scope, responsibilities, fees and terms are discussed before work. The inquiry receives email follow-up; it does not book an appointment, purchase implementation or submit a processing application.

Minimum-charge decision record

Complete this for one genuine discounted order and its matching attempt. Keep amounts with their currencies and units. The comparison is unresolved if the applicable minimum basis is missing; a positive amount below a minimum is not a zero-due result. Keep private identifiers in your own records.

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.

Minimum-charge decision record. The last column is for temporary notes.
Decision inputRecord to consultHow to interpret itYour finding
Final amount dueFinal order calculation, discount record and submitted payment amount.Establish whether the full order is zero or positive; separate an amount mismatch from a minimum failure.
Presentment currency and unitsCurrency on the request and the provider’s amount-unit documentation.Interpret the actual request using that currency’s documented units and exceptions.
Documented minimum basisProvider minimum entry, settlement currency and conversion conditions for this arrangement.Compare on the documented basis; leave the result unresolved if conversion or settlement facts are missing.
Payment method exceptionMethod on this attempt and the exact scope of any documented exception.An exception for a different method does not change this comparison.
Reported provider resultMatching error or payment result and its timestamp.Record whether the result actually identifies a minimum problem rather than assuming every failure does.
Checkout payment requirementMatching Session amount, payment_status and integration version, if using Stripe Checkout.Distinguish no_payment_required from paid or unpaid; Session completion alone does not settle payment.
Merchant decision and ownerActual offer terms, unresolved comparison and person authorized to decide the next change.Choose an amount correction, rule clarification or offer review without concealing or evading the limit.

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.

Limits

  • Stripe currency and minimum rules describe Stripe. They do not establish another provider’s limits or eligibility for a research-only business.
  • The Checkout status discussion is scoped to the cited preview-version reference; no live merchant configuration or transaction has been inspected here.
  • Do not put card numbers, authentication codes, private payment links, API secrets, bank details or customer records in this worksheet or a public consultation request.

Sources

  • Stripe supported currencies — checked 2026-09-29. API amount units have currency-specific exceptions. Minimum charges depend on settlement currency and conversion, with documented payment-method exceptions; no universal threshold is inferred.
  • Checkout Session object — checked 2026-09-29. In the captured preview-version reference, payment_status distinguishes paid, unpaid and no_payment_required; a complete Session can still have payment processing in progress.
  • Prism solutions — checked 2026-09-21. Prism offers storefront review, processing preparation and help with provider website questions. Scope, fees and terms are discussed before work; the provider decides eligibility and account terms.
  • Prism contact — checked 2026-09-21. The form asks for the website, products and question, excludes card details, passwords and customer records, and receives email follow-up. A request is not an appointment, purchase or processing application.

Get help with checkout

Is this happening on your own store?