Israeli bank direct debit through Masav versus recurring card billing: setup, who absorbs a failed collection, cancellation, cost shape and what data each returns to you.
Key takeaways
- A direct debit authorisation requires an institution code from the bank holding the organisation's account. It is a prerequisite for joining, and it takes time.
- With direct debit the bank may decline a charge when there is no cover, and the charge comes back to you as a return.
- The customer can cap the authorisation by amount and period, and cancel it at their bank at any time, without going through you.
- Card failure looks different: the card expires, is replaced or is blocked, and the transaction is declined at the moment of the charge rather than days later.
- Masav also operates the infrastructure for moving direct debit authorisations between banks, so a customer changing bank is not automatically the end of the mandate.
An Israeli direct debit authorisation is permission the customer gives their own bank to honour debit requests from an identified organisation, and the organisation collects by submitting a charges file to Masav. A recurring card charge is a repeat transaction against the card networks through an acquirer. The real difference is not the fee - it is who absorbs failure, how long setup takes, and what information comes back.
Two routes, two architectures
| Dimension | Direct debit authorisation (Masav) | Recurring card charge |
|---|---|---|
| How the organisation is identified | Institution code from the bank | Merchant number with the acquirer |
| What the customer provides | An authorisation at their own bank, optionally capped by amount and term | Card details, usually held as a token by the acquirer |
| How you collect | A charges file uploaded to Masav for a chosen value date | A charge call to the acquirer, usually in real time |
| Typical failure | No cover, authorisation cancelled, account closed | Card expired, replaced, blocked or declined |
| When you learn of failure | In the returns file, after the debit date | In the acquirer's response, immediately |
| What ends by itself | Nothing. The mandate runs until cancelled | The card expires and needs renewal |
When is a direct debit the better route?
When the payment is ongoing, long-lived and its amount can vary - monthly subscriptions, management fees, building committee dues, or collections from business customers. Three operational reasons:
- No expiry. An approved mandate keeps working. There is no annual churn of expired cards to chase customers about.
- Variable amounts. A usage-based billing model fits a charges file better than a fixed recurring card transaction.
- One batch. Thousands of debits go in a single file for a single value date, instead of thousands of individual charge calls.
The price is slower setup. The customer has to establish the mandate with their own bank - in a branch, by phone, or in the authorisations area of the bank's site - and that is a genuine drop-off point in onboarding a new customer.
When is card the better route?
When immediate conversion matters more than long-term stability. A new customer completing a first payment on one page will not stop to establish a bank mandate. Where the first payment and the recurring payment are the same event - sign up and get charged now - card is the natural route.
The second advantage is response time. An acquirer's answer arrives immediately, so you can ask for an alternative payment method while the customer is still on the screen. With direct debit, failure information arrives days later, when they are long gone. The acquirers themselves are compared in Israeli payment gateways compared.
What happens when a collection fails - and how long it takes
This is the difference you feel most in operations. With card acquiring the decline comes back in the transaction response, with a refusal code, and you can react at once. With a direct debit, the charge goes out in a file, the bank attempts the debit on the value date, and if it is not honoured the notice comes back in a returns file with a standardised reason for the return.
For the system that means direct debit collection is not complete without a process that reads an inbound file and updates customer balances. Without it no debt is created and nobody knows the payment never arrived. How to build that is covered in reading the Masav returns file and updating customer debt.
The cost shape - and what actually matters in it
Masav publishes a public tariff, and its structure is composite: a per-transaction component, a per-file component, a per-return component, and one-off charges such as opening a new institution code. Card acquiring, by contrast, is priced mainly as a percentage of the transaction plus a fixed fee.
The implication is that the larger the average transaction, the wider the gap in favour of direct debit, because its cost is largely independent of the amount. On small, frequent payments the difference narrows, and other factors - onboarding drop-off, failure rate, and the cost of handling a failure - weigh more than the fee itself.
Why it is often worth running both
Many organisations do not choose one. They offer both and keep a fallback. The customer picks at signup; if one method fails repeatedly, you ask them to switch instead of losing the collection entirely.
In system terms that means the customer record holds a payment method as its own entity with a type, a status and a last-verified date - not a "card number" field that crowds out every alternative. The reconciliation work that follows from this is described in bank and card transaction reconciliation options.
How you move an existing customer between routes
Migrating customers between collection methods is a project in itself, because part of it depends on an action by the customer rather than by you. Moving from card to a bank mandate requires the customer to establish the mandate at their own bank, so completion rates are lower than they look on paper.
- Send each customer the institution code and the customer reference the mandate must be created with, not a generic request to "set up a standing order".
- Keep collecting on the old method until a successful charge is observed on the new one, not from the day the customer says they set it up.
- Run a defined overlap period and monitor it for duplicates - charging both the card and the mandate in the same month is the expected failure.
- Mark the old method inactive only after at least one successful charge on the new one.
In the opposite direction, mandate to card, the difficulty inverts: setup is fast, but the old mandate has to be cancelled or at least removed from the charges file, or the customer gets billed twice.
What to establish before deciding
- How long your bank takes to issue an institution code, and on what conditions.
- The drop-off you should expect converting existing customers to a bank mandate.
- Who on your side reads the returns file, and how often.
- Whether the amount is fixed in advance or varies each cycle.
- What happens when a customer cancels the mandate - how and when you would even find out.
Sources
Frequently asked questions
Who is identified as the collecting party on a direct debit?
The collecting organisation is identified to Masav by a unique institution code, obtained from the bank where the organisation's account is held, after approval. The customer establishes the mandate at their own bank using that institution code plus a customer reference you supply, so the debit is attributed correctly.
Can a customer cancel the mandate without telling us?
Yes. A direct debit authorisation is managed at the customer's own bank, and they can cancel it there. In practice you discover the cancellation when a charge comes back with the corresponding return reason, which is why routinely reading the returns file is the only way to know in time.
Does a customer changing bank cancel the mandate?
Not necessarily. Masav operates infrastructure enabling banks to handle the transfer of direct debit authorisations between banks in an automated way, including portability. It is still worth monitoring returns through such a transition, since it is a common source of a one-off collection failure.
Which is better for a small monthly subscription?
That is a business decision rather than a technical one. Card converts better at signup and reacts instantly to failure; a direct debit mandate is more stable over years and never expires. Many organisations offer both and move a customer between them when one method fails repeatedly.
Keep reading
Related service
MVP Development
Turn an idea into a validated product in weeks, not months.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build. I reply within 24 business hours with a few targeted questions, then we walk through it on a free 30-minute call, with no commitment. You come away with a scope, a timeline and a fixed price - or a straight answer that it isn't worth building.