Managing transactions.

View history and rollback transactions when needed

Jul 7, 2026

View complete stamp transaction history for any customer and rollback incorrect stamps when necessary. Maintain accurate records while providing excellent customer service.

Accessing transaction history

From members list

Go to Members in the partner sidebar
Search for the customer by name or email
Click the customer's name to open their profile
Locate the Stamp cards column
Click the stamp card name to view transactions

What you'll see

Member information card:

Customer name and tier
Club membership
Quick stats (total points, tier progress)

Stamp card preview:

Current progress (X/Y stamps)
Visual stamp grid
Completion status

"Add stamp" button:

Quick access to add a stamp by hand
Pre-filled with customer information

Transaction timeline:

Chronological list of all stamp activities
Most recent at the top
Complete audit trail

Understanding transaction types

Stamp earned

Event: stamp_earned Description: Customer received stamp through normal purchase

Details shown:

Date and time
Stamps added (+1 in most cases)
Purchase amount (if recorded)
Staff member who processed
Internal notes (if any)
Before/after stamp counts

Example:

Stamp Earned
+1 stamp
Purchase: $7.50
Staff: John Smith
Note: "Regular morning coffee"
Before: 6 stamps → After: 7 stamps
December 4, 2025 at 9:15 AM

Stamps bonus

Event: stamps_bonus Description: Promotional or manual bonus stamps awarded

Use cases:

Customer complaint resolution
Birthday bonuses
Special promotions
Loyalty rewards

Example:

Stamps Bonus
+2 stamps
Staff: Manager
Note: "Birthday bonus - thank you for being a loyal customer!"
Before: 5 stamps → After: 7 stamps
December 4, 2025 at 2:30 PM

Card completed

Event: card_completed Description: Customer collected final stamp and completed card

Details shown:

Completion timestamp
Final stamp that triggered completion
Reward details
Pending rewards count

Example:

Card Completed
+1 stamp (completion)
Purchase: $6.00
Staff: Sarah Johnson
Reward: 1000 points credited
Before: 9 stamps → After: 10 stamps
December 4, 2025 at 4:45 PM

Reward redeemed

Event: reward_redeemed Description: Customer claimed their physical reward

Details shown:

Redemption timestamp
Staff who processed
What was given

The card itself already reset when it completed; redeeming only clears one pending reward, so this row carries no stamp change.

Example:

Reward Redeemed
Physical reward claimed
Staff: Mike Davis
Note: "Gave free large latte"
December 5, 2025 at 10:00 AM

Stamps adjusted

Event: stamps_adjusted Description: Manual adjustment by partner or admin

Use cases:

Correcting errors
Customer service resolutions
System migrations

Example:

Stamps Adjusted
+3 stamps
Partner: Business Owner
Note: "Compensation for system downtime"
Before: 4 stamps → After: 7 stamps
December 4, 2025 at 11:00 AM

Stamps voided

Event: stamps_voided Description: Previous stamp transaction was rolled back

Details shown:

Negative stamp count
Original transaction reference
Reason for void
Who performed the void

Example:

Stamps Voided
-1 stamp
Partner: Business Owner
Note: "Duplicate scan - corrected"
Before: 8 stamps → After: 7 stamps
December 4, 2025 at 3:15 PM

Stamps expired

Event: stamps_expired Description: The card's inactivity window ("stamps expire after N days") passed without a new stamp, so the system cleared the current stamps. A program's end date never removes stamps; it only stops new earning.

Details shown:

Expiration date
Stamps removed
The inactivity note

Example:

Stamps Expired
-7 stamps
System: Automated
Note: "Stamps expired after inactivity period"
Before: 7 stamps → After: 0 stamps
January 1, 2026 at 12:01 AM

Filtering transaction history

Click Filters (next to Export) to open the filter panel. You can stack several filters at once. Each one narrows the list further. Active filters appear as removable chips below the page header, and a count on the Filters button shows how many are applied.

Available filters

Stamp card: Show only transactions for one or more of your stamp cards. Useful when you run several programs and want to read one card's ledger at a time.
Event: Show only specific transaction types (Stamps earned, Bonuses, Completions, Redemptions, Adjustments, Voids, Expirations). Pick one or several.
Stamps: Filter by the number of stamps using a numeric condition: equals, at least, at most, greater than, less than, or between two values.
Date: Filter by when the transaction happened: on a day, before, after, or between two dates.

To add a filter, choose a field from Add filter, set its condition and value, then click Apply. Remove a single filter with the × on its chip, or clear them all with Clear all.

Filters carry into exports

Whatever you filter (and search) on the list is what you export. Narrow the list first, then click Export. The CSV, TSV, or JSON contains only the matching rows.

Search

Search within transactions:

Event type
Stamp card name
Member name

Results update as you type.

Rolling back transactions

When to rollback

Valid reasons:

Duplicate scan (customer scanned twice)
Wrong stamp card (meant for different program)
Accidental addition
Customer request with valid reason

Invalid reasons:

Customer changed their mind after purchase
Retroactive policy changes
Arbitrary removals

Rollback process

To delete the last stamp:

Open customer's transaction history
Verify the most recent transaction is the one to remove
Click "Delete Last Stamp" button
First click: Button shows warning
Second click: Confirms deletion
Void transaction is created
Stamp count decrements
Statistics update automatically

Two-step confirmation prevents accidental deletions.

Rollback scope

Delete last stamp voids the customer's most recent earned, bonus, or adjusted stamp entry on that card. It works whether or not the card completed in between; the count steps back within the card's range. To unwind several stamps, repeat the action, one entry at a time, newest first.

Staff have their own narrower correction at the counter: Undo recent stamp reverses only their own latest stamp. The partner-side delete covers everything else.

After rollback

What happens:

Void transaction appears in timeline
Stamp count decreases
Progress bar updates
Customer sees updated progress
Complete audit trail preserved

All transactions remain in the database: Nothing is deleted for good. The void transaction creates a negative entry that reverses the original.

Viewing internal information

As a partner, you see information customers don't:

Purchase amounts

Visible to: Partners, Staff, Admins Hidden from: Customers

Track transaction values for:

ROI analysis
Average purchase calculations
Minimum purchase verification

Staff attribution

Visible to: Partners, Staff, Admins Hidden from: Customers

See which staff members are:

Processing most stamps
Making errors (frequent voids)
Providing excellent service

Internal notes

Visible to: Partners, Staff, Admins Hidden from: Customers

Read context about transactions:

Special circumstances
Customer requests
Promotional details
Resolution notes

Exporting transaction data

To export customer transaction history:

Open transaction history page
Apply any desired filters
Click Export button
Select CSV format
Download file

Export includes:

All transaction details
Timestamps
Staff information
Purchase amounts
Notes
Before/after counts

Use exports for:

Customer service documentation
Dispute resolution
Audit compliance
Business analysis

Common management scenarios

Scenario 1: Duplicate scan

Situation: Staff scanned the customer's QR code twice by mistake

Solution:

View transaction history
Identify duplicate entry (same timestamp, same staff)
Click "Delete Last Stamp"
Confirm deletion
Explain to customer

Scenario 2: Wrong program

Situation: Stamp added to coffee card instead of pastry card

Solution:

Rollback stamp from coffee card
Go to the correct stamp card
Add the stamp to the pastry card by hand
Add note explaining the correction

Scenario 3: Customer dispute

Situation: Customer claims they should have more stamps

Solution:

Review complete transaction history
Verify customer's claim against records
If valid: Add bonus stamps with explanatory note
If invalid: Explain the discrepancy
Document resolution

Scenario 4: System error

Situation: Stamps weren't added due to technical issue

Solution:

Verify the issue occurred
Add the missing stamps by hand
Note: "Added manually - system error on [date]"
Report technical issue to support

Best practices

Review often: Check transaction history weekly to spot patterns or issues.

Document everything: Add a note whenever you adjust stamps by hand.

Train staff: Ensure employees understand proper stamp addition procedures.

Respond fast: Address customer concerns about stamp counts right away.

Maintain accuracy: Only rollback when necessary and justified.

Preserve history: Never delete transactions. Use voids for corrections.

Troubleshooting

"Cannot delete last stamp"

Possible causes:

Card is completed with pending reward
Transaction is not the most recent
You lack permissions

Solution:

Wait for reward redemption
Contact admin for special cases
Verify your account permissions

"Transaction history not loading"

Possible causes:

Network connectivity issue
Large transaction volume
System maintenance

Solution:

Refresh the page
Check internet connection
Try again later
Contact support if persists

"Stamps don't match customer's claim"

Possible causes:

Customer confused with different program
Customer miscounted
Actual system error

Solution:

Show customer the transaction history
Explain each transaction
Verify against receipts if available
Add bonus stamps if genuine error

Next steps

Best Practices: Optimize your stamp card management
Monitoring Performance: Track program success
Creating Your First Program: Set up new stamp cards