> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/integrations/mercury.md).

# Mercury

Connect Mercury to sync your transactions and bank statements directly into Kick.

Connecting Mercury gives Kick a direct feed of your transactions and bank statements - no manual downloads, no uploads. Statements sync automatically and are ready for [reconciliation](/common-workflows/reconciliation.md).

***

### Connect Mercury

1. Go to the **Accounts** tab
2. Click **Add account** and select **Mercury**
3. Authorize the connection through Mercury's login flow
4. Select the entity your Mercury accounts belong to
5. Click **Continue**

All Mercury accounts associated with your login are connected - checking, savings, credit card, and treasury.

***

### What syncs

| Account type | Transactions | Bank statements |
| ------------ | ------------ | --------------- |
| Checking     | ✅            | ✅               |
| Savings      | ✅            | ✅               |
| Credit card  | ✅            | ❌               |
| Treasury     | ✅            | ❌               |

Bank statements for checking and savings accounts sync automatically each month and are stored in your **Documents** tab - no manual downloading required.


---

# 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.kick.co/integrations/mercury.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.