// Security by vertical
SaaS security for e-commerce and marketplace
Why e-commerce concentrates revenue risk
E-commerce and marketplaces are made of flows that touch money constantly: checkout, coupon, order, payment, refund. Each is a surface where a mistake becomes a direct loss (fraud, an infinite coupon, another buyer’s order exposed). In a marketplace, seller isolation adds on: one seller must not see another’s orders, revenue or customers.
AI-built e-commerce gets the storefront right and the checkout and multi-seller boundary wrong, which is where the money and buyer data live.
RET runs this test: a 25-hour Sprint for R$9,500, within 7 business days. See price and timeline for my case
What to review in an e-commerce SaaS
The focus is the money, the order and (in a marketplace) the separation between stores.
- Price, discount and coupon validated on the server, never trusting the client.
- IDOR in an order, invoice or address: swapping an id must not expose another’s purchase.
- Payment webhook with signature and idempotency (no unlock without payment, no double).
- Marketplace: per-seller isolation on orders, revenue and customer data.
- Refund and cancellation flow leaving no orphaned access or credit.
The sector bar
E-commerce faces PCI-DSS (if it touches cards), privacy law for buyer data, and the expectation that fraud and chargebacks are contained. A marketplace adds the seller-contract layer (a cross-store leak is a clause). The technical proof that checkout and isolation hold is what RET delivers.
Where RET fits
The Manual Pentest proves what breaks in checkout, payment and seller isolation, with evidence. Risk Review reads those flows before you scale. The Promptbook guides the first pass on the price, coupon and webhook points.
Frequently asked questions
What is the most common fraud in AI-built e-commerce?
Manipulating price/discount/coupon on the client (AI validates on the front, not the server) and IDOR in orders. Both are cheap to exploit and expensive to ignore; price and coupon must be decided on the server.
What changes in a marketplace?
Seller isolation adds on: one store must not see another’s orders, revenue or customers. It is the same cross-customer leak risk, with contract weight between the stores.
Do I need PCI?
It depends on how you touch cards. Tokenizing via a certified provider greatly reduces the scope. RET does not issue PCI, but tests the technical security of checkout and payment that PCI asks about.
Who runs it at RET?
Gabriel Lima Ferreira, founder and lead pentester, with an authorized scope and reproducible evidence.