# Page Not Found

The URL `payment-integrations-1/digitalriver.js/reference/error-types-codes-and-objects` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Error types, codes, and objects](https://docs.digitalriver.com/digital-river-api/developer-resources/reference/error-types-codes-and-objects.md)
- [Common payment objects](https://docs.digitalriver.com/digital-river-api/payments/payment-integrations-1/digitalriver.js/payment-methods/common-payment-objects.md)
- [Common payment sources](https://docs.digitalriver.com/digital-river-api/payments/payment-integrations-1/digitalriver.js/payment-methods/common-payment-sources.md)
- [Configuring Online Banking (Korea Bank Transfer)](https://docs.digitalriver.com/digital-river-api/payments/payment-integrations-1/digitalriver.js/payment-methods/korea-bank-transfer.md)
- [Configuring Credit Cards](https://docs.digitalriver.com/digital-river-api/payments/payment-integrations-1/digitalriver.js/payment-methods/credit-cards.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://docs.digitalriver.com/digital-river-api/developer-resources/reference/error-types-codes-and-objects.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://docs.digitalriver.com/digital-river-api/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.digitalriver.com/digital-river-api/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., `/digital-river-api/developer-resources/reference/error-types-codes-and-objects.md`).

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