I got some really great questions via email and on my community about PaySnap and I thought I would post my reply here as well.
Shipping costs
PaySnap doesn’t have a backend shipping engine or carrier integrations, so there’s no system that automatically calculates rates based on weight, dimensions, or destination. What you can do is build shipping cost options manually using PaySnap’s form builder — a dropdown or radio field where the customer selects their region (domestic, Europe, international, etc.) and the appropriate rate gets added. You’d set those rates yourself based on what you know about your products’ weights and typical shipping costs.
For the “don’t charge twice” problem — that’s trickier without automation. One practical approach: charge a flat shipping rate at checkout and absorb or refund the difference for multi-item orders. Or you could use a “shipping” product line item that customers only add once. It’s not elegant, but it works for lower-volume stores.
If you need real-time carrier-calculated shipping across multiple countries and complex order combinations, honestly PaySnap isn’t the right tool for that use case. That’s where a full platform subscription starts to earn its keep.
Digital products
Yes, and after thinking about this more I have a simple idea for the next update to make it even better.
PaySnap has a return URL field — after a successful payment, you can redirect the customer to a page that delivers the download. If the visitor is arriving from Stripe or PayPal (i.e., a real checkout), the content is shown. If someone just pastes the URL directly into their browser or shares it with a friend, they get redirected away instead.
This will stop casual link sharing, which covers the vast majority of situations for typical digital products. For most use cases — selling a template, a PDF, a preset pack, etc.
A more robust digital delivery flow (proper token-based access, download limits, that kind of thing) is on my list for a future version.
Bundles and importing products
Bundles are possible — you can build a product listing that represents a bundle with its own price, options, and cart behavior. There’s no “customers also bought” logic or automatic bundling, but you can absolutely set one up manually.
For importing products from a spreadsheet: not directly via PaySnap itself, since the product data lives inside the stacks rather than in a central database. However — this is actually where the Total CMS 3 and Feeds integrations become useful. PaySnap is built to work with both, which means you can drive your product catalog from a CSV or a CMS collection and loop through it dynamically. It takes more setup, but if you have a large product catalog, that’s the path.
The bigger picture
PaySnap is a one-time purchase that lets you hand-build exactly the store your client needs, for as many sites as you want, without platform fees. The trade-off is that it’s not a managed commerce platform — you’re assembling the pieces yourself. For simpler stores or specific use cases, that’s a great deal. For high-complexity requirements (multi-country shipping calculations, automated receipts, inventory sync), it takes more elbow grease, and there are cases where a subscription platform may genuinely be the better fit.
I’m planning a next major version (likely under a new name) and the features I most want to add are: email receipts to purchasers, a better standardized digital product flow, and possibly a shipping integration. No timeline or promises yet, but those are the priorities. Total CMS 3 is also getting a full ecommerce extension down the road, which will open up a lot more — centralized product management, richer integrations, the works.
Hope that helps clarify things. Keep the questions coming.
PaySnap for Stacks Website Builder