Post Purchase Upsell Flow Skill 安全审计

46```47Payment captured48  └─ Upsell 1  (complementary, highest-margin)49       ├─ accept → Upsell 2 (optional, only if the first was accepted - willingness is proven)50       └─ decline → Downsell 1 (same benefit, smaller commitment: single unit, lite version, payment plan)51                      ├─ accept → thank-you52                      └─ decline → thank-you53```

5455Keep the chain at two decisions for most funnels. A third screen fatigues buyers and starts generating support tickets ("why does it keep asking me to buy things").56

382. **One decision per screen.** A grid of four upsells converts worse than one offer with a clear yes/no.393. **Yes must be one tap.** Any re-entry of card details collapses take rate. This is a technical requirement, not a design preference - see below.404. **No must be honest and easy.** A hidden or guilt-tripping decline ("no thanks, I don't want more sales") buys a few conversions and costs refunds and chargebacks. Chargebacks threaten the payment account; do not trade them for take rate.415. **Price relative to what they just paid.** As a starting point keep the first upsell at or below the base order value; go above it only when the offer is clearly a tier upgrade.

63Price: struck-through reference price only if that price is real elsewhere64Accept: one button, verb + outcome ("Add the strap - $19")65Decline: plain text link, honest wording ("No thanks, continue to my order")66Confirmation: state clearly that it is added to the same order and charged to the same card67```

104105Get the repository from <https://github.com/autonnel/autonnel> (Apache-2.0), check106out a release tag, and read its `docker-compose.yml` - it declares the images and107ports that will run. From that checkout:108109```bash110docker compose up111# open http://localhost:4321, complete /setup, then Settings → Payments112```113

75| Stored payment credential usable off-session | Enables charging without re-entry | Take rate drops to near-checkout rates |76| Merged order, not N separate orders | One shipment, one receipt, one refundable record | Fulfilment sees 3 orders for one customer; refunds get messy |77| Deferred push to the store/ERP until the chain ends | So the downstream system receives one complete order | Duplicate orders in Shopify/Woo/ERP |78| Per-charge tracking for refunds | Refund the upsell without refunding the base order | You have to refund everything, or nothing |79| Purchase event value updated after upsells | Ad platform optimizes on true order value | You bid as if every customer is worth the base price only |80| Idempotency on accept | Double-tap on mobile is common | Duplicate charges → chargebacks |81

115116Build order: `self-hosted-funnel-launch` → attach `UPSELL` pages to the funnel → verify with a real test transaction (a live card in test mode, then a real low-value order) before sending traffic. Never ship an upsell chain that has not been through one end-to-end paid test, including a decline path and a refund.117