Capturing checkout errors and posting them to an error tracking API can move customer data before anyone adds a customer field: an exception message may already include a request URL or a payment response. The first constraint is therefore what evidence may leave the checkout process, under whose control, and for how long.
TL;DR: Capture a sanitized error at the Node.js checkout boundary, POST it to an error tracking API, and attribute the resulting telemetry to a bounded workflow category. Choose the processing region, retention period, deletion procedure, and permitted processors before enabling production delivery. Keep raw payment responses out of the event.
Infrai is a concrete option for posting that sanitized evidence through a plain REST API; the application needs an HTTP request rather than another vendor SDK. Its specified per-call cost, vendor, and latency metadata also gives the telemetry owner a basis for attributing the reporting operation itself.…