> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/payment-methods/card-processors/global-payments.md).

# Global Payments

Global Payments processes card, ACH, Apple Pay and Google Pay payments for SensePass locations in the USA.

**Card processor - USA - Card, ACH, Apple Pay, Google Pay**

#### What SensePass does with Global Payments

* Shows Card, ACH, Apple Pay, Google Pay on the SensePass payment page: payment requests, the Digital Terminal and Pay by Link.
* Supports payments, authorizations (capture later), saved payment methods (tokens), charge and save in one step, full refunds, partial refunds.

#### Capabilities

| Country | Method     | Payment | Authorize | Tokenize | Tokenize + Capture | Full refund | Partial refund | Credit | 3DS | Split payment | L2/L3 data |
| ------- | ---------- | ------- | --------- | -------- | ------------------ | ----------- | -------------- | ------ | --- | ------------- | ---------- |
| USA     | Card       | Yes     | Yes       | Yes      | Yes                | Yes         | Yes            | -      | -   | -             | -          |
| USA     | ACH        | Yes     | No        | Yes      | Yes                | Yes         | No             | -      | -   | -             | -          |
| USA     | Apple Pay  | Yes     | Yes       | -        | -                  | -           | No             | -      | -   | -             | -          |
| USA     | Google Pay | Yes     | Yes       | Yes      | Yes                | -           | Yes            | -      | -   | -             | -          |

Yes = supported. No = not supported. - = not available or not confirmed yet - contact SensePass to check. Notes such as "terminals only" are shown under the table.

#### Set it up

Payment methods are set per location. Contact your SensePass account manager or <support@sensepass.com> to add Global Payments to your location. They tell you which details from your Global Payments account SensePass needs and where to enter them.

{% hint style="danger" %}
**Important:** Keep your credentials confidential. Do not send them by email or chat. Enter them only in the dashboard.
{% endhint %}

#### Who to contact

| For                                                                      | Contact                                                   |
| ------------------------------------------------------------------------ | --------------------------------------------------------- |
| Your Global Payments account, settlement and fees                        | Global Payments support                                   |
| Setting up Global Payments in SensePass, payments that fail in SensePass | <support@sensepass.com> or your SensePass account manager |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sensepass.com/sensepay/payment-methods/card-processors/global-payments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
