Sandbox trial

Which settlement modes you can use in sandbox, and how to arm conformance outcomes. Your first request is covered on Getting started.

Start with Getting started

If you haven't completed a sandbox redemption yet, follow Getting started first. It covers access, your key, the status check, one redemption and one poll.

Settlement mode availability

Mode

Availability

Sandbox behavior

Mode 1

Live

Default simulated delegated-signing redemption and swap path.

Mode 2

Live

Redemption and mixed Mode 1/2 swaps for issuers with simulated profiles.

Mode 3

Design

Pre-burn recovery machinery required before initiation is enabled.

The mode comes from each issuer's capability profile. See Settlement modes.

Getting Mode 2

You can't pick Mode 2 in your request. Issuers declare an ON_INSTRUCTION profile through Issuer capability declaration during onboarding, and the mode follows automatically.

Conformance outcomes

Once a happy-path redemption works, arm the rejection, failure and silence scenarios to check that your integration handles every saga path. Tenant admins with a JWT session (runOwnConformancePack) can arm outcomes on their own transactions. Machine API keys can't. None of this exists in production.

Conformance testing has the full harness documentation: who can arm, what the adapter returns and the pass criteria.

Current trial limits

Mode 3 initiation needs full recovery machinery. See Mode 3.
Whether you're on Stellar Testnet, Polygon Amoy or Solana Devnet depends on how your participant's adapter is configured. You can't switch networks from the client.