> 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/wallets-and-pay-later/bit.md).

# Bit

Customers in Israel pay with Bit on the SensePass payment page.

Bit is available through Cardcom or PayMe.

**Wallet - Israel - Bit**

### What SensePass does with Bit

* Shows Bit on the SensePass payment page: payment requests, the Digital Terminal and Pay by Link.
* Supports payments, full refunds.
* Works in the JavaScript UI SDK for web checkout (see the SDK table).

### Capabilities

#### Payment page

| Country | Provider | Method | Payment | Authorize | Tokenize | Tokenize + Capture | Full refund | Partial refund | Credit | 3DS | Split payment | L2/L3 data |
| ------- | -------- | ------ | ------- | --------- | -------- | ------------------ | ----------- | -------------- | ------ | --- | ------------- | ---------- |
| Israel  | Cardcom  | Bit    | Yes     | No        | No       | -                  | Yes         | No             | -      | -   | -             | -          |
| Israel  | PayMe    | Bit    | Yes     | 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 |
| ------------- | -------------- | --------- | -------- | -------------- | ---------- |
| Bit (Cardcom) | Yes            | No        | No       | Yes            | -          |

### Set it up

Bit is set up through Cardcom or PayMe. Follow the credentials steps on that provider's page, then add Bit to the location in **SensePass Partners** > location > **Payment Methods**.

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

#### Currency and amounts

| Country | Currency | Minimum amount | Decimal amounts | Payment page language |
| ------- | -------- | -------------- | --------------- | --------------------- |
| Israel  | ILS      | 5              | Yes             | Hebrew                |

### Who to contact

| For                                                          | Contact                                                   |
| ------------------------------------------------------------ | --------------------------------------------------------- |
| Your Bit account, credentials, settlement and fees           | Bit support                                               |
| Setting up Bit 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/wallets-and-pay-later/bit.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.
