Ridgeway Supply takes card payments through Paylink. When a payment settles, Paylink calls Ridgeway's callback and Ridgeway marks the order paid.
Paylink signs every callback with a timestamp and a MAC over the body. Ridgeway's integration guide has a section on testing against the callback without a live payment.
Order RW-2026-0441 is live and unpaid. The request below is a real Paylink callback you captured five days ago from a test purchase you made and refunded.
One change to this request triggers the vulnerability. The challenge is to use your security intuition to work out what to change. Find the value the server shouldn’t trust, change it, and send it. The response tells you whether you were right.
Hint. Mark order RW-2026-0441 paid without paying for it.
“A callback that verifies signatures is a callback that requires them.”
Treat a missing signature as a failed one and refuse. Give the sandbox its own endpoint, its own credentials and its own order store, so that a test callback cannot reach a live order whatever it says. Add a test that posts an unsigned callback for a live order and expects a refusal rather than a state change.
Anywhere verification has an else branch: unsigned requests treated as test traffic, a development mode enabled by the absence of a header, an API that accepts either signed or unsigned callers for backwards compatibility, a MAC checked only when the field is present. The pattern is the same as an optional CSRF token or an optional nonce. Before spending time on a signature, send the request without one and see which handler answers.
One Request Away is a daily series of challenges. They’re like code review, but for HTTP requests: in each one you’re one request away from triggering a vulnerability, and your goal is to identify what you need to change.