2Checkout沙箱账号INS推送失败问题咨询（已关闭Demo模式）

I’ve dealt with similar frustrating issues with 2Checkout’s sandbox environment before, so I know how stuck you must feel right now. Let’s walk through potential fixes and explanations for why your Instant Notification Service (INS) is still landing in the failure zone even after disabling Demo Mode:

• Verify every detail of your sandbox webhook setup
  Even with Demo Mode off, tiny configuration mistakes can derail INS delivery. Double-check:

  • Your sandbox endpoint URL matches your production working URL exactly—no typos, HTTP/HTTPS mismatches (sandbox typically enforces HTTPS for testing endpoints).
  • Your server whitelists 2Checkout’s sandbox IP ranges. Firewalls or security plugins often block sandbox traffic that isn’t explicitly allowed.
  • You’re using the sandbox-specific secret key for INS signature validation. Mixing production and sandbox keys will cause validation failures, automatically pushing notifications to the failure zone.

• Use 2Checkout’s sandbox INS simulator for targeted testing
  The 2Checkout sandbox dashboard has a built-in tool to send test INS requests directly. Trigger a test notification and monitor your server logs in real time. If the test fails, your logs should show specific errors—like timeouts, invalid signatures, or unreachable endpoints—that pinpoint the problem.

• Check for sandbox-specific service issues
  While 2Checkout hasn’t publicly announced discontinuing sandbox INS, some accounts run into isolated bugs or backend glitches in the sandbox environment that break delivery. Reach out to their support team with your sandbox account ID and copies of your failure logs—they might have internal notes about ongoing issues affecting specific accounts.

• Rule out server-side response delays
  If production works but sandbox doesn’t, check if your sandbox environment has slower response times. 2Checkout’s sandbox expects a 200 OK response within a tight window (usually 10 seconds). If your server takes too long to process sandbox INS requests, the system will mark them as failed. Add logging to track how long your server takes to respond to sandbox notifications.

To directly answer your question: 2Checkout hasn’t formally stopped sending INS to sandbox accounts—many developers still use it successfully. Your working production INS confirms your core setup is correct, so this is almost certainly a sandbox-specific issue tied to your account’s configuration or a temporary backend glitch.

内容的提问来源于stack exchange，提问作者Manoj Mohan