Payment gateway integration in Israel: card payments, subscriptions and invoices that send themselves
Customers pay by card without leaving your site or app, subscriptions renew without anyone remembering to charge them, and a proper Israeli receipt goes out after every payment. You see who paid, whose charge failed and why.
- A development team in Netanya, Israel
- Card numbers stay with the processor
- Money goes straight to you, not through us
What is payment gateway integration, and what do we build?
Payment gateway integration is the code that connects your website or app to an Israeli card processor and to your invoicing service. We build a checkout inside your site, saved-card tokens held by the processor, recurring billing and installments, a receipt or tax invoice issued automatically after every charge, failed-payment handling and an owner dashboard. We work with the processor you already have, such as PayPlus, or help you choose one.
Where the money gets stuck today
Customers leave your site for a payment page they don't trust
You send a payment link on WhatsApp and it opens a processor page on another domain, with a different design and a company name the customer doesn't recognise. Some ask whether it's safe, others just close the tab, and a deal that was nearly done stays open.
On the 1st of the month, someone charges cards by hand
A subscriber list in Excel, card numbers once read out over the phone, and someone in the office keying in charge after charge on the terminal. When that person is on holiday or on reserve duty, half the month's charges simply don't happen.
Receipts get issued late at night, one at a time
Amounts copied from the processor's report into the invoicing system, a customer's name typed wrong, and right before the VAT report your accountant asks for the receipts that are missing. It comes back every month, and nobody started a business to do it.
A charge fails and nobody notices
The card was replaced, expired or hit its credit limit. The processor logged the failure in a report nobody opens, and the customer keeps using the service. You find out two months later and have to make the awkward phone call.
From the first call to a real charge
Map how you charge today
A short call about what you sell — one-off payments, memberships, installments or deposits — and which processor and invoicing service you use. You show us how it works now; we come back with a map of the flows and a list of open questions.
Choose the processor and invoicing service
Already on PayPlus or another processor? We check that its API supports what you need. Starting from scratch? We compare options together by what matters to your business: recurring charges, installments, Bit and digital wallets, API quality. You sign the agreement and settle the fees directly with the processor.
Build in a test environment
Checkout, saved cards, recurring charges, receipts and failed-payment handling all run first on the processor's sandbox terminal and in the invoicing service's test mode. No real money, no real documents.
Test with a real card
A small charge on a real card, a refund, and a receipt that actually goes out. You or your accountant check that the document looks right before your first customer pays.
Go live
We switch to the production terminal, turn on alerts and the dashboard, and show you and your team where to see payments, how to refund a customer and how to freeze a membership.
Stay with you after launch
In the first period we review every failed charge and every alert. Processors and invoicing services update their APIs from time to time, and we update the integration to match.
What you get
- A checkout inside your site or app, in your design, using the processor's secure card fields — no redirect to an outside page
- Saved-card tokens, recurring card billing (horaat keva) and installments
- Subscription management: plans, upgrades, freezes and cancellations — for you and for the customer
- A receipt or tax invoice issued automatically after every charge and emailed to the customer
- Failed-charge handling: retries by your rules, a reminder with a card-update link, and an alert to you
- An owner dashboard: who paid, when, what failed and why — with an export for your accountant
- Terms, cancellation and privacy policies placed where they belong on the site — worded by your lawyer
Four common ways to bill
Pilates studio or gym memberships
Monthly memberships renew on their own, customers get a message with a renewal link when their class pass is about to run out, and a membership can be frozen for reserve duty or a trip abroad in one click — without cancelling and re-creating the standing order.
Online course paid in installments
Israeli customers expect to split a course into tashlumim. They pick the number of payments at sign-up, access opens only after the charge is approved, and the receipt is already in their inbox. Card-company installments and a fixed-term monthly charge behave differently when a card fails — we'll explain which suits your course.
Monthly B2B retainer
A marketing agency, IT support or bookkeeping firm: the monthly charge runs on a fixed date and the tax invoice goes straight to the client's accounts department, without anyone on your side having to remember to issue it.
SaaS or app with paid plans
A free trial that turns into a paid plan, an upgrade in the middle of the month, cancellation from the customer's account page. The system always knows who should have access, because the status comes straight from the processor.
Automatic Israeli receipts and tax invoices
Israeli invoicing has its own rules, and your accountant already has a system they trust. After every successful charge, our code calls your invoicing service's API — Morning (formerly Green Invoice) and iCount are two Israeli services with public APIs — and issues the right document. VAT, numbering and document type are handled by the invoicing service, using the settings your accountant chose. We don't do your bookkeeping; we make sure the right document goes out and reaches the customer.
- A VAT-exempt osek patur issues a receipt; an osek murshe or a company issues a tax invoice/receipt
- A refund made at the processor also produces the matching credit document, so it doesn't get lost
- Tax Authority allocation numbers, where the law requires them, are requested through the invoicing service
- The document is emailed to the customer, and a copy stays in your invoicing system
- A charge with no document behind it shows up as an alert, not as a surprise at month-end
What usually breaks in a payment integration — and what we check before launch
Most payment bugs don't show up in the first test. They appear in month two, when a standing order tries to charge a saved card, or when a customer closes the browser halfway through paying. This is what we check in advance:
- Payment confirmation comes from the processor's server, not only from the customer's browser — otherwise a customer who closed the tab is recorded as unpaid
- The terminal is set up to allow charging a saved card — some settings, such as requiring CVV on every transaction, block recurring charges
- Not every payment method works for a standing order — we check with the processor before you offer customers a monthly plan
- A double click on the pay button doesn't charge the customer twice
- API keys live only on the server — not in browser code and not in logs
- Some processors accept API calls only from a registered server address, so we set that up before going live
Card data, privacy and who owns the accounts
Card numbers are typed into the processor's secure field and don't pass through your server. What you keep is a token, the last digits for display and the payment history. We design the customer database with Amendment 13 to Israel's Privacy Protection Law in mind, and the processor and invoicing accounts are opened in your business's name.
- The processor agreement is in your name, and the money goes straight to you, not through us
- Role-based access: who sees payments, who can refund and who can only view
- An activity log: who refunded, who froze a membership and when
- Export your data to your accountant or another system whenever you want
Tell us in one message how you charge today: which processor, how receipts go out and what happens when a charge fails. We'll come back with a sketch of the automated flow.
Processors, invoicing services and channels we can connect
- PayPlus
- Cardcom
- Tranzila
- YaadPay (Hyp)
- Morning (Green Invoice)
- iCount
- Bit
- Apple Pay
- Google Pay
- WhatsApp Business API
- n8n
- Google Sheets
If a system has an API, we can usually connect it. If it doesn't, we'll tell you upfront.
How a project with us runs
The same four steps, whether it's a bot, an integration or a whole system.
Short call
You tell us what's slowing you down and how you work today. We ask questions — and if a ready-made tool fits, we'll say so.
Your partDescribe the task in your own words
Written proposal
Scope, stages and a cost estimate in writing, including who owns the code, the accounts and the data.
Your partReview, ask questions, decide
Build in stages
You see working parts early and try them on real cases. Your feedback goes straight into the next stage.
Your partTest and give feedback
Launch and support
We launch, watch how it behaves in real use and stay on for fixes and improvements.
Your partUse it and tell us what to improve
What affects the cost
- How many payment types you need: one-off, subscription, installments, deposits
- Whether you already have a processor and invoicing service, and what their APIs can do
- Subscription logic: plans, mid-month upgrades, freezes, free trials
- Where the payment lives: an existing site (and what it's built on) or a new system
- What happens when a charge fails: retries, reminders by email or WhatsApp
- The dashboard and the reports your accountant needs
- Languages and currencies on the checkout
Processor fees and the invoicing service subscription are paid directly to those companies and aren't part of our price. You get a written estimate after a short call — phone or WhatsApp us on 050-854-2579.
Ownership, privacy and accessibility
Your code and data
Ownership of the code and data is agreed in writing before we start: who owns the source code, the accounts and the information is in the agreement — not something you find out at the end.
Privacy by design
We build with Israel's Privacy Protection Law and Amendment 13 in mind: we collect only what's needed, keep secrets on the server and agree with you where the data is stored.
Accessibility built in
Interfaces built with IS 5568 and WCAG AA in mind: keyboard navigation, contrast, screen-reader labels and right-to-left layouts.
Payment integration: frequently asked questions
How much does payment gateway integration cost?
It depends on how many flows we build. A one-off checkout on an existing site is a very different job from a subscription system with plans, freezes, installments and automatic invoices. The technology behind your current site and the quality of the processor's API matter too. Processor fees are separate. Message us on WhatsApp with what you sell and how you charge today, and we'll come back with a written estimate.
Which processor should we use — and can you work with the one we have?
Usually it makes sense to stay with your current processor, as long as its API supports what you need; we check that on the first call. If you don't have one yet, we compare by expected volume, recurring billing, installments, Bit and wallets, and your bank. PayPlus, Cardcom and Tranzila are examples of Israeli processors with APIs. If you know Stripe or PayPal from abroad, check that the provider supports your Israeli business and your customers' payment methods.
Do you store our customers' card numbers?
No. The customer enters the card in the processor's secure field; the processor stores it and returns a token — an ID that can be charged again only through your terminal. You keep the token, the last digits for display and the payment history. So there are no card numbers sitting on your website, in your database or in an office spreadsheet.
Can customers pay monthly with Bit, Apple Pay or Google Pay?
Not always. Recurring charges depend on the processor and the payment method: Bit and some digital wallets don't always let you save the payment method for the next charge. So we check with the processor before you advertise a monthly plan. The common setup is a credit card for subscriptions and Bit or a wallet for one-off payments.
Will the receipts and invoices satisfy our accountant?
The documents are issued by your invoicing service, not by our code, so they come in the format your accountant already knows. Document type, VAT, numbering and allocation numbers follow the settings your accountant chose in that service. Our job is to make sure the right document goes out after every charge and every refund, and that a charge without a document shows up as an alert.
How long does it take, and what happens after launch?
Timing depends mainly on three things: how many flows you need, whether the site already exists, and how quickly the processor opens a terminal and approves API access — that part isn't in our hands. After launch we stay on: we watch failed charges and alerts, and we update the integration when the processor or the invoicing service changes something.
Tell us how you charge today
One WhatsApp message to 050-854-2579 or a short form: what you sell, which processor and which invoicing service you use. We'll come back with a sketch of the automated flow and the questions worth answering first — and if a ready-made tool is enough for you, we'll say so.
Tell us in one message how you charge today: which processor, how receipts go out and what happens when a charge fails. We'll come back with a sketch of the automated flow.
Prefer to talk? Call050-854-2579