Sanitized Ramp Support Bundle

Overview

Create an evidence package that Ramp support and internal responders can use without exposing credentials, card details, receipts, or unnecessary employee and financial data.

Prerequisites

• Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary.
• Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation.
• Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved.
• Prepare approved secret storage and a sanitized evidence location.

Current Contract

• Ramp responses include x-trace-id, the preferred correlation handle for developer support.
• API error bodies may include error_v2.error_code, additional information, and a message.
• Webhook and deferred-task incidents need delivery/task identifiers and lifecycle state, not copied secrets or full payloads.
• Authorization failures require environment, grant, and scope metadata, but never the bearer token or client secret.