Secure payment handling
Payment Security
Webbly uses hosted payment-provider checkout so sensitive payment credentials are entered into the provider's secured payment environment rather than Webbly's application.
1. Hosted checkout
Webbly currently sends subscription purchases to Stripe Checkout. Payment fields are served and processed by Stripe. Webbly does not receive or store complete payment-card numbers or card security codes. If Klarna is later displayed as an available method, its hosted components and payment terms will govern that transaction.
2. Transmission safeguards
- Checkout and account traffic is transmitted over HTTPS using transport encryption.
- Payment-provider credentials remain in server-side configuration and are not exposed to the browser.
- Webbly verifies payment status on the server before activating a paid subscription.
- Webhook requests are authenticated before payment events are accepted.
- Access to billing actions is restricted to authorized workspace roles.
3. Information retained
Webbly may retain payment references, provider customer or subscription identifiers, plan, currency, amount, invoice status, and limited payment-method descriptors supplied by the provider. This supports subscription administration, accounting, fraud prevention, refunds, and disputes. Complete card credentials remain with the payment provider.
4. Customer safety
Never send complete card details, passwords, or security codes by email. Confirm that hosted checkout uses an expected Stripe or, when available, Klarna domain before entering payment information. Report a suspicious payment page or billing message immediately to [email protected].
5. Related information
See our Privacy Policy for payment-data use and our Refund & Cancellation Policy for billing corrections and refunds.