LOADING
CHECKOUT, RAILS AND SETTLEMENT
The buyer-facing surface. It qualifies the purchaser, evaluates the cart against every applicable rule, and presents only the payment rails the transaction is actually eligible for.
Business verification, mandatory 2FA and a research or business purpose where the category calls for it. Verified once through Fox Pass, reused on every return visit.
Quantity ceilings enforce at add-to-cart, not at payment. Prohibited combinations never assemble. A buyer never reaches a payment screen they were going to be stopped at.
Each clause is a separate row with its text version and timestamp, not one bundled acceptance — which is what makes them usable as dispute evidence later.
Card data passes from the browser to the acquirer's gateway through hosted fields. No card number transits, is processed by, or rests in this platform.
It selects among permitted rails and never searches for one that will accept. Financial failures may retry within the set; a compliance block may not retry anywhere.
Merchant to acquirer to bank, reconciled daily three ways against platform decisions and bank deposits. A deposit from an unrecognized processor escalates the same day.
Signs in, or creates a business account. Google establishes continuity; it never establishes identity.
Fox Pass is read for an existing credential. If one is current, checkout continues. If not, verification runs here.
Every line is checked against SKU state, certificate currency, quantity ceilings and prohibited combinations, at add-to-cart.
One request to Fox Rules returns either a frozen set of permitted rails, or a terminal block. There is no third answer.
Each clause is recorded as its own row with the text version shown and the timestamp accepted.
Hosted fields post the card directly to the acquirer. A token returns. No card number touches this platform.
An HTML and PDF snapshot is written, carrying the SKU, certificate links, attestation version and support contact.
Funds move merchant to acquirer to bank. Reserves accrue at the agreed term and release daily once the first hold period matures.
Daily, three ways. Any mismatch escalates to the acquirer and the bank the same day.
Blocked and declined are different types with different code paths. The blocked screen has no retry button, no alternate rail, and no route back into payment. If they shared a component someone would eventually add a retry, and the compliance stop would leak into the payment path.
Pick a scenario from the demo bar. 'Patented compound' stops before payment renders; 'Ordinary order' clears and shows two rails, not three, because one SKU restricts ACH.
