Ramp Sandbox and Production Isolation

Overview

Make environment selection a typed security boundary. Keep credentials and data from crossing it, verify resolved hosts before token exchange, and require an explicit interlock before production writes.

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 sandbox uses demo.ramp.com and demo-api.ramp.com; production uses app.ramp.com and api.ramp.com.
• Tokens are valid only in the environment where issued, and sandbox and production applications have independent credentials and settings.
• Production Embedded Cards origins must be exact verified HTTPS origins; localhost is not accepted for production integrations.
• Sandbox cannot move real money, but its successful behavior does not prove production authorization or data equivalence.