Refund policy

This is the current refund approach for the site’s digital products.

Because the products are digital, refund questions need to be handled a little more carefully than physical-return questions. The short version is that support should review real delivery, billing, and fulfillment problems seriously — without pretending every digital purchase automatically works like a sweater you can mail back.

Updated April 2026Digital productsSupport-reviewed issues

The short version

If there is a real billing, delivery, or fulfillment problem, email support.

That means duplicate charges, failed delivery, the wrong file, corrupted access, or another issue that prevents the customer from receiving what was actually purchased. Those are support problems worth reviewing directly.

Support email for refund-related issues

Email support@sblocktechnologies.com.

Include the product name, the email used for the order, the purchase date if you have it, and a short description of the problem.

The situations support should review most seriously

These are the cases this policy is built to catch.

Common review-worthy cases

Duplicate purchases or duplicate charges.
A completed payment with no working delivery or access path.
The wrong product being delivered.
A corrupted, incomplete, or unusable file we cannot fix promptly.
A technical fulfillment problem that leaves the order unresolved after support review.

What this policy does not promise automatically

Not every digital-product refund question has the same answer.

That is the part worth saying plainly.

Why it is handled case by case

Digital products are delivered electronically and cannot be returned in the same practical way as physical goods. So support needs room to distinguish between a real fulfillment problem and a request that is really about fit, timing, or changed plans.

What to expect from support

Support should review the facts fairly, look at whether delivery actually worked, and respond in light of the order status, the issue described, and the current Stripe-checkout plus protected-delivery flow.

What this policy is trying to match

The policy is meant to track the actual checkout and delivery flow in production: Stripe payment, protected order-access delivery, and support review when a billing or fulfillment problem is real.

Before you write in

These pages answer the questions that usually sit right next to refund requests.

Best companion pages

Delivery and Access

For the digital-delivery baseline and what support should help resolve first.

Support

For the direct support email and what to include in your message.

For the broader digital-product and site-use rules around purchases.

For how order, support, and checkout-related data are handled.

Sources and basis

What this refund page is based on

This page is built from the current digital-product model on the site and the practical need to have a support-first refund route around live Stripe checkout and protected digital delivery.

Current PDF product model and support flow

Used for the support-first structure and the decision to frame refunds around real billing, delivery, and fulfillment problems.

Current trust-page architecture

Used for the split between support, refund, delivery, terms, and privacy so purchase questions land in the right place.

Current Stripe-checkout and delivery implementation

Used so the refund wording matches the real customer flow: Stripe payment, protected order-access delivery, and support review when fulfillment does not work as expected.