Israeli Payment Orchestrator
Verified91/100Orchestrate Israeli payment gateways (Cardcom, Tranzila, PayMe, Meshulam, iCredit, Pelecard) with unified routing, fallback, and installments (tashlumim). Use when user asks about multi-gateway payment integration, "slikat kartisim", "tashlumim", payment routing, Shva network, BOI payment-services regulation, gateway comparison, or building a payment abstraction layer for Israeli merchants. Provides unified API patterns, installment handling, Shva clearing rules, and regulatory compliance. Do NOT use for single gateway setup (use cardcom-payment-gateway or tranzila-payment-gateway instead).
Trust score 91/100 (Verified) · 16+ installs · 3 GitHub contributors · MIT license
Israeli businesses accepting online payments need to work with local payment gateways like Cardcom, Tranzila, and PayMe. Each provider offers a different API, different report formats, and different terms. Managing multiple payment providers simultaneously is complex, and payment errors directly impact cash flow.
skills-ilHow to use this skill
Not sure how? Read the guide- 1. Click "Download ZIP" to download the skill files.
- 2. Open Claude Desktop and go to Customize > Skills.
- 3. Click "+" and select "Upload a skill", then upload the ZIP file.
- 4. Start a new conversation. The skill will activate automatically when relevant.
Developers? Install via command line (CLI)
npx skills-il add skills-il/tax-and-finance@v1.2.0-israeli-payment-orchestrator --skill israeli-payment-orchestrator -a claude-codeWhen to Apply
- When the user is integrating two or more Israeli payment gateways (Cardcom, Tranzila, PayMe, Meshulam, iCredit, Pelecard) and needs a unified abstraction
- When the user wants automatic fallback or routing between gateways for high availability or cost optimization
- When the user asks how Israeli installments (tashlumim regilim, kredit, mo'adon) map to Shva clearing codes across different gateways
- When the user is designing recurring billing or token-based subscriptions and needs to compare gateway support
- When the user needs to comply with Bank of Israel Directive 357, PCI DSS, and Shva clearing rules across a multi-gateway setup
Try These Prompts
I run a small online store in Israel with about 50,000 NIS monthly turnover. Which payment gateway is best for me among Cardcom, Tranzila, and Grow?
I want to offer customers the option to pay in 3 interest-free installments on my website. How do I set this up with a payment gateway and what are the commission costs?
A customer tried to pay on my site but the transaction failed. What are the common reasons for payment failures in Israel and how do I help the customer complete the purchase?
Frequently Asked Questions
Changelog
Corrected that Tranzila also supports club installments (cred_type 9), fixed moved Grow/Cardcom docs links, and added gotchas on cross-gateway token non-portability, server-side verification, and 3DS2.
Jul 20, 2026
v1.1.1: fixed the Shva CreditType codes (credit=6 not 2, club=9 not 3; clarified CreditType vs transaction type), corrected the Meshulam API style to multipart/form-data everywhere, and fixed the dead Bank of Israel link plus the regulator framing (ISA regulates non-bank payment-service providers; BOI oversees banks and Shva).
Jun 7, 2026
Added Reference Links section with 6 official-docs URLs (Cardcom, Tranzila, PayMe, Meshulam/Grow, iCredit, BOI), reinforcing the production base for Meshulam.
May 5, 2026
Related Skills
Author: skills-ilIntegrate Grow by Meshulam payment gateway into Israeli applications -- covers payment pages (iframe/redirect/SDK), tokenization, recurring billing, payment links, refunds, invoices, webhooks, and 3DS authentication via the Grow Light API. Use when user asks to accept payments via Grow or Meshulam, set up "slikat ashrai" with Grow, create payment links (drishat tashlum), handle recurring charges (hora'ot keva) via Grow tokens, process refunds or Bit cancellations, integrate Grow webhooks, or mentions "Grow", "Meshulam", "grow-il", "meshulam.co.il", Grow payment page, or Grow API. Prevents costly integration mistakes by guiding correct FormData request format, server-side-only restrictions, and the mandatory approveTransaction step that many developers miss. Do NOT use for Cardcom integration (use cardcom-payment-gateway), Tranzila integration (use tranzila-payment-gateway), general payment orchestration across multiple gateways (use israeli-payment-orchestrator), or non-payment queries.
Author: yonatangrossDetect price gaps between TASE and US listings of the same dual-listed company (Check Point, NICE, CyberArk, Teva, and 40+ pairs), converting via the Bank of Israel representative rate and flagging gaps above a threshold. Use when the user asks to compare a dual-listed stock's Tel Aviv vs NASDAQ/NYSE price, spot cross-listing arbitrage, or understand a premium/discount between exchanges. Provides per-pair gap %, trading-hours-overlap confidence, and currency-adjusted comparison. Do NOT use for single-market analysis (use tase-stock-analysis).
Author: skills-ilSave money in Israel through smart shopping, cashback optimization, subscription auditing, and deal hunting. Covers Zap price comparison, BuyMe strategies, cashback programs, credit card perks, loyalty stacking, seasonal sales, and recurring expense reduction. Helps identify unnecessary subscriptions and maximize savings on everyday purchases.
Use at your own risk. Terms of Use · Security
Want to build your own skill? Try the Skill Creator · Submit a Skill