Woo keeps the real order. Stripe gets a clean payment object.
VeilPay sits between WooCommerce and Stripe as a minimization layer. Your catalog, SKUs, fulfillment details, and customer order context stay in WooCommerce. Stripe gets the smallest practical payload to collect payment.
Products, tax, shipping, stock, and customer data stay in WooCommerce.
Only reference, amount, currency, and a neutral descriptor move forward.
Customers pay on Stripe, not on Woo or VeilPay.
Woo marks the order paid after a signed event maps back to the original reference.
Nothing about your storefront or checkout UI changes. Taxes, shipping, account rules, and stock deductions stay where they are.
The canonical order includes full line items, customer details, totals, internal notes, and fulfillment data.
One payment item, one amount, one currency, one opaque reference. No SKU list and no product naming trail.
The success event maps the opaque reference back to the pending Woo order and updates status.
| Field category | Default Woo to Stripe | VeilPay |
|---|---|---|
| Product names | Sent | Omitted |
| SKUs and variants | Sent | Omitted |
| Line-item breakdown | Sent | Collapsed to one total |
| Storefront success URL | Sent | Replaced with VeilPay route |
| Woo order record | Kept in Woo | Kept in Woo |
Walk through the handoff on your own store.
Send us your store URL and what you want the demo to prove. We will tailor the walkthrough around your WooCommerce payment flow.