Headless 360Advancedcheckoutpaymentsstripecommerce
Implement headless checkout with payment provider abstraction
Real World Scenario
The brand uses Stripe for payments across web and mobile while B2C Commerce manages basket and order creation.
Expected Answer
• Integrate payment provider via Commerce payment processor framework or custom hook
• PCI scope minimization using provider SDK tokenization—no raw card data on app servers
• Idempotent payment intent creation tied to basket ID preventing double charges
• Handle async payment confirmation webhooks updating order status in Commerce
• 3DS and regional payment method support per market configuration
• Reconciliation between Stripe settlements and Commerce order totals
• Clear failure UX with basket preservation on payment decline
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Integrate payment provider via Commerce payment processor framework or custom hook Also consider: PCI scope minimization using provider SDK tokenization—no raw card data on app servers In practice: Idempotent payment intent creation tied to basket ID preventing double charges Optimize for scale and operational observability.
Architect Perspective
Payment abstraction layer isolates provider swaps—never embed Stripe-specific logic throughout checkout UI code.