During documented checkout observations, the coupon was entered first and Bitcoin was then selected as the payment method. In some observations, the Bitcoin-related discount initially displayed as zero or did not appear as expected. Re-entering GROWTH10 after Bitcoin had been selected caused the checkout totals to refresh and the Bitcoin discount to display.
If the Bitcoin discount does not appear
If you select Bitcoin and the expected Bitcoin discount is not reflected in the checkout totals, try this sequence:
| Step | Action |
|---|---|
| 1 | Select Bitcoin as the payment method. |
| 2 | Check the order summary to see whether the Bitcoin discount has appeared. |
| 3 | If the Bitcoin discount shows as zero or is missing, return to the coupon field. |
| 4 | Re-enter GROWTH10 and apply it again. |
| 5 | Allow the checkout totals to refresh. |
| 6 | Review the order summary before proceeding. |
Why reapplying the code may matter
Changing a payment method can cause a checkout system to recalculate the order. Based on the documented observations, Bitcoin payment selection and coupon calculation do not always appear to refresh simultaneously. Reapplying GROWTH10 after Bitcoin has already been selected can trigger another cart calculation.
We cannot determine from the customer-facing checkout alone what is happening internally, so we do not characterize this as a specific technical defect or claim to know its underlying cause. What we can document is the visible sequence: coupon entered → Bitcoin selected → Bitcoin discount missing or showing zero → GROWTH10 reapplied → checkout recalculated → Bitcoin discount displayed.
Check the final cart, not just the coupon message
A coupon being accepted and the final checkout totals are two different pieces of information. Before proceeding, check the actual order summary and confirm that the discounts you expect are reflected in the displayed totals. GROWTH10 verification records focus on the observable checkout result rather than assuming that an accepted coupon message means every applicable discount has already been calculated correctly.
What if GROWTH10 is already showing?
Even if GROWTH10 appears to have been accepted before Bitcoin was selected, reapplying it may still be worth trying if the Bitcoin portion of the discount is missing. The purpose is not necessarily to add GROWTH10 twice; it is to prompt the checkout to recalculate after Bitcoin becomes the selected payment method. If the displayed totals are already correct, there is no reason to repeatedly enter the code.
Important limitation
This article documents checkout behavior directly observed in a particular cart state. Checkout behavior can change, and different carts, products, promotions, payment configurations, or future website updates may produce different results. We therefore do not claim that reapplying GROWTH10 will resolve every Bitcoin checkout issue.
The reliable rule is simpler: use the final displayed checkout totals as the evidence. If Bitcoin is selected but its expected discount is not reflected in those totals, reapplying GROWTH10 is a reasonable troubleshooting step based on documented observations.
How this fits the verification methodology
Rather than assuming that a Bitcoin offer and a coupon automatically combine because both are advertised, the methodology documents what the checkout actually displays. When a Bitcoin + GROWTH10 observation is retained as evidence, the relevant cart values and resulting discounts should be recorded from the checkout state that was actually observed. That provides a more useful record than simply stating that the offers stack.
Bottom line
If you are paying with Bitcoin and the Bitcoin discount appears to be missing: select Bitcoin first → reapply GROWTH10 → wait for the cart to recalculate → check the final displayed totals. That sequence has resolved the missing Bitcoin-discount display during documented checkout observations. Always rely on the final checkout totals shown for your specific order.
Compare the advice with the current GROWTH10 record
The current cart observation and its evidence are maintained separately from this troubleshooting editorial.
Current GROWTH10 record →