> For the complete documentation index, see [llms.txt](https://snowconedao.gitbook.io/snowconedao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://snowconedao.gitbook.io/snowconedao/build/utilities/splits-payer.md).

# Splits Payer

`SNOWETHERC20SplitsPayer` contracts make it easy to route funds to a group of splits from other contracts or within inheriting contracts. This is useful for routing funds to a number of Snowcone project treasuries and other addresses within other contracts such as an NFT marketplaces.

The `SNOWETHERC20SplitsPayer` can be inherited from any contract to facilitate internal transactions to split groups in AVAX or any ERC-20, assuming the projects in the split group are using a payment terminal that accepts the tokens. They can also be deployed as standalone splits payer copies using `SNOWSplitsPayerDeployer`.

**Inheriting SNOWSplitsPayer**[**​**](https://info.juicebox.money/dev/learn/risks/#inheriting-jbsplitspayer)

Inheriting from `SNOWETHERC20SplitsPayer` will give a contract access to a public `SNOWSplitsPayer.pay(...)` function, a public `SNOWSplitsPayer.addToBalanceOf(...)`function, and two functions `SNOWSplitsPayer._payToSplits(...)` and `SNOWSplitsPayer._payTo(...)`. These can be used from within the contract to route funds to a group of splits while specifying where leftover funds should go. Use the internal function if the inheriting contract has already handled receiving the funds being forwarded.

Follow instructions in Getting started to import the `SNOWSplitsPayer` files into a project.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://snowconedao.gitbook.io/snowconedao/build/utilities/splits-payer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.