Plain answers about what VeilPay changes, and what it does not.
This is a data-minimization layer for WooCommerce and Stripe. It does not change your merchant identity, policy obligations, or Stripe's visibility into payment-required data.
Does VeilPay hide my Stripe business identity?
No. Stripe still sees your Stripe account, payment amount, customer payment details, and any compliance data Stripe requires. VeilPay minimizes catalog and order detail, not merchant identity.
Does VeilPay process card data?
No. Customers enter their card on Stripe-hosted pages. Card entry, 3DS, and card network flows stay on Stripe.
Does WooCommerce still keep the full order?
Yes. WooCommerce remains the source of truth for products, customer details, shipping, tax, stock, and fulfillment history.
Is this for bypassing Stripe rules or restricted-business policies?
No. VeilPay is for cleaner payment architecture and smaller outbound payloads. Merchants must still comply with Stripe, card network, and local regulatory requirements.
How does installation work?
VeilPay is implemented as a WooCommerce payment method flow. You add Stripe credentials, a signing secret, verify sandbox callbacks, and then enable the payment method in production.
What about refunds and disputes?
Refunds can still originate in WooCommerce or Stripe. The opaque payment reference keeps reconciliation consistent between both systems.
Why not just redact fields after the fact in Stripe?
Because the cleaner design is to avoid sending unnecessary fields in the first place. That reduces both audit surface and operational leakage.
Still have a specific edge case?
Send the scenario and we will map it against the current VeilPay flow, sandbox behavior, and WooCommerce reconciliation model.