# Resources overview (https://docs.chargeflow.io/docs/reference/overview) Resources is the lookup layer. The merchant and platform sections walk you through a job; this section holds the facts those guides link to, documented once so there is a single canonical answer. Nothing here is sequential. Come in from a link, get the answer, go back. ## What lives here [#what-lives-here] | Section | Who it is for | Read it when | | ----------------------------------------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [Start here](https://docs.chargeflow.io/docs/reference/start-here/product-model) | Anyone new to Chargeflow | You need the map before the details: the [product model](https://docs.chargeflow.io/docs/reference/start-here/product-model), the [transaction lifecycle](https://docs.chargeflow.io/docs/reference/start-here/transaction-lifecycle), and [the language of disputes](https://docs.chargeflow.io/docs/reference/start-here/language-of-disputes) | | [Concepts](https://docs.chargeflow.io/docs/reference/concepts/chargeback-lifecycle) | Anyone new to disputes | You need the vocabulary: the chargeback lifecycle, reason codes, network timelines, how alerts and automation work | | [API fundamentals](https://docs.chargeflow.io/docs/reference/api-fundamentals/authentication) | Developers | You are writing code: authentication, API keys, pagination, errors, rate limits, idempotency, the go-live checklist | | [Integrations](https://docs.chargeflow.io/docs/reference/integrations) | Merchants and platforms | You want to know whether Chargeflow connects to a processor, store, subscription, or support tool you already run | | [Tools](https://docs.chargeflow.io/docs/reference/tools) | Developers and agents | You want the OpenAPI spec, the Postman collection, SDKs, or the MCP server | | [Error codes](https://docs.chargeflow.io/docs/reference/error-codes) | Developers | A call returned something you did not expect | | [Security and compliance](https://docs.chargeflow.io/docs/reference/security) | Security and procurement reviewers | You are assessing how Chargeflow handles data | | [FAQ](https://docs.chargeflow.io/docs/reference/faq) | Everyone | You have a short question and want a short answer | | [Status](https://docs.chargeflow.io/docs/reference/status) and [Support](https://docs.chargeflow.io/docs/reference/support) | Everyone | Something looks broken, or you need a human | | [Changelog](https://docs.chargeflow.io/docs/reference/changelog) | Developers | You want to know what shipped and when | ## If you are here for one thing [#if-you-are-here-for-one-thing] Most readers arrive on one of these three paths: * **Making your first API call.** Start with [Authentication](https://docs.chargeflow.io/docs/reference/api-fundamentals/authentication), then the [API get started](https://docs.chargeflow.io/docs/api/2025-04-01/get-started) page. * **Debugging a response.** Go straight to [Error codes](https://docs.chargeflow.io/docs/reference/error-codes). * **Checking whether we support your stack.** Go to [Integrations](https://docs.chargeflow.io/docs/reference/integrations). ## Next step [#next-step] Learn the chargeback lifecycle first; every other page in this section assumes it. Already fluent in disputes and just here to build? Go to [API fundamentals](https://docs.chargeflow.io/docs/reference/api-fundamentals/authentication).