> 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/versapay.md).

# VersaPay

VersaPay processes card payments for SensePass locations in the USA.

**Card processor - USA - Card**

### What SensePass does with VersaPay

* Shows Card on the SensePass payment page: payment requests, the Digital Terminal and Pay by Link.
* Supports payments, authorizations (capture later), saved payment methods (tokens), full refunds, partial refunds.
* Works in the JavaScript UI SDK for web checkout (see the SDK table).

### Capabilities

#### Payment page

| 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            | -      | No  | -             | -          |
| USA     | Apple Pay  | No      | No        | No       | -                  | -           | No             | -      | -   | -             | -          |
| USA     | Google Pay | No      | No        | No       | -                  | -           | No             | -      | -   | -             | -          |

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.

#### JavaScript UI SDK

| Method     | Manual capture | Authorize | Tokenize | Partial refund | L2/L3 data |
| ---------- | -------------- | --------- | -------- | -------------- | ---------- |
| Card       | Yes            | Yes       | Yes      | -              | -          |
| Apple Pay  | No             | No        | No       | -              | -          |
| Google Pay | No             | No        | No       | -              | -          |

### Get the credentials from VersaPay

SensePass needs the API credentials from your VersaPay account. The **Add Payment Details** window for VersaPay in SensePass Partners lists each field, and required fields are marked with \*.

Sign in to your VersaPay account to create or copy these credentials. If you cannot find them, contact VersaPay support.

### Enter the credentials in SensePass Partners

Payment methods are set per location.

1. In SensePass Partners, open the location's three-dot menu and select **Payment Methods**.
2. Click **+** at the end of the **VersaPay** row. The **Add Payment Details** window opens.
3. Paste the credentials into the matching fields. Required fields are marked with \*.
4. Click **Save**.

{% hint style="info" %}
**No access to SensePass Partners?** Your SensePass partner sets up payment methods for you. Ask them to add VersaPay to your location.
{% endhint %}

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

### Good to know

* Test in Sandbox with the official test cards - see [Testing](https://docs.sensepass.com/sensepay/developers/transaction-api/testing) in the Developers section.

### Who to contact

| For                                                               | Contact                                                   |
| ----------------------------------------------------------------- | --------------------------------------------------------- |
| Your VersaPay account, credentials, settlement and fees           | VersaPay support                                          |
| Setting up VersaPay 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/versapay.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.
