Stand up an HTTPS endpoint that accepts POST requests from Toast and can handle high concurrency; submit the endpoint URL to Toast support for configuration in the sandbox environment
Implement handlers for at least the GIFTCARD_REDEEM transaction type, which applies a gift card balance to a check, and GIFTCARD_REVERSE, which rolls back a redemption
For each inbound request, validate the request signature or shared secret provided by Toast before processing any balance change
Return a well-formed JSON response with the updated gift card balance and a success or failure status code so Toast can complete or void the tender on the check
Test the integration with 10 or more concurrent gift card redemptions in the sandbox before requesting production approval
Log all inbound requests and responses for audit purposes; gift card financial transactions require a reliable reconciliation trail
Known gotchas
This is an outbound integration model — Toast calls your endpoint, not the other way around; you host the gift card balance authority
GIFTCARD_REVERSE must be idempotent; Toast may retry reversals if your endpoint times out, so guard against double-reversals with a transaction ID check
Sandbox and production endpoint URLs are configured separately; confirm the correct URL is active in each environment before testing
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