​

Payments and receipts

Hilt is strongest after payment, when the merchant can answer buyer questions from one place. 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

Payments are the first stop when a merchant wants to trace a transaction.

​

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

Not every template creates a member record, but when it does, Members becomes the access truth.

​

Receipts show the proof trail

Receipts are the verification layer:

• transaction reference
• public proof link
• downloadable PDF proof
• invoice metadata
• template context
• buyer-facing and support-facing proof

When a buyer asks for evidence, the receipt should be the clean answer. Hilt’s receipt workspace is now useful for more than just opening a single proof link. Merchants can work from one ledger to:

• search by receipt, transaction, wallet, or product
• attach invoice details to the receipt record
• open the public proof page
• generate a PDF proof document
• send the proof link directly to the buyer

​

The right investigation sequence

When a buyer says something feels wrong:

1. find the payment
2. open the related member record if access is involved
3. open the receipt
4. confirm what was purchased and what happened afterwards
5. open Support if the issue needs a human conversation trail

That workflow is far more reliable than reconstructing the story from wallet screenshots alone.

​

What each page is best at

​

When the buyer needs the next concrete action

If the issue is not just proof, the merchant flow should stay operational:

• retry delivery from the member or support view when access did not land
• inspect subscription status when a recurring buyer needs the next access step
• send the receipt proof directly when the buyer only needs evidence

That keeps proof, access, and support attached to the same payment story instead of scattering the work across separate tools.

​

Common questions

​

What is the difference between Payments, Members, and Receipts?

Payments show the confirmed commercial event, Members show the access outcome, and Receipts show the shareable proof trail.

​

What should I open when a buyer says they paid?

Find the payment first, then check the related member record if access is involved and the receipt if proof is needed.

​

Are receipts only for buyers?

No. Receipts also help merchants, support teams, and external systems verify what was purchased, when it confirmed, and which proof link belongs to the transaction.