---
title: "Demo applications"
description: "Explore complete Inttegro integrations for popular languages, frameworks, and mobile stacks."
canonical: "https://studio.inttegro.com/demos"
format: inttegro-machine-docs/v1
language: "C#"
sdk_version: "v10.3.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/csharp/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 347
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 848
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Explore complete Inttegro integrations for popular languages, frameworks, and mobile stacks. This C# representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Demo applications?

Use this demo guide to inspect a complete working integration and compare it with the application being built.

#### Q2. What is authoritative on this page?

The demo proves one working composition, not the only supported architecture. Follow its linked SDK and API pages for current contracts.

#### Q3. What page-specific constraint matters most?

Do not copy demo credentials, identifiers, or deployment assumptions. Recreate configuration through supported public setup paths.

#### Q4. Can Inttegro MCP materially help with this task?

No catalog ability is sufficiently specific to recommend for this page. Use the documentation directly; consult the MCP catalog only if the task later requires governed live account context or a supported operation.

#### Q5. How should the reader verify the answer and continue?

Open the hosted experience, trace the corresponding source, and verify that its SDK and API usage still matches the current linked documentation. Continue with [Official SDKs](https://studio.inttegro.com/machine/csharp/sdks.md) when those concerns enter scope.

## Document content

# Demo applications

See Inttegro Checkout working in the stack you use. Open a live demo, read the
source, or deploy your own.

> Demo Release Overview is interactive content. Use the canonical page to view it.

Every demo keeps the API key and order creation on the server. Web demos show
embedded, modal, and hosted Checkout. Mobile demos show the native payment
sheet.

Keep `INTTEGRO_API_KEY` on the server. Never put it in browser or mobile code.

> Demo Catalog is interactive content. Use the canonical page to view it.

## Run a demo

Choose a framework below, then use its Docker or cloud link. You will need an
Inttegro API key and active Product and Price IDs. Each README has the exact
setup commands.

## Reference

- [Released demo suite](https://github.com/inttegro/inttegro-demos/tree/v1.8.3)
- [Demo acceptance contract](https://github.com/inttegro/inttegro-demos/blob/v1.8.3/CONTRACT.md)
  — shared server and mobile behavior
- [Mobile boundary and device checks](https://github.com/inttegro/inttegro-demos/blob/v1.8.3/MOBILE.md)
  — backend ownership and device verification
- [Official SDKs](https://studio.inttegro.com/machine/csharp/sdks.md) — installation and source