Pelecard Payment Gateway
Trusted89/100Integrate Pelecard payment processing into Israeli web and mobile apps -- covers iframe payment flow on gateway21.pelecard.biz, ActionType selection (J2/J4/J5/J5h), tashlumim (installments), tokenization, ConfirmationKey server-side validation via PaymentGW/GetTransaction, refunds, 3D Secure 2, Bit wallet, and Apple Pay via ClientSecure.js. Use when user asks to accept payments via Pelecard, set up "slikat ashrai" with Pelecard, validate a Pelecard callback, charge a saved Pelecard token, or mentions "Pelecard", "פלאקארד", "gateway21", "PelecardStatusCode", or "ConfirmationKey". Do NOT use for Cardcom (use cardcom-payment-gateway), Tranzila (use tranzila-payment-gateway), Grow/Meshulam (use grow-payment-gateway), multi-gateway orchestration (use israeli-payment-orchestrator), or invoice generation (use green-invoice).
Trust score 89/100 (Trusted) · 5+ installs · 3 GitHub contributors · MIT license
Pelecard is a Payment Service Provider (PSP) and one of the largest Israeli card-acquiring aggregators, but its public documentation is scattered across a Postman workspace, a sandbox UI, a WordPress plugin listing, and third-party PHP libraries, with no single canonical reference. Agents that try to integrate Pelecard end up confusing the legacy gateway20 host with the production gateway21, picking the wrong ActionType (which silently changes whether money actually moves), or trusting a browser-side ConfirmationKey instead of re-verifying server-side. Each of those mistakes leaks revenue or, worse, ships an exploitable free-order path to production.
How 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.0.3-pelecard-payment-gateway --skill pelecard-payment-gateway -a claude-codeWhen to Apply
- When integrating Pelecard for the first time on an Israeli site or app
- When you need to create an iframe URL on gateway21.pelecard.biz and validate the callback server-side
- When implementing recurring billing (hora'ot keva) on a stored token
- When handling tashlumim (installments 2-36) or 3D Secure 2
- When adding Bit wallet as a payment option and designing around the per-transaction cap
Try These Prompts
How do I integrate Pelecard on my Israeli site, create an iframe URL on gateway21, and store the ConfirmationKey for callback verification?
My server received a Pelecard callback with PelecardStatusCode and ConfirmationKey, how do I validate it server-side before marking the order paid?
I want to charge a customer ₪99 monthly for a subscription. How do I save a Pelecard token and handle MIT / 3DS on renewals?
How do I add Bit as a Pelecard checkout option, and why do I need to cap amounts around ₪5,000?
Frequently Asked Questions
Changelog
Clarified that Gateway21 also exposes its own sandbox environments, so the "gateway20 = sandbox" split is not a hard rule.
Jul 20, 2026
v1.0.2: fixed a misattribution to the dofinity library (real paths: PaymentGW/init for create and PaymentGW/ValidateByUniqueKey for validation; GetTransaction is a Gateway21 lookup; the library is pinned to gateway20). Resolved the create-session path to PaymentGW/init, clarified that GetTransaction does not return the ConfirmationKey, and fixed an invalid supported_agents slug.
Jun 7, 2026
Related Skills
Orchestrate 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).
Integrate 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.
Detect 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).
Use at your own risk. Terms of Use · Security
Want to build your own skill? Try the Skill Creator · Submit a Skill