# Chargeblast
- [Welcome to Chargeblast](https://docs.chargeblast.com/reference/welcome-to-chargeblast.md): You're on your way to eliminating chargebacks!
- [Implementation Overview](https://docs.chargeblast.com/guides/implementation-overview.md): Understand the three Chargeblast services and two integration paths to choose the right implementation for your business.
- [Alerts Implementation](https://docs.chargeblast.com/guides/alerts-implementation.md): Learn how to implement CDRN (Visa) and Ethoca (Mastercard) alerts to intercept disputes before they become chargebacks.
- [Digital Receipts & Deflections](https://docs.chargeblast.com/guides/deflections-implementation.md): Learn how to implement Digital Receipts, Compelling Evidence 3.0 (CE3.0), and First Party Trust (FPT) to prevent chargebacks before they happen.
- [Authorization](https://docs.chargeblast.com/api-reference/introduction/authorization.md)
- [Webhooks](https://docs.chargeblast.com/api-reference/webhooks/setup.md): This page will help you get started with our webhooks.
- [Fetch Alerts](https://docs.chargeblast.com/api-reference/alerts/fetch-alerts.md): Get all the alerts from your Chargeblast account.
- [Fetch an Alert](https://docs.chargeblast.com/api-reference/alerts/fetch-an-alert.md): Get a specific alert.
- [Update Alert](https://docs.chargeblast.com/api-reference/alerts/update-alert.md): Update the status of an alert to inform the issuing bank whether a refund will be issued. If an alert is left unactioned for 48 hours, it will be automatically declined. For the best outcome, mark alerts as resolved within 24 hours of receiving them (some smaller banks will escalate quarantined tran…
- [Alert Types](https://docs.chargeblast.com/reference/alert-types.md): A guide to all alert networks and data sources (subproviders) in Chargeblast.
- [Reason Codes](https://docs.chargeblast.com/reference/reason-codes.md): A guide to all reason codes used when actioning CDRN/Ethoca alerts via the update alerts endpoint.
- [Create Credit Request](https://docs.chargeblast.com/api-reference/credit-requests/create.md): Creates a credit request for a rejected alert. Will fail if requesting credit from resolved alert or alert with an existing credit request, otherwise will simply return 200 response code.
- [Fetch Disputes](https://docs.chargeblast.com/api-reference/disputes/fetch-disputes.md): Get all the chargeback disputes from your Chargeblast account.
- [Upload Orders](https://docs.chargeblast.com/api-reference/sync-data/upload-orders.md): Upload orders to the chargeblast system. This will allow you to match disputes and chargebacks to the orders you have uploaded. Amount should be in cents, e.g. $19.99 => amount = 1999. This endpoint is rate limited to 100 requests every 10 seconds.
- [Upload Disputes](https://docs.chargeblast.com/api-reference/sync-data/upload-disputes.md): Upload disputes with per-dispute validation. Each dispute must reference an existing order via chargeId or include an order object to create it, so every dispute is linked to a charge. Valid disputes are saved even when others in the batch fail. Returns succeeded and failed dispute ids with reasons.…
- [Fetch Orders](https://docs.chargeblast.com/api-reference/sync-data/get-orders.md): Get all the orders from your chargeblast account. Receipt info is omitted from this endpoint.
- [Fetch Order](https://docs.chargeblast.com/api-reference/sync-data/get-order.md): Get a specific the order from your chargeblast account. Receipt info is included with this endpoint.
- [Upload IP Data](https://docs.chargeblast.com/api-reference/sync-data/track.md): This is used to upload IP data. Not needed if you are implementing /orders/upload (instead pass IP data there) - only used if you are on a supported integration and want to board with compelling evidence.
- [Fetch Deflection Logs](https://docs.chargeblast.com/api-reference/deflections/logs.md): Get a list of all look up requests.
- [RDR Action Endpoint](https://docs.chargeblast.com/api-reference/getting-started/rdr-endpoint.md)
- [Enrollment Lifecycle](https://docs.chargeblast.com/api-reference/enrollment/enrollment-lifecycle.md): How enrollment works across programs: enrolling files a request, records start Pending, and they become Enrolled once the provider confirms.
- [Fetch Merchants](https://docs.chargeblast.com/api-reference/enrollment/fetch-merchants.md): Get all the merchants from your chargeblast account. Response is paginated. The `name` field is set during onboarding of the merchant and corresponds to the individual name of the merchant for multi-merchant accounts (usually associated with the DBA or billing descriptor).
- [Fetch Descriptors](https://docs.chargeblast.com/api-reference/enrollment/fetch-descriptors.md): List the descriptors on your account as a flat, filterable, paginated record set.
- [Enrollment Status](https://docs.chargeblast.com/api-reference/enrollment/enrollment-status.md): Report your merchant's enrollment status for every program (Ethoca, CDRN, RDR, Amex, Discover). Each entry is `none`, `pending`, or `enrolled`. Enrollment via the API files a request, so a program stays `pending` until the provider-side enrollment confirms (which flips it to `enrolled`). The contrib…
- [Fetch Merchant](https://docs.chargeblast.com/api-reference/enrollment/fetch-merchant.md): Get an individual merchant from your chargeblast account.
- [Enroll Merchant](https://docs.chargeblast.com/api-reference/enrollment/enroll-merchant.md): Enroll a merchant in an alert or refund program. Send a `program` discriminator with that program's fields. `ethoca` and `cdrn` require `descriptors`. `rdr` requires `arns` and/or equal-length paired `bins`/`caids` (its `bins`/`caids` are persisted as queryable RDR descriptors). `amex` and `discover…
- [Unenroll Merchant](https://docs.chargeblast.com/api-reference/enrollment/unenroll-merchant.md): Unenroll one or more descriptors. Pass `descriptor_ids` (obtain ids from `GET /api/v2/descriptors`); a single legacy `descriptor_id` is also accepted. Descriptors that were still `Pending` (never live with the provider) are removed immediately and returned under `removed`. Descriptors that were live…
## OpenAPI Specs
- [openapi](/openapi.json)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.
Measured from the saved file
Linked document
UTF-8 text size
6.2 KB6376 bytes
Token count
1439o200k_base encoding
Markdown links
2929 distinct URLs
Fenced code blocks
036 lines in the file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
Project H1
Chargeblast
Context architecture
How the content is divided
1 H2 sections organize 29 parsed Markdown links. 27 links point to .md or .markdown paths; 1 link occurrences use another hostname. Linked destinations have not been recursively validated.
H2 section
Links
UTF-8 bytes
Tokens
OpenAPI SpecsLine 31
2
141
33
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Code, installation and API examples
Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
1 links have authentication-related labels
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
The Optional section
No H2 section named “Optional” was detected in this file.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP references and configuration text
No MCP or Model Context Protocol term was detected in the captured file. 0 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
These are text and link observations. No MCP server connection, authentication or tool call was tested.
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
What can be said about freshness
This capture establishes a baseline. Update frequency cannot be determined from one observation.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.