---
title: "About Inttegro"
description: "What Inttegro is and how its commerce API fits together."
canonical: "https://studio.inttegro.com/about"
format: inttegro-machine-docs/v1
language: "Python"
sdk_version: "v12.0.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/python/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: 417
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 1369
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** What Inttegro is and how its commerce API fits together. This Python representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use About Inttegro?

Use this page as orientation before selecting the narrower guide or reference that owns the implementation contract.

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

Use this page for orientation; follow its canonical SDK, guide, API, or MCP links for exact contracts.

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

Use the page to choose a canonical next source instead of treating summary material as a complete implementation contract.

#### 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?

Select the narrowest linked guide or reference, apply its stated completion condition, and verify against authoritative resource state when the task changes data. Continue with [Connect an AI agent Use MCP when you want an authenticated AI client to inspect commerce data or perform confirmed actions.](https://studio.inttegro.com/machine/python/inttegro-mcp.md) and [Design a checkout flow Understand hosted checkout before deciding whether to use Inttegro's checkout page or build a custom payment experience.](https://studio.inttegro.com/machine/python/products/checkout.md) when those concerns enter scope.

## Document content

# About Inttegro

Inttegro is commerce infrastructure for teams that need to accept payments,
manage orders, track money movement, and communicate with customers through one
API.

It gives your application durable records for the parts of commerce that need
to be correct: customers, payment methods, orders, products, prices, balances,
payouts, financial accounts, files, and customer messages. Those records let
you build checkout flows, invoices, payout operations, account dashboards, and
support tools without inventing a separate payment backend for each workflow.

## What Inttegro helps you build

- Payment flows for mobile money, hosted checkout, and saved payment
  methods.
- Order workflows that preserve line items, payment state, receipts, invoices,
  and lifecycle history.
- Catalog workflows for products, prices, and buy links.
- Payout workflows that connect merchant balances to real-world bank accounts
  and mobile money wallets.
- Customer communication flows for OTPs, transactional messages, scheduled
  notifications, and broadcasts.
- File workflows for uploads, public file links, and resources that need to be
  attached to commerce records.

## How the pieces fit together

Most integrations start with orders. An order describes what the customer is
buying, how much it costs, and whether payment should happen now or later.
Payment methods let Inttegro charge the customer. Balances and balance
transactions show how the resulting money moves inside Inttegro. Payouts move
available funds from your balance to configured financial accounts.

Product and price records help you reuse catalog data instead of recreating
line items by hand. Customer records let you attach payment methods, contact
channels, and commerce history to the same buyer over time. Communication and
file APIs support the surrounding operational work: receipts, reminders,
verification, uploads, and customer-facing resources.

## Where Studio fits

Studio is the working reference for Inttegro. Use it when you need to understand
the product model, copy SDK-native examples, inspect endpoint parameters, or
give an AI agent a precise link to the behavior you want it to follow.

## Choose your next step

Pick the path that matches what you are trying to do now. [Make your first request
Start here if you want the shortest path from API key to a working Inttegro API call.](https://studio.inttegro.com/machine/python/quickstart.md) [Learn how Studio is organized
Use The Inttegro API landing page to understand products, guides, references, SDKs, and automation-friendly links.](https://studio.inttegro.com/machine/python/index.md) [Design a checkout flow
Understand hosted checkout before deciding whether to use Inttegro's checkout page or build a custom payment experience.](https://studio.inttegro.com/machine/python/products/checkout.md) [Connect an AI agent
Use MCP when you want an authenticated AI client to inspect commerce data or perform confirmed actions.](https://studio.inttegro.com/machine/python/inttegro-mcp.md)