# API Documentation
## Docs
- [Introduction](https://docs.fractalpay.com/introduction.md): Welcome to the Fractal documentation
- [Implementation Guide](https://docs.fractalpay.com/implementationguide.md): Integrations simplified
- [Webhooks](https://docs.fractalpay.com/Webhooks.md)
- [Low Code JS](https://docs.fractalpay.com/EmbeddedPayments.md): Fractal JS in depth
- [GooglePay™ Web Integration](https://docs.fractalpay.com/googlepay.md)
- [Full Merchant Submit](https://docs.fractalpay.com/api-reference/merchant-onboarding/full-merchant-submit.md): Full Merchant Submit
- [Get Merchants by Client](https://docs.fractalpay.com/api-reference/merchant-onboarding/get-merchants-by-client.md): Get Merchants by Client
- [Hosted Onboarding](https://docs.fractalpay.com/api-reference/merchant-onboarding/hosted-onboarding.md): SAML authentication and hosted merchant onboarding flow
- [Payment Request](https://docs.fractalpay.com/api-reference/payment-collection-methods/payment-request.md): Payment Request
- [Payment Request Customer](https://docs.fractalpay.com/api-reference/payment-collection-methods/payment-request-customer.md): Payment Request Customer
- [Create Link](https://docs.fractalpay.com/api-reference/payment-collection-methods/create-payment-link.md): Create Link
- [Payment Link](https://docs.fractalpay.com/api-reference/payment-collection-methods/qr-payment-link.md): Payment Link
- [Delete Pay Link](https://docs.fractalpay.com/api-reference/payment-collection-methods/delete-pay-link.md): Delete Pay Link
- [Remote Deposit Capture](https://docs.fractalpay.com/api-reference/payment-collection-methods/remote-deposit-capture.md): Submit a check image for remote deposit capture. Sends the front and back images of a check as a multipart/form-data upload.
- [Update Pre-Authorization](https://docs.fractalpay.com/api-reference/preauthorizations/increment-pre-authorization.md): Increases or decreases the authorized amount on an existing preauthorization. If new_authorized_amount is greater than last_authorized_amount, an incremental authorization is issued and a preauth.increment webhook fires. If new_authorized_amount is less, a partial reversal is issued and a preauth.de…
- [Capture Pre-Authorization](https://docs.fractalpay.com/api-reference/preauthorizations/capture-pre-authorization.md): Charges the customer for the currently authorized amount on an existing preauthorization. Converts the preauth into a completed transaction. Fires a preauth.charge webhook on success.
- [Charge Customer](https://docs.fractalpay.com/api-reference/customers/charge-customer.md): Charge Customer
- [Create Customer](https://docs.fractalpay.com/api-reference/customers/create-customer.md): Create Customer
- [Get Customer](https://docs.fractalpay.com/api-reference/customers/get-customer.md): Get Customer
- [Get Customers](https://docs.fractalpay.com/api-reference/customers/get-customers.md): Get Customers
- [Request Card](https://docs.fractalpay.com/api-reference/customers/request-card.md): Request Card
- [Get Transactions](https://docs.fractalpay.com/api-reference/transactions/get-transactions.md): Get Transactions
- [Get Transaction](https://docs.fractalpay.com/api-reference/transactions/get-transaction.md): Get Transaction
- [Return Sale](https://docs.fractalpay.com/api-reference/transactions/return-sale.md): Return Sale
- [Void Sale](https://docs.fractalpay.com/api-reference/transactions/void-sale.md): Void Sale
## OpenAPI Specs
- [openapi](https://docs.fractalpay.com/api-reference/openapi.json)
- [openapiOLD](https://docs.fractalpay.com/api-reference/openapiOLD.json)
- [openapiTEST](https://docs.fractalpay.com/api-reference/openapiTEST.json)
## Optional
- [Embedded Payments](https://fractalpay.com/)
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
3.8 KB3867 bytes
Token count
860o200k_base encoding
Markdown links
3030 distinct URLs
Fenced code blocks
042 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
API Documentation
Context architecture
How the content is divided
3 H2 sections organize 30 parsed Markdown links. 25 links point to .md or .markdown paths; 2 link occurrences use another hostname. Linked destinations have not been recursively validated.
H2 section
Links
UTF-8 bytes
Tokens
DocsLine 3
25
3428
753
OpenAPI SpecsLine 31
3
220
59
OptionalLine 37 · Optional
2
161
36
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
2 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
1 H2 section named “Optional” contain 2 parsed links. 28 links sit outside those sections. That puts 6.7% of the file’s parsed links under Optional.
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.