Stripe or an Israeli Gateway? The Questions That Actually Decide

I will start with the conclusion: Stripe is nicer to develop against, and that is the weakest reason to choose it. The developer-experience gap is worth a few days of work. Getting the instalments or invoicing question wrong is worth a rebuild.

This article gives no fee table - rates are negotiated per business and per volume, and any figure I published would be wrong for you. It is about the four questions that actually decide.

Question 1: do your customers want to pay in instalments?

This is the first question, and it usually decides on its own.

Splitting a charge into monthly instalments is a standard expectation of Israeli consumers, not a nice-to-have. A business selling a several-thousand-shekel product without offering instalments loses sales - that is not theoretical.

In Israeli gateways this is a core, built-in capability. Grow, for instance, supports splitting into up to 12 instalments as part of the flow.

Do not assume a direct equivalent exists elsewhere. "Instalments" in the Israeli sense - splitting a card charge into monthly payments through the card issuer - is not the same as "buy now, pay later" products in other markets, which are typically third-party lending with a separate approval process.

If the business needs instalments, that is nearly a final answer in favour of a local gateway.

Question 2: who issues the invoice?

An Israeli business must issue tax documents. The question is who connects the payment to the document.

• A local gateway: often has a built-in or well-trodden connection to the Israeli invoicing systems - Morning, iCount, EZcount, Rivhit. Some gateways issue a document themselves.
• Stripe: does not know what an Israeli tax invoice is, what an allocation number is, or the difference between a tax invoice and a combined invoice-receipt. That entire connection is yours.

It is not impossible - it is additional work that belongs in the estimate rather than being discovered afterwards.

Question 3: currency and payouts

Here I am careful, and you should be too.

Country support and local-currency payout support are two separate questions. A provider can accept payments from a country without settling in the local currency, and the answer changes over time and by account type.

What to verify directly with the provider before designing anything:

1. Can an Israeli business open an account through the standard process, and under what conditions?
2. In which currency is money settled to a bank account, and to what type of account?
3. What is the conversion cost if settlement is not in shekels?
4. What is the cycle time until money is in the bank?

Do not rely on an article, including this one. Eligibility and currency questions change, and the relevant answer is the one you got in writing from the provider for your account.

A point easy to miss: if settlement is not in shekels, a conversion layer is added that affects both real cost and accounting reconciliation - because the amount landing in the bank will not equal the amount charged.

Question 4: who your customers are

This is the question that flips the answer:

That last row is not said often enough: there is no rule against two gateways. A business selling both in Israel and abroad can use a local gateway for the local market and an international provider for the international one.

The cost: two integrations to maintain and two reconciliation processes. That is a real cost - but it is usually lower than forcing one provider onto a market it does not fit.

What holds regardless of the choice

Once decided, these apply either way - and they are the difference between an integration that holds and one that loses orders:

• Webhook, not redirect. The browser redirect depends on the customer staying on the page. Anyone who closes the tab the moment payment clears never reaches it, and the order stays "pending" while the money has been taken.
• Idempotency. The same notification can arrive twice.
• Cross-check the amount against the order, server-side, always.
• Do not touch card details. That is the whole benefit of a hosted page, and it holds only if you do not send, log or store them.
• Who issues the document - one side only, documented in advance.

How to decide in practice

1. Does the business need instalments? If yes - a local gateway, and we are nearly done.
2. Who are the customers? Israeli consumers lean local; business customers abroad lean international.
3. Verify eligibility and currency in writing with the provider you are considering.
4. Price the invoicing connection - with an international provider that work is yours.
5. Fees - a conversation with the providers, not a technical consideration. Preferably with three.
6. Developer experience - last. Always.

And finally, the most important thing: if the business already works with a gateway, the recommendation is almost always not to switch. A gateway carries a contract, negotiated rates and a relationship. Recommending a change because another API is nicer is bad advice.