Cardcom Payment Gateway
Trusted85/100Integrate Cardcom payment processing and Israeli invoice generation into applications, covering Low Profile payments, tokenization, recurring billing, and automatic tax invoice/receipt creation per Israeli law. Use when user asks to accept payments via Cardcom, generate Israeli invoices with payments, set up "slikat ashrai" with hashbonit, handle recurring billing (hora'ot keva), or mentions "Cardcom", "CardCom API", "Low Profile", Israeli payment with invoicing, or needs combined payment plus document generation. Targets the REST API V11. Do NOT use for Tranzila integration (use tranzila-payment-gateway), general accounting, or non-payment queries.
Trust score 85/100 (Trusted) · 63+ installs · 3 GitHub contributors · MIT license
Israeli businesses need both payment processing and legally-compliant tax document generation (invoices, receipts, credit notes) for every transaction. Most payment gateways handle only the payment side, forcing developers to build separate invoicing systems. Cardcom uniquely combines payment processing with automatic Israeli tax document generation in a single REST API V11 call, but its integration patterns (Low Profile, server-to-server Transaction, standalone CreateDocument), tokenization for recurring billing, and Israeli-specific document types require domain knowledge to implement correctly.
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@v2.3.0-cardcom-payment-gateway --skill cardcom-payment-gateway -a claude-codeWhen to Apply
- Accepting payments with automatic Israeli tax invoice/receipt generation
- Building e-commerce checkout with a combined payment plus document flow
- Implementing subscription billing with token charges and monthly invoice generation
- Creating standalone tax invoices or receipts without payment processing
- Adding Bit or PayPal alongside credit card payments
- Processing refunds and issuing the matching credit document
Try These Prompts
How do I accept credit card payments with automatic Israeli invoice generation using the Cardcom V11 API?
Set up a recurring subscription with Cardcom: create a token via Low Profile, then charge it monthly through the Transaction endpoint with invoice generation
How do I process a refund with Cardcom RefundByTransactionId and issue the matching credit document?
Generate a standalone Israeli tax invoice with Cardcom Documents/CreateDocument without processing a payment
Frequently Asked Questions
Changelog
Corrected a core error: ApiPassword was documented as required only for refunds and document creation, when the V11 spec requires it on 19 of the 50 endpoints that take a request body, including ListTransactions. Added Step 6.5 with a full ListTransactions call, and fixed two further errors in the same endpoint family: neither ListTransactions nor SpecialTransactions accepts TerminalNumber, and SpecialTransactions is a read endpoint, not a charge operation.
Jul 28, 2026
Added a section on allocation numbers, which the skill did not cover at all even though it generates Israeli tax documents. There is no allocation-number field in the API and that is deliberate: Cardcom requests it automatically at document creation, but only after a one-time Tax Authority authorization in which both permission types must be selected. Without it, a customer cannot deduct input VAT on any invoice above 5,000 shekels. Corrected the language field guidance: the misspelled Languge applies to the standalone document and transaction objects, but the Low Profile document uses the correct spelling, and since these schemas reject unknown fields the old blanket rule broke the payment flow the skill recommends first. Fixed the request contract for the transaction-lookup endpoint, and fixed the response validator, which was treating a card-validation-only code as success on charges, refunds and document creation. Also corrected the PCI DSS version and softened three claims about test credentials, settlement days and pricing that could not be verified.
Jul 27, 2026
Removed a documentation endpoint that does not exist in the V11 API (Documents/CreateTaxInvoice), clarified the language-field name across the document schemas (Languge vs Language), and documented the real SuspendedDeals/Charge endpoint for charging a suspended deal. All verified against the live V11 OpenAPI spec.
Jul 6, 2026
Related Skills
Author: skills-ilOrchestrate 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).
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).
Use at your own risk. Terms of Use · Security
Want to build your own skill? Try the Skill Creator · Submit a Skill