Connect bit ביט accounts, P2P payments, and merchant flows to your stack—safely
bit is the largest peer-to-peer payment app in Israel, operated by Bank Hapoalim, with more than two million users and an estimated 80% share of P2P transfers between consumers. We deliver bit ביט protocol analysis, account login flows, payment-request endpoints, balance and statement exports, group-collection inspection, and merchant Bit-button integrations. Every integration follows the Bank of Israel PSD2 standard that has been live since April 2021 and the wider OpenBanking pattern.
What we deliver
Every bit ביט engagement ends with a signed-off, runnable package. You receive an OpenAPI 3.1 specification, a written protocol report covering the login chain and token refresh, runnable reference implementations in Python and Node.js, a test plan with replayable fixtures, and compliance notes mapped to Israeli regulation. The exact mix is scoped during kick-off so that small studios pay only for the surface they need, while enterprise customers can extend to bulk-account orchestration and SIEM-ready logging.
Deliverables checklist
- OpenAPI 3.1 specification for every endpoint
- Protocol & auth report (OAuth, device binding, refresh chain)
- Runnable Python & Node.js reference for login, balance, statement
- Automated pytest / Jest suites with replay fixtures
- Compliance brief: Bank of Israel PSD2, GDPR/Privacy Law 5781-1981
- Optional hosted endpoints with HMAC-signed webhooks
Engagement models
- Source code delivery from $300 — runnable source plus docs; pay on satisfaction
- Pay-per-call hosted API — usage-based pricing, no upfront cost
- Bug-fix & refresh subscription for endpoint drift (quarterly)
- White-label SDK packaging for resellers
Data available for integration
The table below maps bit ביט’s in-app surfaces to the structured data points an OpenBanking-style integration can expose. Granularities are written against the published transaction caps — up to 5,000 ILS per transfer and 20,000 ILS per month for retail users, with higher merchant ceilings on authorised accounts.
| Data type | Source surface | Granularity | Typical use |
|---|---|---|---|
| P2P transfers | “Home” & activity feed | Per transfer, ILS, ISO-8601 timestamp | Reconciliation, AML monitoring |
| Wallet balance | Balance card | Snapshot + balance-change events | Cash-flow dashboards, treasury |
| Payment requests | Requests inbox | Per request: payer, amount, status | Receivables, dunning workflows |
| Group collections | “Groups” module | Group, participants, share, reminders | Event HR, club & team finance |
| Merchant Bit-button | Allpay / PayMe checkout | Per order: order_id, amount, refund_id | E-commerce reconciliation |
| Foreign-currency orders | FX pre-order screen | Currency, amount, airport branch | Travel-tech integrations |
| Refund inflows | Insurance & pension refunds | Source, amount, reason code | Personal finance, audit |
| Arnona payments | Municipal-tax tile | Municipality, billing period, amount | Citizen-services portals |
Typical integration scenarios
1. Small-business reconciliation for Israeli e-commerce
A Shopify-style merchant in Tel Aviv exposes the Bit button at checkout via the Allpay or PayMe gateway. Our integration consumes the merchant Bit-button webhook stream and reconciles each order_id against the Bit transfer leg and the bank settlement leg pulled from Bank Hapoalim’s PSD2 AISP feed. This collapses what is currently a three-screen workflow into one event, mapping to the OpenFinance “payment-account-information” primitive.
2. Group treasurer dashboard
Sports clubs, parents’ committees, and small offices in Israel rely on bit’s group collection. We expose the group state — participants, due amounts, reminder cadence — through a read-only endpoint a treasurer dashboard can poll. The flow uses OAuth-style consent and maps cleanly to the PSD2 “account information” pattern: read access only, refreshed every 90 days under the consumer’s active consent.
3. Personal-finance aggregator (PFM)
A PFM app wants a single “Israel pocket” that combines a user’s bit wallet balance, Hapoalim current account, and any Cal or Max credit lines. Our adapter normalises bit’s ILS-only balance and transaction list into the open-banking account and transaction schemas, so the PFM’s existing categoriser can ingest bit data without bespoke schema work.
4. KYC & AML screening for merchant onboarding
An onboarding platform must verify that a vendor’s receiving leg is a real Israeli bit account before unlocking payouts. The integration runs a small Bit-button proof-of-life transfer, then matches the resulting recipient_hash back to the vendor record — a pattern aligned with the Bank of Israel’s i-AML guidance for digital wallets.
5. Travel-tech foreign currency orchestration
A travel agency reads each customer’s bit foreign-currency pre-order — currency, amount, pickup branch at Ben Gurion airport — and feeds it into a trip itinerary, so the user sees their cash pickup alongside flights and hotels. The endpoint exposes order status webhooks so the agency can prompt the user when the currency is ready.
Technical implementation
Each engagement begins by mapping the public Allpay and PayMe Bit-button surface, the Poalim developer-portal PSD2 endpoints, and any documented bit developer-portal sandboxes (developer.bitpay.co.il) into a single OpenAPI 3.1 contract. The following snippets are illustrative shapes; the actual fields and signing headers are confirmed against current sandbox responses before delivery.
1. Authorize a user (OAuth-style consent)
POST /api/v1/bit/auth/token
Content-Type: application/json
X-Client-Id: ofl_studio_demo
{
"grant_type": "authorization_code",
"code": "<PSD2_CONSENT_CODE>",
"redirect_uri": "https://merchant.example/cb",
"device_binding": {
"platform": "android",
"fingerprint": "sha256:..."
}
}
200 OK
{
"access_token": "eyJhbGciOi...",
"refresh_token": "rft_...",
"expires_in": 1800,
"scope": "balance:read transactions:read"
}
2. Fetch a transaction statement
POST /api/v1/bit/statement
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json
{
"account_id": "il-bit-9f3c",
"from_date": "2026-04-01",
"to_date": "2026-04-30",
"types": ["p2p", "request", "merchant"]
}
200 OK
{
"currency": "ILS",
"count": 42,
"items": [
{
"id": "tx_01HXYZ...",
"direction": "out",
"amount": 120.00,
"counterparty_hash": "ph_4a1b",
"memo": "BBQ split",
"ts": "2026-04-14T19:02:11+03:00",
"status": "settled"
}
],
"next_cursor": "cur_eyJv..."
}
3. Merchant Bit-button webhook
POST https://merchant.example/webhooks/bit
X-Signature: t=1715300000,v1=hmac-sha256:...
Content-Type: application/json
{
"event": "bit.payment.settled",
"order_id": "ord_8821",
"bit_tx_id": "tx_01HY7K...",
"amount": 249.90,
"currency": "ILS",
"merchant_id": "mer_allpay_77",
"occurred_at": "2026-05-09T12:41:08+03:00"
}
// On error: respond 5xx; the platform retries
// with exponential backoff for up to 24 hours.
Compliance & privacy
bit operates inside one of the most explicit fintech rule sets in the region. Bank Hapoalim adopted the Bank of Israel PSD2 standard from April 2021, and in 2024 the Bank of Israel approved bit to operate as a full digital wallet beyond its original P2P scope. Every endpoint we deliver respects three layers: (1) explicit, time-bound consumer consent recorded with timestamp and scope; (2) data minimisation in line with Israel’s Privacy Protection Law 5781-1981 and GDPR for any EU-resident user; (3) audit logging of every API call with non-reversible hashes for counterparties so downstream systems do not store raw phone numbers.
We do not bypass authentication, reverse engineer protected client code, or use unauthorised credentials. Integrations rely on documented Poalim dev portal flows, the bit developer portal sandbox, and merchant SDKs from Allpay, PayMe, and similar PSPs. The 1% annual fee on inflows above 25,000 ILS that took effect in January 2025 is surfaced as a discrete field in the statement response so downstream accounting can reconcile it cleanly.
Data flow & architecture
A typical bit ביט integration uses a short, auditable pipeline:
- Client app or merchant checkout — user grants PSD2-style consent or completes a Bit-button payment.
- OpenFinance Lab ingestion layer — normalises Poalim PSD2 responses, bit developer-portal events, and PSP webhooks into a single schema.
- Storage & retention — encrypted at rest, separated by tenant, with per-record consent expiry (default 90 days, configurable).
- API output / analytics — REST endpoints, signed webhooks, and optional BigQuery / Snowflake exports for analytics teams.
Market positioning & user profile
bit is the dominant Israeli P2P wallet, with over two million users and an estimated 80% share of person-to-person digital transfers, according to Globes reporting around the January 2025 fee rollout. Its core user is the Israeli consumer aged 18–55 on Android or iOS, paying for group activities, splitting restaurant bills, and increasingly using the app as a digital wallet for online checkout and municipal payments. On the merchant side, small businesses and direct-to-consumer brands accept bit through Allpay and PayMe gateways, while large retailers integrate it alongside Apple Pay and Google Pay. Geographically the app is concentrated in Israel and serves Israeli passport-holders abroad through its foreign-currency pre-order feature, making it a natural integration point for travel-tech, e-commerce, and any cross-border product targeting the Israeli market.
Screenshots
Tap any thumbnail to view the full screen. These are the in-store screenshots used to scope the user surfaces above — balance, P2P transfer, groups, and merchant Bit-button.
Similar apps & integration landscape
Teams integrating bit ביט typically also touch the wider Israeli digital-payment ecosystem. The apps below are part of that landscape and often appear in the same wallet, treasury, or PFM unification project. Coverage here is purely descriptive — the goal is to make the integration map explicit for product teams scoping cross-app data flows.
PayBox (Israel Discount Bank)
Social payment app focused on group collections and P2P transfers. Holds group membership graphs, payment-request inboxes, and merchant payment events — users with both bit and PayBox histories often need a unified transaction export.
Pepper Pay (Bank Leumi)
Pepper’s payment surface powered by Bank Leumi. Provides P2P transfers and a digital wallet linked to Leumi current accounts, with a separate PSD2 dev portal at Leumi for AISP access.
Max
Israeli credit-card and payment app owned by Warburg Pincus. Holds card transaction history and BNPL plans — an obvious sibling source when normalising consumer spend alongside bit wallet activity.
Anypay (Isracard)
Isracard’s contactless and online payment app. Holds card-on-file events and Isracard loyalty data, often paired with bit in unified Israeli wallet stacks.
Cal Pay (Cal-Online)
Cal’s consumer payment surface with credit and instalment plans. Useful pairing for treasurers reconciling Cal-issued card transactions against bit P2P inflows.
Leumi App
Bank Leumi’s primary mobile banking app, exposing current-account balances and transfers under Israel’s PSD2 standard — the natural counterpart for a bit wallet linked to a Leumi top-up source.
Bank Hapoalim App
The flagship Hapoalim banking app and source of truth for a bit wallet’s funding source. Reads current-account postings against bit transfers for end-to-end auditing.
Apple Pay (Israel)
Apple’s contactless wallet, now the largest digital wallet by user count in Israel. Bit and Apple Pay frequently co-exist on the same device; integration projects need to attribute revenue between the two rails.
Google Pay (Israel)
Google Wallet’s Israeli deployment, launched in partnership with Bank Leumi and others. Holds tokenised card events that complement bit’s account-based P2P data.
BitPay Israel (merchant)
Merchant-side Bit-button infrastructure run via the bit developer portal. Provides checkout-level webhooks and refund APIs that pair with the consumer-side wallet integration described above.
About us
OpenFinance Lab is an independent technical studio focused on mobile-app protocol analysis and OpenData / OpenFinance API integration. Our engineers come from Israeli and international banks, payment service providers, and security teams. We have shipped production endpoints for Israeli P2P wallets, EU PSD2 AISP/PISP flows, and merchant-side reconciliation tooling, and we operate exclusively under customer authorisation or documented public APIs.
- Payments, digital banking, insurtech, and travel-tech
- OpenAPI 3.1, Python & Node.js, Go & Rust on request
- Security reviews and CI test harnesses included by default
- Bank of Israel PSD2, GDPR, and Privacy Law 5781-1981 aligned
Contact
Send the target app, the surfaces you want exposed, and any sandbox credentials you already hold — we will reply with a scope and quote within one business day.
Engagement workflow
- Scope confirmation: which bit surfaces (P2P, groups, merchant button) and which data points.
- Protocol analysis & API design (2–5 business days).
- Build & internal validation against sandbox or live consent (3–8 business days).
- Docs, samples, automated test suite (1–2 business days).
- First delivery typically 5–15 business days end-to-end.
FAQ
What do you need from me to start a bit ביט integration?
How long does delivery take for a bit ביט API drop?
How do you handle compliance with Bank of Israel and PSD2 rules?
📱 Original app overview (appendix)
bit — Israel’s leading payment app, making it easy and secure to send and receive money. The app is operated by Bank Hapoalim and used by over two million people in Israel, with an estimated 80% share of P2P transfers between consumers. Daily caps are 5,000 ILS per transfer and 20,000 ILS per month for retail users; only Israeli Shekels are supported. In January 2025, bit rolled out dark-mode display and introduced a 1% fee on annual inflows above 25,000 ILS. In 2024 the Bank of Israel approved bit to act as a full digital wallet for all Bank Hapoalim customers.
- Manage your balance — money received stays in the app; keep it or transfer onward.
- Shop online with ease — pay on websites and apps with bit; no need to enter credit-card details.
- Order foreign currency in advance — pre-order currency and pick it up at Ben Gurion airport.
- Group collections made simple — create a group for a BBQ or gift, invite friends, send reminders.
- Send payment requests — someone forgot to pay you? Send them a request through the app.
- Receive insurance and pension refunds — refunds arrive straight to your bit account.
- Pay Arnona (municipal taxes) — get notified and pay directly in the app.
- Carrefour Club credit card — apply for the card, earn +Carrefour coins, redeem in stores.