# Page Not Found

The URL `payment-gateways/setting-up-afterpay-as-a-payment-processor` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Setting up Afterpay as a payment processor](https://help.booksession.co/product-docs/integrations/payment-gateways/setting-up-afterpay-as-a-payment-processor.md)
- [Setting up Stripe as a payment processor](https://help.booksession.co/product-docs/integrations/payment-gateways/setting-up-stripe-as-a-payment-processor.md)
- [Setting up PayPal as a payment processor](https://help.booksession.co/product-docs/integrations/payment-gateways/setting-up-paypal-as-a-payment-processor.md)
- [Setup Surcharge per Payment Processor](https://help.booksession.co/product-docs/integrations/payment-gateways/setup-surcharge-per-payment-processor.md)
- [Elevating Your Experience: Latest Platform Updates and Fixes](https://help.booksession.co/product-docs/updates-and-new-features/elevating-your-experience-latest-platform-updates-and-fixes.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://help.booksession.co/product-docs/integrations/payment-gateways/setting-up-afterpay-as-a-payment-processor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://help.booksession.co/product-docs/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://help.booksession.co/product-docs/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/product-docs/integrations/payment-gateways/setting-up-afterpay-as-a-payment-processor.md`).

You may also use `Accept: text/markdown` header for content negotiation.