Test your Checkout Everywhere integration

Run these cases against the Checkout Everywhere quickstart. Copy the tables into your test report and attach redacted evidence. Every case starts Not run.

Scope and setup

Scope	What is covered
Quickstart	Dashboard workflow to connect the store, configure checkout, generate a direct link/QR, and verify a store order.
Merchant integration	Store catalog, stock, shipping/tax settings, support details, and the installed connector’s order permissions.
Additional launch work	Live campaign destinations, printed QR assets, fulfillment, receipts, refunds, and reporting.
Inputs	BigCommerce test store, one available physical product/variant, one sandbox campaign and link, downloaded QR PNG, test phone, and expected shipping/tax totals.
Evidence	Record build/date, tester, sandbox division, device/browser, case result, order/transaction/seller or link IDs as applicable, and redacted logs/screenshots. Never attach tokens, credentials, or personal banking data.

Use real sandbox execution for Q cases. Label controlled response substitutions, outages, and replay tests separately; mocks do not establish live payment acceptance. Use a fresh order for each payment test and reset store/fixture changes afterward. Do not retry an uncertain payment until it is reconciled.

1. Quickstart checkpoints

Test	Input	Steps	Expected output	Result
Q1 · Connect store	BigCommerce test hash/token	1. Connect the test store with the documented scopes. 2. Locate the product.	Catalog imports from the intended store; no live store connected by mistake.	Not run
Q2 · Configure checkout	Bolt Payments; store branding/support	1. Reopen payment settings. 2. Inspect logo and contact details.	Immediate Capture and correct currency saved; store identity/support correct.	Not run
Q3 · Create link	Sandbox quickstart campaign; chosen variant	1. Create Direct to checkout link. 2. Open copied URL.	Correct product, variant, quantity, price, and currency; no unexpected promotion.	Not run
Q4 · Create QR	Downloaded PNG; phone camera	1. Scan at intended size. 2. Compare with copied link.	Same checkout/product/variant; readable scan and usable mobile destination.	Not run
Q5 · Verify order	4111 1111 1111 1111; 03/30; 737	1. Pay once from QR destination. 2. Match Bolt transaction and BigCommerce order.	Completed payment and matching product, shopper, amount, currency, and order number in both systems.	Not run

2. Functional integrity

Test	Input	Steps	Expected output	Result
F1 · Disabled destination	Deactivate test link	1. Open old URL. 2. Scan saved QR. 3. Reactivate and repeat.	Inactive destination cannot complete a new purchase; reactivation restores the intended destination.	Not run
F2 · Product availability	Make test variant unavailable	1. Update store availability. 2. Wait for catalog sync. 3. Open link.	Unavailable item cannot be sold; restore inventory after the test. Record observed sync delay.	Not run
F3 · Store totals	Supported shipping/tax address	1. Compare final checkout total with store configuration. 2. Complete purchase.	Shipping/tax included consistently in payment and store order.	Not run
F4 · Payment/order gap	Missing or delayed connector order in a controlled test	1. Observe paid transaction without store order. 2. Follow recovery process.	Support can identify and reconcile the original transaction; no blind repeat charge.	Not run
F5 · Cancellation	Close checkout before payment	1. Start from link. 2. Close. 3. Reopen.	No paid order from abandonment; correct variant remains available when reopened.	Not run

3. Merchant-owned experience

Test	Input	Steps	Expected output	Result
E1 · Campaign promise	Actual email/post/QR artwork	1. Compare copy, price, and variant with destination.	Campaign promise matches what the shopper can buy; no misleading price or product.	Not run
E2 · QR readability	Intended printed/display size and lighting	1. Scan with supported phones. 2. Try at normal viewing distance.	Reliable scan without cropping; destination clear and usable. Record asset dimensions.	Not run
E3 · Branding/support	Checkout logo/contact details	1. Review on desktop and phone. 2. Follow support route.	Recognizable merchant and reachable support; no test placeholder branding.	Not run
E4 · Accessibility	Merchant campaign page; keyboard/screen reader	1. Reach link and read campaign. 2. Use text-link alternative to QR.	Descriptive accessible link and readable layout; QR is not the only way to reach checkout.	Not run
E5 · Confirmation	Completed order	1. Read confirmation. 2. Find order/support details.	Clear purchase result, expected delivery, and recovery/support route without requiring a second purchase.	Not run

4. Additional launch requirements

Test	Input	Steps	Expected output	Result
L1 · Live destinations	Production campaign and final artwork	1. Confirm production store/payment setup. 2. Scan every final asset.	Each asset uses the intended production URL; no sandbox destinations distributed.	Not run
L2 · Order lifecycle	Receipt, inventory, fulfillment, refund	1. Run each supported operation. 2. Reconcile store/Bolt records.	Business effects occur once; refund and inventory behavior agree with merchant policy.	Not run
L3 · Decline/review	Account-appropriate failure/review cards	1. Complete sandbox scenarios. 2. Check store and payment states.	No fulfillment on an unapproved/unpaid purchase; merchant-owned recovery is clear.	Not run

Completion gates

Gate	Required evidence
Quickstart verified	All Q cases pass in the real sandbox, including merchant-owned integration work.
Ready for launch review	All Q, F, E and applicable L cases pass; no required Blocked or Not run cases. Record exclusions with a reason and obtain technical/experience-owner review.
Failed or blocked case	Record actual output, issue/owner, and retest evidence. A successful payment does not excuse a broken shopper or seller experience.

Use Pass, Fail, Blocked, Not run, or Not applicable with a reason. A build or mocked test result does not verify production processing, delivery, or settlement.