Authenticate to the Transact IDX or campus commerce API using the institution's API credentials (OAuth 2.0 client credentials or API key depending on deployment)
GET the student account endpoint with the student's campus ID or patron ID to retrieve current meal plan balances, declining balance totals, and plan type
Validate the student's meal plan enrollment status and identify the target account category (e.g., dining dollars vs. meal swipes)
POST to the account deposit or value-add endpoint with the student ID, account category, amount, and a transaction reference ID for idempotency
Verify the transaction response includes a confirmation number and updated balance reflecting the new funds
Log the transaction reference ID and poll or webhook-listen for any reversal events within the settlement window
Known gotchas
Transact's API surface differs significantly between the legacy TMS platform and the newer IDX platform — confirm which platform version the institution is running before building the integration
Duplicate deposits can occur if the client retries a request without checking for an existing confirmation number; use a caller-supplied idempotency key or transaction reference in every POST
Meal swipe accounts are typically count-based (not monetary) and cannot be topped up via a value-add API; only declining balance or dining dollar accounts accept monetary deposits programmatically
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp