A concise definition
A digital receipt records the supported details of a completed transaction in electronic form. It is not the payment itself, and it does not prove that an unrelated payment provider settled funds. In TerraGridTech’s current flow, an approved POS creates the receipt after the sale and presents a QR or receipt code that the customer can use with TGT User Wallet.
How it differs from an emailed PDF
An emailed PDF is one delivery format and normally requires the merchant to collect an email address. A QR claim can let the customer choose to collect the receipt in a supported Wallet flow. The choice of delivery method does not change the merchant’s responsibility to provide required transaction information or an accessible alternative.
How it differs from a payment record
A receipt describes a sale. A bank statement, card authorisation or payment-provider status describes movement or authorisation of money. The two records can be related but should not be presented as interchangeable. TerraGridTech’s public receipt pages do not verify provider settlement.
Receipt creation and customer claim
The approved business or POS sends supported receipt facts using controlled access. The service returns receipt readiness information for the customer QR. A customer can scan the QR or enter the receipt code in TGT User Wallet. Claiming an already-created receipt uses no additional receipt credit. [1]
Merchant proof and personal Wallet metadata
The business receipt remains the merchant-facing proof of what was issued. Personal categories, labels and notes that a customer adds in the Wallet are customer metadata; they should not silently rewrite the merchant’s receipt proof. This separation helps preserve the meaning of the original record.
Privacy and customer choice
A receipt should contain only the information needed for its legitimate purpose. Sensitive credentials do not belong in receipt fields. Retailers should explain the available delivery options and preserve a reasonable alternative for people who cannot or do not want to use the Wallet. [8][10]
Practical checklist
- Complete the sale before creating the receipt.
- Confirm which receipt facts the merchant must retain.
- Offer a clear customer delivery choice.
- Keep credentials and unnecessary personal data out of receipt fields.
- Provide a paper or other accessible fallback where required.
Limitations
- A digital receipt is not a payment-settlement guarantee.
- Availability depends on an approved business, active plan and supported POS flow.
- Legal and retention needs vary by transaction and jurisdiction.
Next steps
Sources and limitations
TerraGridTech. Current product answers and operating limits (opens in a new tab). 2026-07-17. Accessed 2026-07-17.
Scope: Current TerraGridTech production product scope. Limitation: Product operating facts, not environmental evidence; recheck after any plan or backend contract change.
Ministry of Electronics and Information Technology, Government of India. Digital Personal Data Protection Act, 2023 (opens in a new tab). 2023-08-11. Accessed 2026-07-17.
Scope: India. Limitation: Not legal advice; staged commencement and implementing rules must be checked at the time of use.
National Institute of Standards and Technology. NIST Privacy Framework (opens in a new tab). Version 1.0 published 2020; programme updated continuously. Accessed 2026-07-17.
Scope: United States; voluntary international use. Limitation: Voluntary framework; it is not certification or a substitute for applicable law.