
Israeli Payment Orchestrator
Implement Israeli card acquiring, installment semantics, and gateway-specific fields without mixing Shva CreditType codes or installment programs.
Overview
Israeli Payment Orchestrator is an agent skill for the Build phase that encodes Israeli card gateway credit-type and installment rules for correct payment API payloads.
Install
npx skills add https://github.com/skills-il/tax-and-finance --skill israeli-payment-orchestratorWhat is this skill?
- Documents Shva CreditType (סוג אשראי) codes 1–9 including credit (6) vs Isracredit (2) and club installments (9)
- Separates regular installments (תשלומים), credit installments (קרדיט), and club (מועדון) merchant vs bank interest model
- Grounds claims in gateway matrix references for Israeli orchestration and Tranzila-style parameters
- Helps agents pick correct cred_type and installment caps (often up to 36 payments) per gateway rules
- Shva CreditType enum distinguishes codes 1, 2, 3, 4, 5, 6, 8, and 9 for Israeli credit products
- Maximum installments typically 36 on referenced Israeli gateway patterns
Adoption & trust: 1 installs on skills.sh; 22 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are integrating Israeli payments but CreditType, installment (תשלומים), and credit (קרדיט) enums are easy to confuse across gateways and docs.
Who is it for?
Solo founders building Israeli B2C checkout, billing portals, or marketplace payouts that must speak local acquirer dialects.
Skip if: US/EU-only Stripe-only stacks with no Israeli acquirer, or pure tax filing without payment capture.
When should I use this skill?
Implementing or reviewing Israeli payment capture, installments, or gateway-specific credit type fields.
What do I get? / Deliverables
After the skill runs, orchestration code and agent-generated handlers use the right Shva-style codes, installment modes, and gateway matrix fields for Israeli checkout.
- Correct cred_type and installment mapping in orchestration code
- Gateway matrix-aligned parameter checklist for Israeli checkout
Recommended Skills
Journey fit
Payment orchestration is wired during product build when checkout and billing integrations go live. Israeli gateways (Shva, Tranzila-class flows) are third-party payment integrations with locale-specific enums and compliance nuances.
How it compares
Use alongside generic payment skills when you need Israel-specific cred_type truth tables, not a global Stripe wrapper.
Common Questions / FAQ
Who is israeli-payment-orchestrator for?
Indie developers and small teams implementing Israeli card payments, installments, and gateway-specific fields in web or mobile commerce backends.
When should I use israeli-payment-orchestrator?
Use it in Build → integrations while designing checkout APIs, mapping Tranzila/Shva parameters, or reviewing agent-generated payment code before staging certification.
Is israeli-payment-orchestrator safe to install?
Payment skills touch money movement—check the Security Audits panel on this page, never paste live API secrets into chats, and validate against your acquirer’s current PDF spec.
SKILL.md
READMESKILL.md - Israeli Payment Orchestrator
{ "schemaVersion": "1.0", "skill": "israeli-payment-orchestrator", "generated_at": "2026-06-07T00:00:00Z", "claims": [ { "claim_id": "shva-credittype-codes", "claim": "Shva CreditType (סוג אשראי) enum, a field distinct from transaction type (סוג עסקה): 1=regular/immediate, 2=Isracredit/30+, 3=immediate debit, 4=club credit, 5=Leumi special, 6=credit installments (קרדיט, interest to bank), 8=regular installments (תשלומים, merchant-financed), 9=club installments (מועדון). Interest-free installments use CreditType 8 (merchant subsidizes). Credit (קרדיט) is 6, NOT 2; club installments are 9, NOT 3.", "source_url": "https://github.com/astrails/active_merchant_tranzila", "raw_snippet": "cred_type: 1 Regular, 2 Isracredit/30+, 3 Immediate debit, 4 Club Credit, 5 Leumi special, 6 Credit (קרדיט), 8 Installments (תשלומים), 9 Club installments (מועדון).", "fetched_at": "2026-06-07T00:00:00Z", "appears_in": ["SKILL.md", "SKILL_HE.md", "references/gateway-matrix.md"] }, { "claim_id": "installment-types", "claim": "Installment type semantics: regular installments (תשלומים) - merchant gets the full amount upfront, the bank collects from the customer monthly, no interest by default; credit installments (קרדיט) - the customer pays the bank in installments with interest, merchant gets full amount; club installments (מועדון) - issuer-specific program (Isracard, CAL, Max). Maximum installments typically 36 (some gateways cap at 12 or 24); Shva may enforce a minimum per-installment amount.", "source_url": "https://docs.tranzila.com/", "raw_snippet": "תשלומים רגילים: בית העסק מקבל את מלוא הסכום, הבנק גובה מהלקוח חודשית ללא ריבית; קרדיט: הלקוח משלם לבנק עם ריבית; מועדון: תוכנית מנפיק. עד 36 תשלומים (חלק מהשערים עד 12/24).", "fetched_at": "2026-06-07T00:00:00Z", "appears_in": ["SKILL.md", "SKILL_HE.md", "references/gateway-matrix.md"] }, { "claim_id": "gateway-api-styles", "claim": "Gateway API styles: Cardcom REST JSON; Tranzila REST / form-POST (form-encoded key-value); PayMe bearer-token REST JSON; Meshulam/Grow multipart/form-data (NOT JSON), server-side only, Light API at secure.meshulam.co.il/api/light/server/1.0/; iCredit REST JSON; Pelecard REST JSON. Bit support by default: PayMe yes, Meshulam yes, others no. Fee ranges (0.5-1.0%) are indicative and negotiation-dependent.", "source_url": "https://grow-il.readme.io/reference/overview", "raw_snippet": "Grow (Meshulam) Light API requires multipart/form-data, not JSON, server-side only; Cardcom uses JSON; Tranzila uses form-encoded params; PayMe uses bearer-token JSON.", "fetched_at": "2026-06-07T00:00:00Z", "appears_in": ["SKILL.md", "SKILL_HE.md", "references/gateway-matrix.md", "scripts/compare_gateways.py"] }, { "claim_id": "regulation", "claim": "Israeli payment-services regulation: the Regulation of Payment Services and Payment Initiation Law 5783-2023 makes the Israel Securities Authority (ISA) the primary regulator of non-bank payment service providers; the Bank of Israel supervises banks and credit-card companies and oversees Shva as a controlled payment system. Shva (שב\"א, Automatic Bank Services) still operates the credit-card clearing network. Transaction data retention 7 years; PCI DSS tokenization (never store full PANs); 3DS2 for card-not-present transactions.", "source_url": "https://www.boi.org.il/en/economic-roles/supervision-and-regulation/payment-systems-oversight/", "raw_snippet": "חוק הסדרת העיסוק בשירותי תשלום ויוזמה בתשלום, התשפ\"ג-2023: רשות ניירות ערך מפקחת על נותני שירותי תשלום שאינם בנק; בנק ישראל מפקח על הבנקים וחברות כרטיסי האשראי ומפקח על שב\"א.", "fetched_at": "2026-06-07T00:00:00Z", "appears_in": ["SKILL.md", "SKILL_HE.md"] }, { "claim_id": "reference-urls-and-figures", "claim": "Reference URLs for the gateways and the BOI oversight page, plus illustrative figures (