> For the complete documentation index, see [llms.txt](https://docs.chargebackstop.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chargebackstop.com/developer/partner-integration-guide/integrating-with-chargebackstop.md). # Integrating with ChargebackStop ChargebackStop for Partners has extensive API and webhook capabilities. ## Terminology To understand how our API and platform work, it helps to learn these terms and their relationships. ### Partner Your partner account. * In production, you’ll typically only have one. ### Organisation An organisation within your partner account. * We recommend setting separate organisations for all your customers. ### Membership A membership of a user within an organisation. * This enables your customers to log in to their organisation. * If your integration does not include your customers logging into ChargebackStop platform in any form (including whitelabel solutions), you will not need to create any memberships. ### Merchant A merchant account within an organisation. * If your customer has multiple merchant accounts with payment processors, create a separate merchant account for each one. * When creating a new merchant, we strongly recommend passing `external_id` as their MID, CAID, or provider account ID. It helps you differentiate merchant accounts later on. ### Integration A connection with a data source (e.g. payment processor such as Stripe, Adyen, Shopify, etc.), or a custom orders integration if you decide to push orders to ChargebackStop using the [Orders API](/developer/api-documentation/orders.md). * Integrations allow ChargebackStop to match incoming alerts to transactions, and (for payment-processor-based integrations) to automatically refund or cancel payments associated with alerts. ### Enrolment An enrolment with a dispute prevention service (Ethoca or Verifi RDR). * Creating an enrolment in the ChargebackStop platform starts the process of enrolling the merchant account with the selected service. * Enrolment can span across multiple merchant accounts, e.g. when a single descriptor enrolled with Ethoca is used across multiple accounts. ### Alert An individual pre-dispute alert. * An alert is always tied to an enrolment, as it’s the enrolment that’s the source of the alert. ### Representment A dispute case ingested via your payment processor. * Only available if you choose to work with ChargebackStop for representment. ## API The ChargebackStop platform has an API that supports creating and managing all of the entities above. You can read more about how to consume the API and onboard customers in our [API integration guide](/developer/partner-integration-guide/api-integration-guide.md) page. ## Webhooks The ChargebackStop platform supports webhooks for the following events: * `alert.created` * `alert.updated` * `enrolment.created` * `enrolment.updated` * `representment.created` * `representment.updated` * `scheme_notice.created` * `scheme_notice.updated` Full webhook documentation is available here: [Webhooks](/developer/partner-integration-guide/webhooks.md) Webhooks can be tested using our Postman collection: . You can read more on the page linked above. --- # 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://docs.chargebackstop.com/developer/partner-integration-guide/integrating-with-chargebackstop.md?ask=&goal= ``` `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.