# Billing Product Family

## How to use this document

Use this page after [Product Decision](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/product-decision.md) selects Billing. Start with the section matching the requested billing scenario, resource, or operation; the sections are not a required reading sequence.

- For questions about Billing capabilities and business value, use [Product Introduction](#product-introduction).
- For a billing workflow, match the described charging model in [Billing Scenarios](#billing-scenarios), then read only the selected scenario overview.
- For a specific resource or Dashboard feature, use [Resources and Features](#resources-and-features). Questions or operations involving a single resource do not require choosing a billing scenario.
- For a named API or notification field question, read its contract directly. If the document URL is unknown, use the [API index](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/api/index.md) or [Billing Notifications](#billing-notifications). Before writing or modifying code that relies on asynchronous notifications to confirm business results or handle asynchronous errors, or configuring notification URLs, follow Billing Notifications to select the required documents.
- Choose a [Payment Integration Mode](#payment-integration-modes) only when subscription activation or payment collection affects the answer or implementation. For a selected scenario, follow its scenario-specific integration path.

For a complete workflow, start with the scenario and add resource, API, or notification documents only as required by the current stage. For general explanations, stop when the question is answered; do not load SDK or sample-code unless the question concerns them. For implementation, also follow [Code Examples and Required References](#code-examples-and-required-references).

For relationships between Billing resources, read [Resource Relationships](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/resource-model.md), then only the resource documents needed for the question.

## Product Introduction

Antom Billing manages what is sold, how it is priced, who is billed, and how recurring or usage charges, invoices, discounts, credits, and tax are handled.

For product scope and business value, read the relevant official introduction:

- Recurring billing: [Subscription overview](https://docs.antom.com/ac/billing/subscription_overview.md).
- Invoice billing: [Invoices overview](https://docs.antom.com/ac/billing/invoices_overview.md).

Read both only when the question covers both. For a specific scenario, resource, or operation, go directly to the matching section below.

## Billing Scenarios

Match the charging model using the table below, not by reading each scenario document. Choose by commercial model, not API name.

| Merchant requirement | Scenario |
| --- | --- |
| Fixed recurring amount | [Fixed-rate Subscription](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/scenarios/fixed-rate-subscription/overview.md) |
| Recurring price by seat | [Per-seat Subscription](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/scenarios/per-seat-subscription/overview.md) |
| Meter usage at one rate | [Pure usage-based](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/scenarios/pure-usage-based/overview.md) |
| Licensed quantity tiers | [Order quantity tiered](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/scenarios/order-quantity-tiered-pricing/overview.md) |
| Meter usage tiers | [Tiered usage-based](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/scenarios/tiered-usage-based/overview.md) |
| Recurring free tier, then usage | [Free tier + usage](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/scenarios/free-tier-usage/overview.md) |
| Fixed fee plus metered overage | [Base fee + overage](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/scenarios/base-fee-overage/overview.md) |
| Metered Subscription plus purchased credit | [Usage + prepaid credit](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/scenarios/usage-prepaid-credit/overview.md) |
| Billing catalog or hosted one-time Invoice | [One-time Billing payment](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/scenarios/one-time-payment/overview.md) |

If the information is insufficient to select a scenario, ask one question about the charging model that distinguishes the relevant rows. Do not force a requirement outside the table into a listed scenario.

Without Billing lifecycle needs, route ordinary one-time charges in One-time Payments and recurring membership in Subscription Payment.

## Resources and Features

Choose the resource or feature relevant to the question or operation. Each linked page directs you to the relevant product, Dashboard, or API document. Read only the needed links in a row; add another resource only when its relationship is needed to explain the behavior or implement the operation.

| Need | Load |
| --- | --- |
| Catalog and pricing | [Product](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/product.md), [Price](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/price.md) |
| Identity and self-service | [Customer](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/customer.md), [Customer Portal](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/customer-portal.md) |
| Recurring lifecycle | [Subscription](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/subscription.md) |
| Usage and credit | [Meter](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/meter.md), [Credit Grant](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/credit-grant.md) |
| Billing, adjustment, and records | [Invoice](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/invoice.md), [Credit Note](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/credit-note.md), [Receipt](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/receipt.md) |
| Discounts | [Coupon](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/coupon.md), [Promotion Code](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/promotion-code.md) |
| Asynchronous outcomes | [Notifications](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/notifications.md) |
| Tax | Use the [API index](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/api/index.md) |

## Payment Integration Modes

For subscription activation, choose by how the Subscription is created, not who collects card information.

| Merchant flow | Path |
| --- | --- |
| Antom checkout creates the Subscription through a Payment Session | [CKP](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/integration-modes/ckp.md) |
| Backend independently creates the Subscription, then initiates Pay when required | [Direct API](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/integration-modes/direct-api.md) |
| Hosted `SEND_INVOICE` payment | [Invoice channel](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/integration-modes/invoice-channel.md) |

An Antom-hosted card page or 3DS alone does not select CKP. Direct API also supports Antom-hosted card collection through its payment Profile.

For one-time payments or prepaid-package purchases, follow the selected scenario's payment route instead of the Subscription activation rules.

If a required path is unknown, ask one concise question. Invoice generation alone does not select Invoice channel.

When a scenario and path are selected, load the scenario-specific path first. A general mode page only selects shared official flow knowledge; it never replaces that path or mixes Create Payment Session with Pay.

## Billing Notifications

Before writing or modifying Billing code that relies on asynchronous notifications to confirm business results or handle asynchronous errors, read Notification Processing Rules in the [Billing Notifications guide](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/capabilities/notifications.md). Identify the current stage from the selected scenario's workflow or the requested operation, then use Select By Current Stage in that guide to read the matching primary notification contracts and any conditional contracts whose conditions apply. Do not load unrelated notification contracts. For a multi-stage implementation, select notifications separately for each stage.

- To identify a notification from a supplied sample, use the guide's `notifyType` tree and matching contract. In a live receiver, verify the signature before trusting the notification or performing business actions. The selected scenario and contract determine the business action.
- To configure notification delivery, use the guide's Notification URL Configuration section and the contract for the operation that sets the URL.
- For a specific notification field question, the contract can be read directly; add the guide when shared handling rules are relevant.
- Synchronous CRUD and queries do not require notifications merely because they belong to Billing. Meter upload needs `notifyEvent` for asynchronous processing failures.

## Code Examples and Required References

For implementation, use the selected scenario overview and its path when activation or collection applies, or the relevant resource guide or API document for an individual operation. Load [SDK Description](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/select-sdk.md), then [Billing Sample-Code Index](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/sample-code/index.md). From there, select one language index, its linked SDK Basics, and one exact sample per stage. Recurring Subscription Direct API additionally requires exactly one payment Profile from that language index; One-time Direct Pay uses the One-time Payments route instead. Read [FAQ (Coding)](https://cdn.marmot-cloud.com/page/antom-integration-doc/troubleshoot/faq-coding.md) and complete coding gates.

Related API References are available for contract details, not as a mandatory load list. Without an exact sample, use exact operations and the confirmed SDK.

When notification handling applies, follow [Billing Notifications](#billing-notifications).

Stop loading when the selected scenario or operation, language, sample, and result or failure handling are clear. A payment path and notification handling are required only when they apply to the scenario or operation being implemented.