> For the complete documentation index, see [llms.txt](https://docs.oisy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oisy.com/using-oisy-wallet/oisy-pay.md).

# OISY Pay

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FIroYca31skkSmxosUWMK%2FOISY-pay-url-select.jpg?alt=media&amp;token=9450a830-b15c-4e91-8fda-a2644bf37464" alt=""><figcaption></figcaption></figure>

**OISY Pay** lets you complete real-world and online payments using Open CryptoPay. It’s designed for simple checkout flows where you either scan a QR code or paste a payment link, then send the exact amount from the asset and network you choose.

#### Where you can use it

OISY Pay works with all Open CryptoPay-enabled merchants, including:

* SPAR Switzerland
* Shopware stores
* WooCommerce stores

For more details see here: <https://opencryptopay.io/ecosystem.html>

#### How it works

Merchants generate a payment request (QR code or URL) via Open CryptoPay.

You approve camera access (for QR scans) or paste a link manually, choose what you want to pay with, then confirm the transaction in OISY.

#### Supported assets

When paying, you can select from:

* ICP
* ckBTC
* VCHF
* VEUR
* BTC
* WBTC
* ETH
* USDC
* USDT
* dEURO
* ZCHF (Frankencoin)
* DAI
* BNB
* SOL

#### Pay flow

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FRX9DdGyV4Ox67adFJEht%2Fimage.png?alt=media&amp;token=ffd6f3f0-a1e0-40c7-ba64-cdb730759178" alt=""><figcaption></figcaption></figure>

1. Open OISY
2. Tap the Universal Scanner icon (top-right)
3. Choose how to enter the payment request:
   * Scan QR code (enable camera permission when prompted)
   * Paste URL (manual link input)
4. Select the asset and chain you want to pay with
5. Review recipient details (tap the arrow next to Recipient to expand)
6. Tap Pay
7. After confirmation, you’ll see a Payment Confirmed screen with the merchant name and amount<br>

#### Recipient details you can review

Before you pay, you can expand the recipient section to view:

* Name
* Address
* Country
* Phone number
* Email address
* Website

#### Payment confirmation

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FAfjruFcSd3dgPfDto5rN%2FOISY-pay-done.jpg?alt=media&amp;token=a9ba3f3f-7fb2-46c8-aea7-91cb9855fba2" alt=""><figcaption></figcaption></figure>

Once the transaction is successful, OISY displays a confirmation screen showing:

* The merchant (example: Paid at SPAR)
* The amount paid (example shown in USDC)
* “Powered by Open CryptoPay” branding for clarity on the payment rail

#### Notes

* If scanning is blocked, check your device camera permissions for OISY.
* If you received a link instead of a QR code, you can paste the URL directly to start the same flow.


---

# 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.oisy.com/using-oisy-wallet/oisy-pay.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.
