All decks
Telegram TON CheckoutPharoah Technology · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductTelegram TON Checkout
Register keytg-ton-checkout
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)
Live atton-checkout.pharoahtechnology.com · HTTP 200 on 9 September 2026
PriceFree · [object Object]
Built from2 register parts, 2 live, 1 probe-verified
Listed14 August 2026

What it does

Telegram checkout with a usage credit-meter and multi-rail top-up, including TON.

Runs on

Telegram Mini App + in-app Stripe checkout surface
Consumer usage credit-meter + multi-rail top-up
Source: estate register (products, product_parts, builder_blocks) · deploy probe 9 September 2026Evidence live
03The frameWhat this buyer's profession checks

We will measure it against the buyer's own change-control.

Three checks a buyer in this field applies, whether or not they name the standard. We use them as the frame for everything that follows.

Check 1

A control between the work and the submission

Check 2

A process fit for this buyer, not a generic one

Check 3

Readiness for the next rule change

Frame chosen by BRG as a summary of the buyer's own change-control. Verify the wording with the body before external use.No accreditation is claimed
04Why it's better · 1 of 6Check 2 · fit for purpose

The job as the register describes it.

Users in Telegram cannot pay for usage without leaving the app or holding the wrong currency.

Who carries it

Telegram merchants wanting to accept Stars and TON crypto.

Source: register pain_point · audienceThe problem, stated plainly
05Why it's better · 2 of 6Check 2 · fit for purpose

What it does instead.

Drop-in checkout that takes Telegram Stars and TON crypto payments on your white-label site or bot. One snippet, instant settlement, no card processor required.

Telegram checkout with a usage credit-meter and multi-rail top-up, including TON.

The parts doing the work

Telegram Mini App + in-app Stripe checkout surface verified

Self-contained Telegram Mini App (SPA at GET /app): verifies Web App initData -> JWT, shows credit balance, AI ask box, Forge tool runner, shop UI, in

Consumer usage credit-meter + multi-rail top-up

Shared consumer usage-credit ledger: getBalance/spend/grant with idempotency on (account,reason,ref); multi-rail top-up (Stripe card packs c50/c200/c5

Source: register purpose, public_blurb, product_parts joined to builder_blocks2 of 2 parts shown
06Why it's better · 3 of 6Check 1 · controls

Proof it exists, not a roadmap.

200

HTTP status of ton-checkout.pharoahtechnology.com on 9 September 2026 · real-content-verified

1/2

register parts verified by probe

2

parts wired live

HTTP 200

functional surface probe

Open ton-checkout.pharoahtechnology.com during the talk. Anything the deck claims should be visible there.

Source: register deploy_probe_code, deploy_probed_at, product_parts.verified_by_probeProbed, not promised
07Why it's better · 4 of 6Against the market, honestly

Where we lead, and where we don't.

Category: in-chat payments. Nearest rivals: Stripe Checkout, Telegram Payments via Stripe, Wallet Pay, Shopify Checkout, PayPal; strongest is Stripe. Our edge: every mainstream checkout ends by sending the buyer to a browser, and each hop loses conversion; we take the payment inside the chat, so the sale never depends on the buyer opening anything. How we beat them: no redirect at the moment of intent, which matters most on mobile where the drop-off is worst.

Source: register vs_competition (18 August 2026)Named competitors are the register's, not the presenter's
08Why it's better · 5 of 6Check 2 · fit for purpose

Built for one kind of buyer.

Telegram merchants wanting to accept Stars and TON crypto.

Source: register audience, serves_nichesOne buyer, not everyone
09Why it's better · 6 of 6Price is part of the scope

What it costs, in one line.

Free

Basis: [object Object]

Buying route

Payment on enquiry
software
Scope named on the next slides, so the price has a boundary
Source: register price_gbp, billing_interval, pricing_basis, payment_link_activeNo hidden rate card
10What's inside

The parts, with their verification state.

PartCategoryStateVerified
Telegram Mini App + in-app Stripe checkout surfacefull-stacklive_wired
Consumer usage credit-meter + multi-rail top-upbackendlive_wired
Source: product_parts joined to builder_blocks · 2 of 2 shown probe-verified   not yet
12Why packaging matters

Five things a package does that a price cannot.

1
Scope becomes visible. The parts are named, so nothing is assumed.
2
Boundaries are explicit. What is outside is written down before the first invoice.
3
It is auditable. A package is a documented process, which is what the buyer's own change-control looks for.
4
Buyers compare like for like. A referral needs a defined thing to refer.
5
Switching fear drops. The move is inside the package, not a project bolted on the front.
Source: BRG packaging doctrine; frame from slide 3Packaging = a compliance instrument
13This packageCut by what each part does

Telegram TON Checkout, as a package.

full-stack

Telegram Mini App + in-app Stripe checkout surface

Self-contained Telegram Mini App (SPA at GET /app): verifies Web App initData -> JWT, shows credit balance, AI

verified
backend

Consumer usage credit-meter + multi-rail top-up

Shared consumer usage-credit ledger: getBalance/spend/grant with idempotency on (account,reason,ref); multi-ra

live_wired
Source: product_parts grouped by builder_blocks.category2 groups
14Anatomy of the packageOn one page · 1 items of work left, filed

A package reads like a control document.

Inside the scope

  • Telegram Mini App + in-app Stripe checkout surface

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 1 parts probe-verified, latest 9 September 2026
  • Functional surface: HTTP 200
  • Register row updated with every probe

Outside the scope today · work left

  • No build gap recorded in the register
  • 1 part still to verify by probe

Who signs, and where the work sits

  • Pharoah Technology Ltd owns the product and the data layer
  • 0 build packets proposed · 1 management item pending
  • Change log kept in the register
Source: product_parts (inside), deploy and part probes (evidenced), v_deck_work_left (work left; filed to manager_work and build_packets by deck_work_left_sync)One page
15Across the family

Where it hands over.

Anaïs AIgateway.pharoahtechnology.com
Anaïs AI (LLM router / reseller)anaisai.co.uk
Anaïs AI (working app)anaisai.co.uk
Pharoah TechnologyTelegram TON Checkoutton-checkout.pharoahtechnology.com
ATS Résumé Scanner (free)ats.pharoahtechnology.com
Aurora AIauroraai.pharoahtechnology.com
Aurora Guardauroraguard.co.uk
Source: register rows sharing client_key pharoahOne house, many doors
1 / 16
Arrow keys or space · N narration · P print
Slide 1Narration Words Running total

Production guide

How to turn these sixteen slides into a presentation video. Same structure as every deck in the family, so a crew that has made one can make them all.

1 · Deliverable

ItemSpec
Format16:9, 1920×1080, 25 fps, H.264 MP4 plus WebM. Burned captions and a sidecar SRT.
RuntimeNarration below plus screen captures of the live product; typically 8 to 12 minutes.
Framethe buyer's own change-control. Verify the wording of the three checks with the body before external use.
BrandPharoah Technology family palette as rendered here. Green only for verified and live states; red only for exclusions.
VoiceCalm, exact, never theatrical. Read figures and dates in full. Numbers are the register's, and the register is cited on every slide.

2 · Runtime plan

#SlideNarrationWordsStarts

3 · Screen captures

4 · Full narration

5 · What this deck must not say

  • No numbers that are not on a slide with a register source.
  • No accreditation by the buyer's own change-control; the frame is a lens, not a badge.
  • No named competitor read aloud unless the audience asks; the register's names are on slide 7 for the presenter.
  • No client names, volumes or tenure unless the register carries them.

6 · Regenerate

This deck is generated from the estate register. Update the product row, re-run the deck build, redeploy. Do not hand-edit this file.