ShipWright help

Payments

ShipWright uses Stripe test payment rails for the paid pilot order path and tracks authorization, capture, and order completion.

All help

What this screen does

  • Explains payment state shown on orders and job detail.
  • Separates authorization from final capture.
  • Documents the staging test payment setup used by the paid pilot proof.

What to do next

  • Authorize payment during customer checkout.
  • Progress the linked delivery to delivered.
  • Verify capture and final customer order completion.

Status meanings

StatusMeaningNext action
REQUIRES_PAYMENT_METHODNo valid card has been collected.Collect card details in checkout or the payment panel.
AUTHORIZEDStripe has authorized funds but not captured them.Complete delivery before capture.
CAPTUREDPayment capture succeeded.Confirm the order is FULFILLED if the job is delivered.
FAILEDPayment failed or Stripe rejected the request.Inspect Stripe and API error details.

Related guidance

Pilot fallback playbooks

Open the related ShipWright guidance.

Operator actions

  • Confirm web has NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY and API has STRIPE_SECRET_KEY.
  • Use test card 4242 4242 4242 4242 in staging.
  • Verify PAYMENT_AUTHORIZED after checkout and CAPTURED after delivered/capture flow.
  • Check linked order, job, payment, job events, audit log, and outbox records when proving a flow.

Common problems

  • stripe_not_configured: Render or Vercel Stripe environment variables are missing or stale.
  • secret_key_required: the API is not receiving a valid sk_test secret key.
  • Payment authorized but not completed: the delivery has not been delivered and captured yet.
  • Webhook pending: inspect outbox and webhook handling before assuming final payment state.