An order needs no payment after its total reaches zero

Read the status alongside the order it belongs to

Stripe's Checkout Session reference distinguishes payment_status values paid, unpaid and no_payment_required. It also separates payment_status from Session status: a complete Session can still have payment processing in progress. Read the exact fields on the actual Session and match it to the intended store order before interpreting a missing charge.

For this investigation, the question is whether a valid discount has left this order with nothing to collect. A no_payment_required label alone does not identify the discount, establish the final order total or prove that this is the intended purchase flow. Record the Session's mode and the integration's configured API version along with the totals. If the Session represents a different operation or does not match the order, investigate that mismatch before treating the goods as a completed zero-due purchase.

The cited Session reference was captured at API version 2026-08-26.preview. It establishes the distinction between the fields and values; it does not establish that every platform, connector or zero-total order uses exactly the same status mapping. Preserve the provider's actual value rather than changing it to the value you expected.

Trace the zero to the real discount and remaining charges

Start with the product lines and quantities actually accepted into the order. Record the product subtotal, the discount actually applied and the final amount due. Check the issued promotion's conditions against the order rather than assuming that a displayed percentage proves the whole order is free. The final total must also account for the recorded shipping and tax components without adding a component twice when it is already included.

For WooCommerce, the coupon-management guide distinguishes coupon types and restrictions, including product restrictions, usage limits and individual-use settings. Its free-shipping option requires the linked shipping-method setup. A product discount or a coupon's free-shipping setting by itself therefore does not establish that the order's selected shipping method costs nothing. Inspect the method and charge actually saved on this order.

Keep WooCommerce and Stripe observations attached to their own systems. A WooCommerce coupon configuration does not prove how a connector represented the discount in a Stripe Session. Compare the store's calculated result with the provider's recorded total. A remaining positive shipping charge, tax amount or other amount due prevents the product subtotal alone from establishing a zero-due order. If the two totals disagree, resolve the disagreement before classifying the order.

Record an order outcome without fabricating money movement

Once the intended order, applied discount and final zero amount agree, keep the original order record and Session reference as the evidence for why no funds were required. If no charge exists, do not create a charge identifier, state that a card was debited or describe a nonexistent amount as captured. A missing charge becomes a problem only when the verified transaction actually required a payment or another payment attempt remains unresolved.

Check how the installed connector records a completed zero-due checkout and hands the order to the next operating step. This is a specific integration question: does the actual record preserve the zero amount, the applied discount and the accepted order, or has it become stuck waiting for a charge that the confirmed flow did not require? Do not force a paid status merely to release that handoff.

Separate the absence of a payment requirement from permission to fulfill. The team still needs the completed order and its normal authorization, item, availability and delivery checks. A zero total does not show that those checks happened, and it does not justify repeating an order action already recorded.

Choose the next action from the disagreement that remains

If the records confirm a completed zero-due order, the useful next step is to reconcile its store handoff and customer-facing confirmation with that outcome. The confirmation should accurately describe the order, discount and amount due, without claiming a payment was taken when none was. If a positive amount remains, or the Session is incomplete or belongs to another flow, keep the order unresolved and identify that exact condition for the integration owner.

A Prism checkout consultation can discuss a zero-due order that the store mishandles. Summarize which records agree and which handoff remains open, then confirm scope, responsibilities, fees and terms before work. Keep customer records, private payment URLs and credentials out of the public form. Technical handling of a discount establishes neither provider eligibility for the business nor the correctness of its tax obligations.

Zero-due order check

Use one real order and its matching Session. Record the store and provider values separately where both exist. A zero product subtotal is insufficient: the final total, payment state and completed order handoff must each be supported. Leave absent evidence unknown rather than supplying a payment confirmation.

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.