---
title: "Inttegro Checkout"
description: "Use hosted checkout pages to collect payment without building and maintaining your own payment UI."
canonical: "https://studio.inttegro.com/products/checkout"
format: inttegro-machine-docs/v1
language: "Java"
sdk_version: "v8.3.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/java/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: 492
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["create_order"]
estimated_tokens: 2247
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Use hosted checkout pages to collect payment without building and maintaining your own payment UI. This Java representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

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

Use this product guide to understand behavior, boundaries, and lifecycle before choosing API operations.

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

This page is authoritative for product behavior and lifecycle intent. Linked API references define exact operations and data shapes.

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

Keep product behavior separate from transport details and confirm current capabilities before hard-coding market or lifecycle assumptions.

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

Yes, when the reader has an authenticated MCP connection and the task needs live context, guided planning, or a supported operation. The strongest matches are `create_order`; their exact roles and boundaries are listed below.

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

Confirm the chosen behavior against the linked guide and API operation, then verify the resulting resource state rather than relying only on UI presentation. Continue with [Payment method settings](https://studio.inttegro.com/machine/java/guides/understand-payment-method-settings.md) and [Order lifecycle](https://studio.inttegro.com/machine/java/guides/order-lifecycle.md) when those concerns enter scope.

### Recommended MCP assistance

Use these through an authenticated Inttegro MCP connection. This document remains the contract source.

- [`create_order`](https://studio.inttegro.com/machine/java/inttegro-mcp/tools.md#create_order) — action; exact user confirmation required. Creates an order for an existing customer from catalog product and price IDs. This tool never executes payment; finalize defaults to false.

## Document content

# Inttegro Checkout

Inttegro Checkout is the hosted payment experience for finalized orders and Buy links. It lets customers review what they are buying, choose a supported payment method, complete required confirmation, and receive a receipt without your application collecting payment credentials directly.

> Mcp Guide Callout is interactive content. Use the canonical page to view it.

Use this page to choose when hosted checkout fits. Use [Accept payment with Inttegro Checkout](https://studio.inttegro.com/machine/java/guides/accept-payment-with-inttegro-checkout.md) for implementation steps and [Orders](https://studio.inttegro.com/machine/java/api/orders.md) for the exact API contract.

## What Checkout does

Checkout turns a payable Inttegro resource into a customer-facing payment page.

| Resource | How Checkout uses it |
| --- | --- |
| Order | Shows the customer snapshot, line items, total, invoice, and payment state. |
| Invoice URL | Gives the customer a hosted payment page and printable record. |
| Payment method settings | Determines which payment methods can be shown and whether confirmation is required. |
| Customer details | Pre-fills known identity and delivery context when present. |
| Receipt | Confirms the final paid state after payment succeeds. |

Your server remains responsible for creating the order, storing returned IDs, and checking final status. Checkout owns the customer-facing payment UI.

## How the flow works

1. Your server creates an order and finalizes it, or creates a purchase intent that will create an order during hosted checkout.
2. Inttegro returns a hosted URL for the customer-facing payment experience.
3. You redirect the customer or send them the link through a trusted channel.
4. The customer reviews the order, selects a payment method, and completes any required confirmation.
5. Your application looks up the order and waits for a final payment state.
6. After payment succeeds, you fulfill the order and optionally send a receipt.

Do not treat a browser redirect as payment proof. Always verify the order through the API before fulfilling goods or services.

## When to use hosted checkout

Hosted checkout is the default choice when you want to ship quickly, reduce payment-surface risk, and avoid maintaining payment-provider-specific UI.

It fits especially well for:

- invoice-style checkout;
- Buy links and campaign links;
- mobile money payment confirmation;
- teams that do not want payment credentials in their frontend;
- merchants that need a printable customer invoice; and
- workflows where payment can happen after the order is finalized.

Build a custom checkout only when the payment UI must stay fully embedded in your product, when you need unusual multi-step business logic before payment starts, or when the customer experience cannot leave your domain.

## Invoice links and redirects

Finalized orders can expose hosted invoice formats, including a web URL and a PDF URL. Treat these links as sensitive customer data. They do not require your secret API key, and anyone who receives the link can view the invoice while it is usable.

Configure checkout redirects when creating or updating the order:

| Setting | Use |
| --- | --- |
| `checkout_settings.redirect_url` | Send customers back to your product after successful payment. |
| `checkout_settings.cancel_url` | Give customers a clear path when they cancel or abandon payment. |

Redirects improve customer experience, but they are not the settlement record. Use [Lookup an order](https://studio.inttegro.com/machine/java/api/orders.md#lookup-an-order) to confirm status.

## Status and confirmation

Order status and payment status are separate. An order can be finalized and still require payment; a payment can require customer action before it can finish.

When `payment.next_action` is present, show or send the required customer step. For mobile money, that may mean waiting for the customer to approve a prompt or submit a token. Poll at a reasonable interval, or refresh status when the customer returns to your product.

Use the order as the source of truth:

- `requires_payment` means the order still needs collection.
- `paid` means payment succeeded but fulfillment may not be complete.
- `completed` means your system has recorded fulfillment.
- `canceled` and `expired` are terminal outcomes.

## Where MCP helps

MCP is useful for assisted operations around hosted checkout:

- create a draft or finalized order from catalog product and price IDs;
- send an invoice link to the order customer after confirmation;
- look up the current order state; and
- render the order as a compact status card for support or sales teams.

MCP does not replace your checkout backend. Confirmed actions still require explicit approval, and the MCP `create_order` tool does not execute payment.

## Implementation checklist

Before relying on hosted checkout in production:

- create orders from your server, not from an unauthenticated browser;
- use stable idempotency keys for order creation;
- finalize orders before sending invoice links;
- configure `redirect_url` and `cancel_url`;
- store the order ID and invoice URL;
- verify payment status with order lookup before fulfillment;
- send receipts only after payment succeeds; and
- avoid logging invoice URLs in public analytics or client-visible traces.

## Related resources

- [Accept payment with Inttegro Checkout](https://studio.inttegro.com/machine/java/guides/accept-payment-with-inttegro-checkout.md) - Step-by-step hosted checkout integration.
- [Orders API reference](https://studio.inttegro.com/machine/java/api/orders.md) - Order creation, payment, invoice, and fulfillment contracts.
- [Purchase intents](https://studio.inttegro.com/machine/java/products/purchase-intents.md) - Product-specific Buy links that use hosted checkout.
- [Order lifecycle](https://studio.inttegro.com/machine/java/guides/order-lifecycle.md) - How orders move from draft to paid, completed, canceled, or expired.
- [Payment method settings](https://studio.inttegro.com/machine/java/guides/understand-payment-method-settings.md) - Which payment methods are available to checkout.