> For the complete documentation index, see [llms.txt](https://docs.syfu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.syfu.io/payment-data/bind-rules.md).

# 3.4 BIND Rules

> **Note (Manual Import):** For photo-uploaded statements, additional constraints apply\
> (photo timestamp after check-in, within 300 m, ≤ 4-hour gap).\
> See [**3.2 Manual Import** ](/payment-data/manual-import.md)**→ “Manual Import BIND Conditions (ver.0.3.5+)”**.

**Core Principles**

1. **Sequence required**: Check-in → Payment → Data Import → BIND
2. Must be an **in-store (physical) payment experience**. Anything else is invalid.
3. Same store: Must wait **at least 4 hours** before re-check-in.
4. Invalid case: Attempting to BIND payments made **before check-in** (exception: same-day transactions with automatic import).

**Not Eligible (NG)**

* Online payments (Amazon, Uber Eats, etc.)
* Mobile orders with in-app payment (e.g., Starbucks app, McDonald’s app)

**Eligible (OK)**

* In-store face-to-face card payments (physical card, contactless, iD, QUICPay, etc.)
* App orders where payment is completed at the **cashier, kiosk, or POS terminal**

**Mobile Order & Takeout Rules** \
The **only valid criterion** is:\
\&#xNAN;**“Was the payment processed at the store POS (face-to-face)?”**

✅ Eligible (BIND allowed):

* Order via app → pay at store cashier upon pickup
* Self-kiosk or handheld POS payment in-store

❌ Not Eligible (BIND not allowed):

* Full in-app payments (pickup only, no cashier step)
* Table QR ordering with app-only settlement
* Delivery/aggregator platforms (Uber Eats, DoorDash, etc.)
* Balance recharge (Pay apps, transit IC, gift cards)

👉 While there may be potential to expand support for online payments and aggregators in the future, the above rules are strictly enforced under the current system.


---

# 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://docs.syfu.io/payment-data/bind-rules.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.