store.sgit.ai / paying

Paying

What is due now, and what is due when the work is in your hands. Nothing on this page collects anything — there is no form, no card field and no account, and a card is typed on the provider’s own pages.

Why two of the four take a deposit

Two of the four levels are produced without anybody being scheduled, so they take the whole price. The other two are somebody’s work, and neither has run for a paying buyer yet — so they take a fifth on the order and the rest when the work is in your hands. £100 of £500; £300 of £1,500.

The split belongs to the offer and not to the rail. A card tapped on a terminal at the stand takes the same deposit as a link opened on a phone, because what is being split is the risk on a thing that has never run, and that does not change with how the card is read.

A discount code, and why there is nowhere to type one

A code arrives in the address, not in a field. There is no text input anywhere in this site’s output and the gate refuses one, so a code is handed over the way a printed card or a QR at a stand hands it over anyway — store.sgit.ai/policies/?code=…. The store recognises it, shows it as a chip that can be removed, and takes it back out of the address bar, because a screenshot of a checkout should not carry one.

What ships is the hash of the code and never the code. A page that recognised a code by carrying it would be publishing it the moment it was built, so the browser hashes what it was handed and compares. That is worth what it is worth and no more: a short code can be ground out of a hash, and the thing that actually stops a stranger paying nothing is that a browser does not take money — a code changes the amount a payment link is issued for, and the rail decides what is charged.

It comes off the price, and the deposit is then taken on what is left. Half off the £500 level is £250, of which £50 is taken now and £200 on delivery. A code never moves the split, which is a property of the offer. A code at a hundred per cent still places an order and still lands on the page that says what happens next — which is the whole use of one: the flow can be walked end to end before a single real payment link exists.

What the store never sees

No name, no contact, no card. There is no form, input, textarea or select anywhere in this site’s output and a build check holds that line; the provider takes all three on its own pages and hands back nothing. What travels is the amount and an order reference carrying the product codes.

Which agent do you run? → How buying works → Every claim, with its state →