> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/upcoming-changes/consumer-fee-control-and-exact-net-settlement.md).

# Consumer Fee Control and Exact Net Settlement

> **Superseded.** The feature previously described on this page was replaced during development. The fields `consumerFeeAmount`, `consumerFeePercentage` and `splitConfiguration`, the `feeBreakdown` response object, and the `StandardProcessing`, `ExactNetSettlement` and `ConsumerFee` settlement models were not implemented and are not part of the API. Do not build against them.

### What replaced it

The requirement that drove this work, a merchant receiving an exact settlement amount while fees are recovered elsewhere, is met by the [Split Funding Program](https://developers.bead.xyz/split-funding.md).

The approach changed in two ways worth understanding if you reviewed the earlier design:

**Explicit amounts instead of calculated fees.** Rather than passing a fee amount or percentage and having Bead derive the split, your integration passes three explicit dollar amounts on the payment: what the consumer pays, what the merchant keeps, and what is withheld for the partner. Bead performs no rate calculation, which removes the rounding and configuration mismatch problems the earlier design was trying to solve.

**Withholding and periodic distribution instead of routing at settlement time.** Rather than routing a surcharge to a separate destination account at settlement time, Bead withholds the partner's portion at settlement and pays it to the partner as a single periodic bank transfer covering all of their merchants, net of a per payment fee.

**Two destinations, not arbitrary routing.** The earlier design implied a configurable destination. The program that replaced it funds exactly two accounts, fixed by role: the merchant's account on file and the partner's account on file. There is no payee selection on a payment. See [Two destinations, fixed by role](https://developers.bead.xyz/split-funding.md#two-destinations-fixed-by-role).

The outcome for the merchant is the same. They receive exactly the amount specified, with no transaction fee deducted and nothing billed back to them later.

### What to do now

* If you were planning an integration against this page, read [Split Funding Program](https://developers.bead.xyz/split-funding.md) instead.
* For reporting and reconciliation, see [Split Funding Reports](https://developers.bead.xyz/split-funding/reports.md).
* Contact your Bead integration contact to discuss enrollment and partner payout setup.


---

# 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://developers.bead.xyz/upcoming-changes/consumer-fee-control-and-exact-net-settlement.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.
