Short answer: Most Israeli SaaS and e-commerce businesses accept cards through a local gateway such as Cardcom, Tranzila, Grow (formerly Meshulam), Hyp or Pelecard, because these run on Israel's domestic card rails and support local features like installments and Bit. The decision that matters most is the integration pattern, not the vendor: a hosted page or iframe plus card tokens keeps card data off your servers and your PCI scope small.
Key takeaways
- Local rails: Shva connects merchant terminals with Israel's issuers and acquirers for authorization and settlement, as a Bank of Israel report describes.
- Installments are a product decision: regular installments split the total into equal interest-free payments, credit installments add interest over three or more, and the card company runs the schedule (per Hyp's documentation).
- Tokens for subscriptions: Tranzila, Hyp and Pelecard all offer tokenization, so recurring charges never touch raw card numbers.
- Redirect or iframe: a full redirect to a PCI-compliant processor sits outside the SAQ A script-attack criterion in force since April 1, 2025 (PCI SSC); an embedded iframe falls under it.
Choosing an integration pattern
Pick the pattern first, then the gateway that implements it best for your volume.
| Pattern | How it works | Trade-off |
|---|---|---|
| Full redirect | Customer pays on the gateway's page and returns | Lightest PCI burden, least control over UX |
| Embedded iframe | Gateway form inside your checkout | Smoother UX; must show protection against script attacks |
| Server-side token charges | Backend charges a stored token | Required for subscriptions and usage billing; the first token is still collected via redirect or iframe |
Bit, Apple Pay and Google Pay are offered by several local gateways, but rules differ between wallets, so confirm whether a wallet allows installments before promising them at checkout.
