> For the complete documentation index, see [llms.txt](https://help.horsespot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.horsespot.com/product-docs/show-day-tools/payments/alternate-processing-options.md).

# Alternate Processing Options

{% embed url="<https://www.loom.com/share/b05b64643b9f4094b3886a93c20d7801>" %}

## Payment Gateways Beyond Stripe

For many show organizers, Stripe integrated with Horse Spot is a great option for credit card processing and digital transactions. That said, Horse Spot also connects with a number of other gateways and payment processors, such as NMI.

### Why You Might Use a Different Gateway

Horse Spot allows you to move between multiple gateways if you'd prefer to use one other than Stripe, or if you'd simply like a redundancy plan in place. Having more than one gateway option set up means processing never becomes an issue, and you're never left temporarily unable to process payments.

### Setting Up an Alternate Gateway

If you're interested in using a gateway other than Stripe, reach out to the Horse Spot team. We can walk through the specific options that make the most sense for your competitions.


---

# 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://help.horsespot.com/product-docs/show-day-tools/payments/alternate-processing-options.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.
