> For the complete documentation index, see [llms.txt](https://docs.learncard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.learncard.com/build/go-to-production/test-safely.md).

# Test Safely: Staging & Mock Recipients

Before issuing credentials to real users, you should test your integration safely. LearnCard provides several mechanisms to test issuance without sending unwanted emails or SMS messages to real users.

{% hint style="info" %}
**\~5 min** · After the [Quickstart](/start-here/your-first-integration.md).
{% endhint %}

## Environments

To see a staging project in the staging app: `npx @learncard/cli open --network staging` (the `.env` in that folder must already be on staging).

Staging and production are separate networks — nothing below carries over between them; see [What carries over](#what-carries-over).

| Item                     | Staging                                            | Production                                  |
| ------------------------ | -------------------------------------------------- | ------------------------------------------- |
| App                      | `https://staging.learncard.ai`                     | `https://learncard.app`                     |
| Network API (tRPC)       | `https://staging.network.learncard.com/trpc`       | `https://network.learncard.com/trpc`        |
| REST base                | `https://staging.network.learncard.com/api`        | `https://network.learncard.com/api`         |
| Storage API (LearnCloud) | `https://staging.cloud.learncard.com/trpc`         | `https://cloud.learncard.com/trpc`          |
| Developer Portal         | `https://staging.learncard.ai/app-store/developer` | `https://learncard.app/app-store/developer` |

## Use the staging network

The LearnCard Network provides a fully separate staging environment — see [Environments](#environments) above for the URLs. Profiles, API tokens, signing authorities, templates, and credentials are per-network and do not mirror between staging and production; see [What carries over](#what-carries-over).

To connect to the staging network using the SDK, pass the staging URLs to `initLearnCard`:

```typescript
import { initLearnCard } from '@learncard/init';

const learnCard = await initLearnCard({
    seed: process.env.SECURE_SEED,
    network: 'https://staging.network.learncard.com/trpc',
    cloud: { url: 'https://staging.cloud.learncard.com/trpc' },
});
```

{% hint style="warning" %}
**`network` doesn't move storage.** `network` and `cloud.url` are independent options — `cloud.url` defaults to the **production** LearnCloud endpoint (`https://cloud.learncard.com/trpc`) no matter what you pass to `network`. If you only set `network` to staging, credential storage still goes through production LearnCloud. Set both to stay fully on staging.
{% endhint %}

If you are using the LearnCard CLI, you can specify the network using the `--network` flag:

```bash
learncard send --network https://staging.network.learncard.com/trpc
```

The CLI's `send` command only exposes `--network`, not a `--cloud` equivalent — it moves where credentials are issued, not where they're stored.

## Suppress delivery

`suppressDelivery` skips only the notification message (the claim email or SMS) — it is **not** a dry run. The network still creates a real, pending inbox credential addressed to that recipient and still returns `result.inbox.claimUrl`. If that email or phone number later verifies against a LearnCard profile, the recipient can claim it like any other credential.

```typescript
const result = await learnCard.invoke.send({
    type: 'boost',
    recipient: 'test@example.com',
    // from createBoost() — the "network.learncard.com" host ties this template to
    // production; a template created on staging would use a staging host instead.
    templateUri: 'lc:network:network.learncard.com/trpc:boost:abc123',
    options: {
        suppressDelivery: true,
    },
});

console.log('Claim URL:', result.inbox?.claimUrl);
```

{% hint style="warning" %}
**On production, this is a real issuance.** `suppressDelivery: true` only silences the email/SMS — it doesn't sandbox the send. Prefer the [staging network](#use-the-staging-network) or your own address for test sends rather than relying on `suppressDelivery` alone to avoid issuing to a real recipient.
{% endhint %}

You can then manually open the `claimUrl` to verify the recipient experience.

## Use your own email

The simplest way to test delivery is to send credentials to your own email address or phone number. The LearnCard Network will auto-detect the recipient type and route the message accordingly.

## Mock mode for embedded apps

If you are building an embedded application using Partner Connect, you can use mock mode to test your app without connecting to a real host. See [Publish Your App](/build/publish-your-app.md) for details on configuring mock mode.

## What carries over

| Per-network — redo this on every network                                           | Portable — the same everywhere |
| ---------------------------------------------------------------------------------- | ------------------------------ |
| Profile & profile ID                                                               | Your seed → the same `did:key` |
| API tokens                                                                         | Your integration code          |
| Signing authority registrations                                                    |                                |
| Credential templates (the `lc:network:<host>/…` in the URI ties it to one network) |                                |
| ConsentFlow contracts                                                              |                                |
| Issued & claimed credentials                                                       |                                |

A `did:web` profile is the one exception on the portable side — unlike a seed-based `did:key`, its DID embeds the host, so it doesn't carry over between networks either.

## What you should see

When using `suppressDelivery: true`, the API response will include `inbox.claimUrl` but no email or SMS will be sent to the recipient. When using the staging network, credentials will appear in the staging LearnCard App at `https://staging.learncard.ai`, not in the production app at `https://learncard.app`.

## Troubleshooting

| If…                            | Then                                                                                                            |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------- |
| `Profile not found` on staging | You need to create a new profile on the staging network. Profiles do not carry over from production.            |
| `UNAUTHORIZED` on staging      | You are using a production API token. Generate a new one from **Developer Tools** in the staging LearnCard App. |

## Next steps

* [Go to Production](/build/go-to-production.md)
* [Publish Your App](/build/publish-your-app.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.learncard.com/build/go-to-production/test-safely.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.