configure nayax spark api webhook callbacks to track remote pos transaction state without polling
domain: developerhub.nayax.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Provision your Spark server-to-server integration through Nayax's onboarding/sandbox process and register the callback endpoints Nayax will call
Implement a TransactionCallback endpoint to receive the outcome of a completed TriggerTransaction request
Implement a DeclineCallback endpoint to handle cases where the transaction fails after TriggerTransaction succeeded (e.g. the consumer cancels on the device or the terminal times out)
Implement TimeoutCallback and StopCallback endpoints to detect a session that timed out or was stopped by a card being presented
Optionally ask your Nayax Integration Support Engineer to enable up to two static custom headers (shared secret/routing ID) on every callback for verification
Known gotchas
custom header enablement is a manual request through your Nayax Integration Support Engineer / Backoffice, not a self-service API call
these callbacks belong to the Spark server-to-server payment API; they are a separate mechanism from Lynx's machine/inventory health alerting
without implementing DeclineCallback specifically, a consumer-cancelled or timed-out transaction can leave your system believing a TriggerTransaction is still pending
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?