Entity resolved
SafeCash Applications Ltd., company 516016045, operates KashCash under publicly stated Israeli financial-asset service licence 59698. Public records show an active Israeli company incorporated in 2019. [S4]
M&A integration decision · 13 July 2026
KashCash × eToro
An Israel-first path to turn a local digital-cash wallet into a compliant NIS entry point — without importing its current regulatory limits into eToro’s global stack.
01 · Product lens
What KashCash actually is
A regulated Israeli NIS stored-value wallet with bank funding, an internal ledger, P2P transfers and merchant acceptance — not a card issuer, global payment network or crypto platform.
Pre-funded ledger
Users load NIS from a verified bank account through payment initiation or bank transfer. P2P payments are ledger reallocations; merchant funds settle out to bank accounts. [S5]
Technology depth
POS partnerships prove some integration capability, but no public API, webhooks, SDK, sandbox, service-level data or security certification was found. [S6]
02 · Executive verdict
Buy the capability, not the perimeter
The winning structure separates KashCash’s useful wallet technology and Israeli reach from the current product terms and licence constraints.
Recommendation
Proceed to an 8-week diligence and Israel pilot design. Do not connect today’s KashCash wallet directly to eToro trading or Bit2C crypto.
Why: KashCash’s public terms prohibit crypto, securities, FX, credit and financial-services transactions. The integration must be a redesigned, separately governed product. [S3]
03 · Regional pathways
Three markets, three operating models
The product idea travels. The KashCash regulated entity does not.
Proposed scope
●
NIS wallet/sub-account: same-name bank funding, real-time available balance, withdrawal and statements.
●
Bit2C gate: explicit transfer from payment ledger to Bit2C after enhanced KYC, source-of-funds and risk approval.
●
Local utility: optional merchant QR/P2P/family features that make the account useful before investment.
●
Licence design: map the 2023 Payment Services and Payment Initiation law, transitional position and change-of-control requirements. [S7]
●
Crypto AML: Bit2C/eToro licence 72080, Travel Rule readiness, chain analytics and complete fiat/crypto lineage. [S8]
●
Hard boundary: no unverified or touch-anonymous balance may fund crypto, securities, FX or eToro UK trading.
Proposed scope
●
Use eToro entities: eToro USA and eToro NY already disclose FinCEN MSB registrations and state money-transmission/virtual-currency licensing. [S9]
●
Sponsor-bank structure: consumer wallet/FBO arrangement with ACH and, later, instant-payment rails; do not commingle broker-dealer, crypto and wallet balances.
●
Regulation E: prepaid/P2P disclosures, receipts, periodic history, unauthorised-transfer liability and error resolution. [S10]
●
Financial crime: BSA/AML programme, OFAC screening, fraud and account-takeover controls, SAR/CTR/recordkeeping where applicable. [S11]
●
Tax data: preserve lot and transaction lineage needed for digital-asset broker reporting, including Form 1099-DA requirements. [S12]
●
Remove anonymity: no anonymous proximity transfer for a US investment funding product.
Proposed scope
●
Fiat layer: eToro Money Malta is authorised for electronic money and payment services; extend its ledger and account experience rather than passport SafeCash. [S13]
●
Crypto layer: eToro Europe publicly states a CySEC MiCA authorisation, enabling an existing EEA crypto perimeter. [S13]
●
PSD2/next regime: payment-account, safeguarding, SCA, consumer-rights and open-banking requirements remain in the payment entity. [S14]
●
Travel Rule: transfer data and counterparty controls under the EU Transfer of Funds Regulation for crypto flows.
●
Privacy: define controller/joint-controller/processor roles, conduct DPIAs and control Israel/EEA data transfers. [S15]
●
Go/no-go: do not duplicate eToro Money unless KashCash technology produces a measured 12+ month speed or cost advantage.
Preliminary regulatory analysis only. Launch scope and licence conclusions require local counsel and regulated-entity compliance approval.
04 · Target architecture
One experience. Explicit regulated boundaries.
The UX may feel unified, but every movement is typed, permissioned, reconciled and attributable to the correct legal entity.
Funding
Verified bank account
Payment initiation / bank transfer · same-name validation · device and fraud signals · consent evidence
Payment perimeter
NIS / fiat wallet ledger
Safeguarded funds · double-entry ledger · P2P / merchant utility · statements · reconciliation · limits
Controlled gate
Bit2C / eToro account
Enhanced KYC · source of funds · sanctions/AML · crypto Travel Rule · investing and wallet services
Non-negotiable: proximity-private or low-KYC money is ring-fenced. Only verified, attributable funds can cross from the payment ledger into crypto or securities.
| Proposed API | Purpose | Critical controls | Events / webhooks |
|---|---|---|---|
POST /v1/customers | Create linked identity across wallet and regulated account. | Entity routing, consent, age, residency, duplicate detection. | customer.created, kyc.updated |
POST /v1/wallets | Open local-currency wallet/sub-account. | Licence eligibility, safeguarding account, limits profile. | wallet.opened, wallet.restricted |
POST /v1/funding-intents | Initiate same-name open-banking deposit. | SCA, consent, bank-account ownership, idempotency. | funding.authorized, funding.settled |
POST /v1/transfers | Move value between internal sub-accounts or users. | Transfer type, counterparty KYC tier, velocity, sanctions/fraud. | transfer.posted, transfer.reviewed |
POST /v1/investment-gates | Request wallet-to-Bit2C/eToro movement. | Enhanced KYC, source of funds, purpose, AML decision. | gate.approved, gate.denied |
GET /v1/reconciliation | Prove ledger, bank/trust and settlement alignment. | Immutable snapshots, four-eyes review, aged exceptions. | recon.break_detected, recon.closed |
05 · Delivery roadmap
Prove the ledger before the growth story
The first milestone is not launch. It is evidence that the technology, safeguarding and regulatory model are acquisition-grade.
01
0–90 days
Diligence + design
- Source code, architecture and dependency audit
- Licence/change-of-control legal map
- Trust-account and daily reconciliation evidence
- User/POS cohort and unit-economics validation
- Israel target operating model and API contract
- Threat model, penetration test and fraud review
02
3–6 months
Controlled Israel pilot
- Employee / invited-client NIS wallet
- Same-name bank funding and withdrawal
- Separate payment and Bit2C ledgers
- Enhanced gate into crypto
- Daily finance/compliance reconciliation
- Support and incident runbooks
03
6–12 months
Scale or contain
- Broader Israel launch if gates pass
- Merchant/P2P utility experiments
- Evaluate eToro Money feature reuse in EEA
- US sponsor-bank and Reg E discovery only
- Decide acquisition, partnership or IP/talent deal
- Retire duplicated stack aggressively
Executive sponsor
Israel GM / eToro crypto leadership. Owns strategic scope, M&A posture and go/no-go.
Accountable workstreams
Payments, Bit2C, Legal, Compliance/MLRO, Finance/Treasury, Security, Data, Product and Operations.
Critical dependencies
SafeCash diligence access, regulator/counsel view, Ofen Finance transferability, bank/trust arrangements and Bit2C closing structure.
06 · Commercial case
Underwrite active behaviour, not registrations
KashCash’s public scale claims are encouraging proof points, but M&A value must be tied to retained transactors, net revenue and eToro funding lift.
Contribution-margin equation
Payment revenue + merchant/interchange revenue + deposit conversion + retention value − rails − fraud − compliance ops − support − safeguarding cost − incentives
Pilot KPIs
≥70%bank-link completion
≥60%30-day funded retention
<15 bpsfraud loss / TPV target
>99.99%ledger posting integrity
100%daily recon closure
+15%Israel funded-account lift
Targets are proposed pilot gates, not forecasts.
07 · Risk register
Five risks decide the deal
Most are resolvable — but only with evidence before commercial commitment.
| Risk | Severity | Why it matters | Mitigation / gate |
|---|---|---|---|
| Regulatory mismatch | Critical | Current terms prohibit the exact crypto/securities use case eToro wants. | New product/entity contract; counsel and regulator validation before pilot. |
| Ledger / safeguarding integrity | Critical | A wallet acquisition fails if liabilities cannot be reconciled to safeguarded cash daily. | Independent ledger audit, trust confirmations, break history, insolvency analysis. |
| Anonymous-transfer abuse | Critical | Touch privacy can amplify mule, fraud, sanctions and source-of-funds risk. | Provider-visible identity, tiered limits, graph monitoring, no investment funding. |
| Third-party dependency | High | Open banking, POS and bank/trust contracts may not survive change of control. | Contract assignment review; dual-source critical providers; exit plans. |
| Scale claim quality | High | Registered users and enabled POS locations may not reflect active volume. | Transaction-level cohort proof, merchant activation, TPV and retention. |
| Stack duplication | Medium | EEA/UK features overlap with eToro Money and existing card/payment capabilities. | Buy-versus-build benchmark; explicit component retirement plan. |
| Data/privacy transfer | Medium | Identity, location, contacts and financial data cross multiple entities and regions. | DPIA, controller mapping, minimisation, retention and transfer safeguards. |
08 · Diligence questions
Questions that turn marketing into evidence
The public footprint is enough to justify diligence, not enough to price or integrate the business.
Regulatory and legal
What exact activities are authorised under licence 59698? What payment-services transition filings exist? Have regulators approved the current wallet, merchant settlement, minors and proximity transfer models? What changes are triggered by control, branding or crypto adjacency?
Safeguarding and reconciliation
Which bank holds the trust account? Who is the legal beneficiary? Provide daily liability-to-cash reconciliation for 24 months, all breaks, aged exceptions, maker-checker controls, auditor reports and insolvency opinions.
Technology and APIs
Provide architecture, code, deployment topology, ledger schema, idempotency controls, event model, POS protocols, internal APIs, webhooks, DR tests, RTO/RPO, uptime and peak-throughput evidence.
Security and fraud
Provide penetration tests, mobile security reviews, key management, device-binding, SIM-swap controls, ATO rate, fraud typologies, sanctions tooling, investigation workflow and material incident history.
Customers and economics
Reconcile 252k users and 43.2k POS claims to MAU, monthly transactors, TPV, balances, merchant activation, retention, incentive-adjusted CAC, gross/net take rate, support and compliance cost.
Partners and transferability
Provide agreements with Ofen Finance, banks, trust arrangements, BDO, POS vendors, EasyCard and retail chains. Identify exclusivity, assignment, change-of-control, pricing and termination clauses.
Data and privacy
Map all personal data, contact/location permissions, children’s data, retention, deletion, subprocessors, cross-border storage, breach history and consents for reuse inside the eToro group.
People and IP
Confirm IP ownership, open-source exposure, employee/contractor invention assignment, key-person dependencies, retention packages, patents/trademarks and code maintained by third parties.
Next decision
Authorise diligence — with an Israel pilot as the only near-term product thesis.
Do not price global optionality until SafeCash proves technical separability, licence viability, safeguarded-money integrity and active-user economics.
Go
8-week diligence
Code + security + licence + safeguarding + cohort + partner-contract review.
No-go
Direct wallet plug-in
No current KashCash balance should fund crypto, securities or FX under today’s public terms.
Preferred deal
Carve-out / acquisition option
Secure technology, talent and Israeli distribution with staged consideration tied to regulatory and cohort milestones.
Fallback
Commercial partnership
Pilot bank-to-Bit2C funding orchestration without acquiring the consumer wallet liabilities.
09 · Evidence
Primary sources first
Public claims are cited to official product, regulator, app-store and eToro/Bit2C materials. Full bibliography is included in the project files.
S1KashCash Business — claimed users, POS footprint, retail chains
S2KashCash small-business product — 0.4% merchant fee and settlement
S3KashCash consumer terms — licence, limits, rails and prohibited transactions
S4KashCash about / corporate identity and licence claim
S5KashCash FAQ — bank funding, transfer, trust and operational flows
S6EasyCard–KashCash merchant integration evidence
S7Israel Payment Services and Payment Initiation Regulation Law
S8Bit2C announcement — eToro group transaction and licence 72080
S9eToro US MSB, money-transmission and virtual-currency disclosures
S10CFPB Regulation E and consumer electronic-transfer protections
S11FinCEN MSB BSA/AML controls
S12IRS Form 1099-DA instructions for 2026
S13eToro Europe, eToro Money Malta and MiCA licence disclosures
S14European Commission payment-services framework
S15EDPB controller / processor responsibilities
+Open the complete 49-source bibliography and caveats
Legal and regulatory analysis is preliminary, not legal advice, and must be validated by qualified counsel and the relevant regulated-entity compliance teams.