Payments and receipts
Hilt is strongest after payment, when the merchant can answer questions quickly and confidently from one operating trail. The core loop is:- the payment
- the member record when access is involved
- the receipt
- the support thread when a conversation needs to continue
Payments show the commercial event
Use Payments to answer:- what was paid
- which template was used
- what asset was used
- when the payment confirmed
- what the next click should be
Members show the access outcome
Use Members to answer:- who the buyer is
- whether access is active
- when access renews or expires
- whether delivery needs attention
Receipts show the proof trail
Receipts are the verification layer:- transaction reference
- public proof link
- template context
- buyer-facing and support-facing proof
The right investigation sequence
When a buyer says something feels wrong:- find the payment
- open the related member record if access is involved
- open the receipt
- confirm what was purchased and what happened afterwards
- open Support if the issue needs a human conversation trail
What each page is best at
| Page | Best question to answer |
|---|---|
| Payments | Did the buyer pay, with what asset, and when did it confirm? |
| Members | Did the buyer receive active access, and does it need follow-up? |
| Receipts | What proof can the buyer or support share externally? |
| Support | Where should the human conversation live if the normal path broke? |