Transactions

Overview

Transaction history is a paginated audit trail of loyalty events for each member.

It includes purchases, earnings, redemptions, and adjustments generated by platform processing.

For exact retrieval operations, use the API Reference.

Typical Usage

Use transaction history for:

• Member timeline views
• Support investigations
• Financial and rewards reconciliation

Pagination

History retrieval supports standard paging and ordering controls as documented in the API Reference.

Cancellation Behavior

If a previously rewarded purchase is cancelled, Otonum applies a compensating adjustment to reverse associated rewards.

This can produce temporary negative balance values, which should be handled gracefully in member-facing interfaces.

Key Points

• History is read-only from the API perspective
• Adjustments appear as separate transaction entries
• Cancellation does not retroactively alter unrelated reward events

See Also

• Recording Activities: Activity submission semantics
• Task Status: Async processing visibility
• Best Practices: Idempotency and resilience