So, here, their service on Amazon responds with a 200, but has a `status_code: 500` in the body. That's stupid, but OK.
A `riskified` field wasn't filled out in some request it made. The Pi-Hole blocks beacon.riskified.com. So disabling the Pi-Hole for a few minutes and redoing the form got me through it.
I guess this is my fault? I'll accept that, but I still contend the web typically has way too much complexity and shittiness these days. Call riskified on your own time in your lambda or something.