> For the complete documentation index, see [llms.txt](https://developers.usetoggle.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.usetoggle.com/partner-guides/guest-gratuity/accreditation.md).

# Accreditation

For approved partner integrations, you will need to complete our accreditation process.

### Accreditation test cases

You will be asked to complete a series of test cases to ensure all use-cases have been met.

Here is a sample list of test cases:

1. To test successful API authorisation
2. To test failed API authorisation with incorrect username/password
3. To test failed API request due to invalid or expired token
4. To test a successful creation of a new card
5. To test a failed order creation, with an invalid merchant\_id
6. To test a failed order creation, with invalid or missing product\_id
7. To test a failed order creation, with invalid or missing currency
8. To test a failed order creation, with invalid or missing sales\_channel\_id
9. To test a failed order creation, with invalid or missing fulfilment\_method\_id
10. To test a successful reversal of a card creation
11. To test a failed reversal due to missing or invalid line\_item\_id


---

# 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://developers.usetoggle.com/partner-guides/guest-gratuity/accreditation.md?ask=<question>&goal=<endgoal>
```

`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.