> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/faqs/test-att-faqs/commerce-and-billing-faq.md).

# Commerce & Billing FAQ

Financing, taxes, promos, billing cycles, and money flow.

### Quick answers

<details>

<summary>What are financing terms? How does it work?</summary>

Reach is not a lender.

Reach does not set financing terms.

Financing is offered through third-party financing partners integrated into checkout.

How it works:

* financing options show during checkout, when enabled
* the customer picks an option
* the financing partner handles:
  * credit checks and eligibility
  * repayment terms, including APR, tenure, interest, and collections

Reach:

* runs the checkout flow
* records the transaction outcome for orders and reporting

The brand:

* contracts directly with the financing provider
* decides which products and plans are eligible

Financing terms are owned by the financing partner and the brand.

</details>

<details>

<summary>How are taxes calculated?</summary>

Reach calculates taxes using external tax engines.

During checkout:

* Reach sends transaction details (items, prices, ship-to / service location)
* the tax engine returns the applicable taxes
* Reach displays the calculated taxes to the customer

Tax rules, exemptions, and compliance configuration are owned by the brand.

</details>

<details>

<summary>How does money flow?</summary>

Payments are processed through the configured payment gateway or financing provider.

Reach records transaction confirmations to update orders and reporting.

Settlement flow depends on your contracted setup with the providers.

Reach is transaction-aware.

Reach is not a bank or a lender.

</details>

<details>

<summary>How does the promo system work? What promos can be enabled?</summary>

Reach includes a rules-based promotion engine.

Common promo types include:

* percentage discounts
* flat amount discounts
* device-specific promos
* plan-based promos
* cart-level promos
* promo / coupon codes
* agent-only promos
* financing-linked promos (when supported)

Promos can be configured with:

* start and end dates
* eligible channels (Web, App, Agent)
* stackable vs non-stackable rules
* customer eligibility criteria

Promos are configured in Reach.

Promos are defined and approved by the brand.

</details>

<details>

<summary>How do billing cycles work?</summary>

Billing cycles are defined by the brand.

Reach typically supports:

* monthly billing cycles
* one-time charges
* recurring charges
* mid-cycle plan changes applied on the next cycle (standard behavior)

Reach:

* calculates charges using configured billing rules
* generates billing records and reports

The brand:

* owns invoicing and statements
* owns collections and payment follow-up

{% hint style="info" %}
Proration is not supported in the standard billing configuration.
{% endhint %}

</details>


---

# 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.reachplatform.com/faqs/test-att-faqs/commerce-and-billing-faq.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.