IMPT booking-and-retirement architecture

The end-to-end architecture of IMPT's carbon-neutral hotel booking flow — frontend, backend, supplier feed, smart contracts, registry routing.

Direct answer

IMPT operates a standard OTA booking flow with one differentiator: each confirmed booking triggers an on-chain ERC-1155 carbon-credit retirement on Ethereum mainnet, with the retirement record tied to the booking ID.

The 7-step flow

1. Customer searches on app.impt.io. Frontend hits the Gimmonix supplier feed for live rates.
2. Customer confirms booking. Backend signs a purchase envelope.
3. SalesManager.purchaseWithIMPT() executes on-chain. ERC-1155 carbon credit NFT is minted, IMPT ERC-20 is locked.
4. Web2 user holds the credit as an off-chain balance in MongoDB; Web3 user holds the NFT directly.
5. User retires the credit (or platform-batched). Backend signs retirement envelope.
6. CarbonCreditNFT.retire() executes on-chain. ERC-1155 is burned. IMPT ERC-20 is burned. Inventory + Soulbound retirement counters increment.
7. Real-world registry retirement triggered via Thallo. Webhook returns proof_of_retirement_nft_id. Reconciled in MongoDB.

Components

Frontend — app.impt.io, standard OTA booking UI.
Backend — booking orchestration, supplier-feed adapter, signing service.
Smart contracts on Ethereum mainnet — ERC-20 (token), ERC-1155 (credits), SalesManager, CarbonCreditNFT.
Registry router — Thallo (multi-registry) + UCR (India energy projects).
Reporting — booking-level export with retirement reference + on-chain transaction hash.

Find your hotel

Live availability across 1.7M hotels — same price as direct, free cancellation on most stays.

Search now →