Help Center

We help Amuta (Non-Profit Organization) connect payment system to accept donations.

Amuta is a non-profit organization that aims to promote socially significant goals or ideas in society.

Documents required to enable payments

1. Identity document (תעודת זהות) of the founder or director.
2. Certificate of registration of the amuta (תעודה לרישומה של עמותה).
3. Bank account details confirmation (אישור ניהול חשבון בנק).
4. Minutes specifying the authorized signatories (פרוטוקול מורשי חתימה). Must be notarized by a lawyer. Download a sample.
5. Certificate of proper management (אישור ניהול תקין) or a confirmation of document submission signed by an accountant (אישור הגשת מסמכים).

The Certificate of proper management confirms the legality and continuity of the amuta’s activity over a two-year period. The Confirmation of document submission serves as a temporary equivalent of the Certificate of proper management.

Registration steps

1. Make sure that the amuta site matches requirements.
2. Fill in registration form.
3. Within 24 hours, an Allpay manager will contact you to request missing documents.
4. If everything is in order, you will receive approval within 2-3 days and will be able to start accepting payments.

Technical capabilities

Allpay allows non-profit organizations to conveniently accept donations online. You can:

• create payment links, including links with an amount input field where the donor enters the donation amount;
• automatically create documents such as receipt (קבלה) and donation receipt (קבלה על תרומה) according to rules implemented in 2026;
• accept automatic monthly donations (subscriptions);
• embed a payment form on your website;
• accept donations via Bit, Google Pay and Apple Pay;
• and use other Allpay features.

A payout is a transfer of money from your received payments to your bank account, minus fees.

Payouts are made automatically once a month, on the 6th. The payout includes payments that were received in the previous month.

It usually takes up to three business days for the money to appear in your bank account.

The minimum payout amount is 100 ILS, USD, or EUR.

Installment payments are transferred once a month, as money is charged from the customer’s card.

Payment processing time

After a customer makes a payment, it is processed within 3–7 business days. Once processed, the payment is assigned a payout date — the 6th day of the following month.

For example, if a payment is processed on August 25, it will be paid out on September 6. If it is processed on September 2, the payout date will be October 6.

This means there may be cases when a payment is made at the end of one month but processed in the next. In such cases, the payout will be shifted by an additional month. For instance, a payment made on August 30 may be processed on September 2 and therefore will be paid out only on October 6.

You can check the payout date of each payment in its details by clicking the “Details” button.

Fees

If a payout is less than 5,000 ILS, the acquiring bank charges a fee of 14.9 ILS + VAT.

To avoid this fee, you can set payouts to happen only after the balance reaches 5,000 ILS.

Manual payouts

You can turn off the automatic payout on the 6th. In this case, the payout balance will grow each month, and the money will wait until you request it.

There are three payout options:

1. Automatic on the 6th. Each month on the 6th, all available funds in the balance are paid out automatically.
2. Automatic after reaching a set amount. The balance is topped up on the 6th of each month and will be paid out once it reaches the amount you choose. For example, if you set 5,000 ILS, you will not pay the small-payout fee.
3. Manual payouts. The balance is topped up on the 6th, but you decide when to request the payout.

Notifications

You can get payout notifications by e-mail or in Telegram. They can be set up in <span class="u-richtext-element">Settings</span> ➙ <span class="u-richtext-element">Notifications</span>.

Bank account for payouts

Payouts are sent only to the business bank account you gave during registration. You can check it in the settings.

To change the account, you need to provide a bank document with the details of the new account.

Refunds

If you made refunds to customers during the month, these amounts will be deducted from your next payout.

Breakdown and documents

On the 11th of each month, a record appears in the payout history with two documents:

1. A breakdown of all payments for the previous month with the fees shown.
2. A fee receipt, which can be used for accounting.

See also: “Where to download the payment system fee receipt”.

Weekly payouts

If you want to receive payouts more often than once a month, see the article: “Weekly payouts”.

To have the Bit payment button appear on your payment pages, activate the Bit module in the <span class="u-richtext-element">Settings</span> ➙ <span class="u-richtext-element">Modules</span> ➙ <span class="u-richtext-element">Bit</span> section.

Payment via Bit is only possible from a mobile device on which the Bit app is installed. When paying from a computer, the system will display a QR code for scanning and switching to payment from a mobile device.

Payments received through Bit are credited to the business's bank account along with the payout in the same way as other payments.

Bit button for foreign customers

Since Bit is an Israeli system, we make it possible to hide the Bit button for customers who pay from abroad. The system determines the client's geolocation by its IP.

The corresponding switch can be found in the module settings.

Restrictions

No payment from Bit balance. The charge is made from the card linked to Bit. If the card has insufficient available funds, the payment will fail. If no card is linked, Bit will display an “Add card” button instead of the payment button. If the customer does not add a card and abandons the payment, the transaction will return either a “Request declined by customer” or “Request expired” error.

Up to 5000 ILS. Payment via Bit cannot exceed 5,000 shekels. The sum of all payments per month from all customers cannot exceed 20,000 shekels.

ILS. Bit only supports payments in shekels.

No installments. You can only pay with Bit in one payment.

No subscriptions. Bit does not allow you to save your customer card for future charges, so we hide the Bit button for “Subscription” payment links.

Ten minutes. From the moment you press the Bit button, the customer has 10 minutes to make a payment.

Diners. Diners and Discover brand cards are not supported by Bit.

Name and email

Bit does not give us the payer's name and e-mail address, so we request them ourselves when making a payment.

The e-mail field is optional by default, and if it is not filled in by the customer, a payment confirmation will not be sent. You can make this field required in the Bit module settings.

Integrations

For payment integrations from ours catalogue The Bit button will be shown on the payment page if the module is activated and hidden if not.

API

Software integration developers documentation<span class="u-richtext-element">, can control the display of the Bit button on the payment page by using the show_bit parameter.</span> However, the Bit module must first be activated through your Allpay account.

For test payments, use the real card attached to the Bit app. At the same time, don't forget to activate the test mode for payment integration.

Platform developers that need a payment solution can integrate with Allpay.

This model is suitable for platforms that want to add Allpay as a payment method and be listed in the Allpay integrations catalog. It does not include partner payouts and is based on mutual promotion (other partnership models).

This integration will become available to Allpay customers as a ready-made way to connect your platform.

Requirements

To have your platform added to the Allpay integrations catalog, the following conditions must be met:

1. You do not participate in the Allpay partner or referral program.
   This integration is based on mutual promotion.
2. The integration must be approved by Allpay in advance.
   Your platform must be in demand in Israel and already used by real customers.
3. You are ready to support the integration on an ongoing basis.
   You are responsible for maintaining the integration and providing customer support on your side.

How to start

To approve the integration of your platform, contact Allpay support and briefly describe:

• your platform;
• who your customers are;
• how exactly you want to use Allpay payments;
• which integration method you plan to use: manual or automated;
• whether there are already customers who need this integration.

Integration methods

Integration with Allpay can be implemented in two ways:

• manual integration;
• automated integration.

Manual integration

With manual integration, you implement the connection on your side and publish instructions for customers on your website.

The customer will need to:

1. Open the integrations section in the Allpay dashboard.
2. Create API keys.
3. Copy the keys and paste them into the settings of your platform.

Technical involvement from Allpay is usually not required for this type of integration. After implementation, send us information about your platform and a link to the Allpay connection instructions on your website.

After review and approval, your platform will be added to the Allpay integrations catalog.

Automated integration

Automated integration allows the platform to be connected without manually copying API keys. The user clicks the connection button in the Allpay dashboard, confirms the connection on your platform side, and the API keys are transferred automatically.

Before implementation, Allpay provides your platform with:

<span class="u-richtext-element">partner_id</span> — the individual integration ID;

<span class="u-richtext-element">secret_key</span> — the secret key for signing and verifying server requests.

<span class="u-richtext-counter">1</span>Redirect from Allpay to your platform page

The user opens the <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Integrations</span> → <span class="u-richtext-element">Your platform</span> section in the Allpay dashboard and clicks the connection button.

Allpay generates a one-time token for linking the accounts and redirects the user to the confirmation page on your platform side, for example:

https://your-platform.com/connect?token=TOKEN

Where <span class="u-richtext-element">TOKEN</span> is the one-time token created by Allpay.

The standard token lifetime is 1 hour.

<span class="u-richtext-counter">2</span>Confirmation on your platform side

On your side, the user confirms the connection under their account.

After confirmation, your platform redirects the user back to the universal Allpay endpoint:

https://allpay.to/services/endpoints/exchange.php?act=connect&partner_id=PARTNER_ID&token=TOKEN&external_uid=USER_ID&display_name=DISPLAY_NAME

Where:

<span class="u-richtext-element">act=connect</span> — the integration connection action;

<span class="u-richtext-element">partner_id</span> — the individual integration ID;

<span class="u-richtext-element">token</span> — the one-time token created by Allpay;

<span class="u-richtext-element">external_uid</span> — the internal user ID on your platform.

<span class="u-richtext-element">display_name</span> — a human-readable name of the account being connected (e.g. login, name or subdomain on your platform). This is the value shown in the Allpay dashboard's integrations list — pass something the user will recognize themselves, not an internal technical identifier. The value must be URL-encoded, max 255 characters.

<span class="u-richtext-counter">3</span>Creating and sending API keys to your platform

After verifying the token, Allpay links the Allpay user with the user on your platform, creates or finds the API keys <span class="u-richtext-element">api_login</span> and <span class="u-richtext-element">api_key</span>, and then sends them to your endpoint.

Example endpoint on your platform side:

POST https://your-platform.com/allpay/partner/exchange

Request body:

{
  "external_uid": "USER_ID",
  "api_login": "API_LOGIN",
  "api_key": "API_KEY",
  "sign": "SIGNATURE"
}

Where:

<span class="u-richtext-element">external_uid</span> — the user ID on your platform;

<span class="u-richtext-element">api_login</span> — the Allpay user's API login;

<span class="u-richtext-element">api_key</span> — the Allpay user's API key;

<span class="u-richtext-element">sign</span> — the request signature.

<span class="u-richtext-counter">4</span>Request signature

The server request with the API keys is signed using HMAC SHA-256.

Signature format:

hash_hmac('sha256', $payload_json, $secret_key);

Where:

<span class="u-richtext-element">payload_json</span> — the JSON request body;

<span class="u-richtext-element">secret_key</span> — the individual secret key.

<span class="u-richtext-counter">5</span>Response from your platform

After successfully receiving and saving the keys, your platform must return a successful response, for example:

{
  "ok": true
}

After this, Allpay marks the integration as active.

Disconnecting the integration

If the user disconnects the integration on your platform side, you must delete the saved API keys on your side.

In addition, your platform must send a POST request to Allpay to disconnect the integration:

POST https://allpay.to/services/endpoints/exchange.php?act=disconnect&partner_id=PARTNER_ID

Request body:

{
  "external_uid": "USER_ID",
  "sign": "SIGNATURE"
}

Where:

<span class="u-richtext-element">external_uid</span> — the user ID on your platform;

<span class="u-richtext-element">sign</span> — the request signature.

The disconnect request is also signed using <span class="u-richtext-element">secret_key</span>.

If the user disconnects the integration from the Allpay dashboard, Allpay can send a disconnect notification to your platform endpoint. To receive this notification, provide an endpoint on your side.

Connecting via a link from your dashboard

You can start the connection on your side instead of from the Allpay dashboard. You generate a signed link and show it to the user (a button in your dashboard):

https://allpay.to/services/endpoints/exchange.php?partner_id=<your id>&show=start&external_uid=<…>&state=<…>&display_name=<…>&expires=<unix>&return_url=<…>&sign=<…>

The user confirms the connection in Allpay, Allpay sends the keys to your <span class="u-richtext-element">keys_url</span>, and then the user is returned to your <span class="u-richtext-element">return_url</span>.

Link parameters

<span class="u-richtext-element">partner_id</span> — your partner ID;

<span class="u-richtext-element">show</span> — always <span class="u-richtext-element">start</span>, not included in the signature;

<span class="u-richtext-element">external_uid</span> — the ID of what is being connected on your platform (for example, the branch ID), up to 255 characters. A link with a longer value is rejected;

<span class="u-richtext-element">state</span> — any value you generate for this link, up to 500 characters (a longer value is truncated). Store it on your side together with the user who requested the link and the <span class="u-richtext-element">external_uid</span>. We return it in the request to <span class="u-richtext-element">keys_url</span> and in the redirect to <span class="u-richtext-element">return_url</span>;

<span class="u-richtext-element">display_name</span> — what is being connected (for example, the branch name), up to 255 characters. Optional, but we recommend passing it: it is shown to the user on the Allpay confirmation screen and in the Allpay dashboard;

<span class="u-richtext-element">expires</span> — Unix time until which the link is valid. No later than 30 days from now; a link with a later date is rejected;

<span class="u-richtext-element">return_url</span> — required; the address to send the user back to after a successful connection. <span class="u-richtext-element">https</span> only, and the host must match the host of your <span class="u-richtext-element">connect_url</span> exactly (subdomains do not match). A link without a valid <span class="u-richtext-element">return_url</span> is rejected;

<span class="u-richtext-element">sign</span> — the link signature. Calculated with the same rules as for API requests. All parameters except <span class="u-richtext-element">show</span> and <span class="u-richtext-element">sign</span> are signed.

What happens next

1. The user opens the link and signs in to Allpay, if not signed in yet.

2. On the Allpay screen, the user sees which Allpay company is being connected and what exactly (<span class="u-richtext-element">display_name</span>), and clicks "Connect".

3. Allpay sends the keys to your <span class="u-richtext-element">keys_url</span> as a JSON POST request. The <span class="u-richtext-element">X-Allpay-Signature</span> header contains the HMAC-SHA256 of the raw request body, signed with your <span class="u-richtext-element">partner_secret</span>. Request body fields:

<span class="u-richtext-element">external_uid</span> — from the link;

<span class="u-richtext-element">state</span> — from the link (if you passed it);

<span class="u-richtext-element">api_login</span>, <span class="u-richtext-element">api_key</span> — the API keys;

<span class="u-richtext-element">token</span> — an internal value, you can ignore it.

Your server must respond with exactly HTTP 200.

4. The user is returned to <span class="u-richtext-element">return_url</span> with <span class="u-richtext-element">state</span> added (if you passed it): <span class="u-richtext-element">return_url?state=<state></span>, or <span class="u-richtext-element">&state=<state></span> if <span class="u-richtext-element">return_url</span> already has a query string.

If your <span class="u-richtext-element">keys_url</span> does not respond with HTTP 200, the connection is not made, the user sees an error in Allpay, and the same link can be opened again.

Verify the user on your side

The link is not tied to a specific Allpay company: whoever opens it and signs in to Allpay can confirm it. The keys arrive at your <span class="u-richtext-element">keys_url</span> before the user returns to you, so do not activate them right away:

• when the keys arrive, find the link by <span class="u-richtext-element">state</span> and check that <span class="u-richtext-element">external_uid</span> matches;
• on <span class="u-richtext-element">return_url</span>, require the user to be signed in to your dashboard. If they are not, send them to sign in and then back;
• check that this <span class="u-richtext-element">state</span> was issued to the user who is now signed in, that it has not expired, and that this user has rights to that <span class="u-richtext-element">external_uid</span>. If all checks pass, activate the keys and mark the <span class="u-richtext-element">state</span> as used.

This check does not protect against your own user connecting the wrong Allpay company, for example by signing in under a different company. If this matters to you, show your user which connection was made before activating the keys.

Important

The link is single-use. After a successful connection through it, opening it again is rejected, even after a disconnect. Generate a new link, with a new <span class="u-richtext-element">state</span>, for each connection attempt: links with completely identical parameters (including <span class="u-richtext-element">expires</span>) are treated by Allpay as the same link.

An existing connection is never replaced. The connection is rejected if:

• the Allpay company already has a connection to your platform, including a paused one;
• this <span class="u-richtext-element">external_uid</span> is already connected to any Allpay company.

To connect something else, first disconnect the current connection: in the Allpay dashboard, or with <span class="u-richtext-element">act=disconnect</span> from your side. A paused connection cannot be disconnected with <span class="u-richtext-element">act=disconnect</span>, only in the Allpay dashboard.

Open and confirm the link in the same browser. A new link from your platform opened in the same session replaces the previous one.

Security requirements

For automated integration, the following requirements must be met:

1. HTTPS only
   All requests between Allpay and your platform must be sent only over HTTPS.
2. Secure key storage
   The received <span class="u-richtext-element">api_login</span> and <span class="u-richtext-element">api_key</span> must be stored securely on your side.
3. Server request signatures
   Server requests must be signed using <span class="u-richtext-element">secret_key</span>.

<span id="info">Information for the integrations catalog</span>

After the technical part is completed and the integration is working, send us the following information to add your platform to the Allpay integrations catalog:

• platform logo in SVG format;
• short platform description of up to 200 characters;
• extended platform description of up to 360 characters;
• technical support contacts for the integration: email and WhatsApp or Telegram;
• information on whether your integration supports installments, recurring payments, and refunds;
• link to the Allpay connection instructions on your website.

Allpay branding guidelines

Use the correct brand spelling:

correct: Allpay;

incorrect: AllPay, All Pay, allpay.

Use the official Allpay logo.

A J5 transaction is a two-step payment process that begins with a pre-authorization. In the first step, the specified amount is reserved (held) on the buyer’s card for up to 168 hours (7 days) without actually charging the card.

To charge the reserved funds, the seller must initiate a charge request within that time frame and within the reserved amount. If the charge is for a smaller amount, the remaining balance is automatically released.

The term “J5” is used in Israeli payment systems as an internal code to refer to this type of transaction.

Use Cases

Delivery orders – The amount is reserved when the order is placed and charged after delivery is confirmed.

Variable price orders – For example, when buying products sold by weight (meat, fruits, vegetables), the final price is determined after weighing.

‍Pay as you go – The customer uses a service within a limit, and the final amount is calculated at the end.

Car rentals & hotels – The amount is reserved to cover possible damages or extra expenses.

Custom-made products – When ordering custom furniture or jewelry, the amount is reserved at checkout and charged when the product is ready.

Limitations

The charged amount cannot exceed the reserved amount.

Charging is allowed only once. Any attempt to charge again or after 168 hours will result in an error.

Supported Payment Methods

Both Israeli and international credit and debit cards are supported.

Quick payment methods (Apple Pay, Google Pay, Bit) are not supported for J5. These buttons will be hidden on the authorization page.

Important to know

An authorization may look like an actual payment to the customer: some card issuers send an SMS in the same format as they do when a card is charged. However, in the card issuer’s online account, the transaction is usually marked as “Amount not final” or something similar.

If you subsequently charge less than the authorized amount, the remainder is released automatically. However, the card issuer may need a from few hours to few days to update the transaction details and make the unused amount available to the customer again.

How to Use

J5 functionality is available to developers via the Allpay API: view API documentation.

Demo

Allpay lets you display the price in one currency that is convenient for the customer, while charging in another currency.

For example, for customers in Canada you can display the price in CAD, while charging in ILS, so the funds are paid out to the merchant bank account without additional conversion.

In this scenario, the customer will see the amount in two currencies on the payment page, for example: <span class="u-richtext-element">100 CAD (226 ILS)</span> The actual charge will be made in Israeli shekels (ILS).

This format helps to:

• show the customer the price in a currency they understand;
• clearly explain which currency will be charged;
• reduce confusion when the customer later sees the charge in their bank statement.

Exchange rates are taken from Google Finance at the moment the payment page is opened.

Payment currency

Payment currency (optional parameter <span class="u-richtext-element">currency_payment</span>) is the currency in which the actual charge is made and the funds are paid out to the merchant bank account.

The customer’s card currency does not matter — after the charge, the customer’s bank will convert the amount using its own exchange rate if the card is denominated in another currency.

By default, after registering in Allpay only ILS payment currency is available. You can enable USD and EUR according to this instruction.

Supported payment currencies

Euro — EUR

Israeli new shekel — ILS

United States dollar — USD

Display currency

Display currency (required parameter <span class="u-richtext-element">currency_display</span>) is the currency shown to the customer on the payment page.

Always send this parameter, even if display currency is same as payment currency.

• the item cost provided in <span class="u-richtext-element">price</span> must be sent in the display currency;
• Allpay automatically converts the amount from <span class="u-richtext-element">currency_display</span> to <span class="u-richtext-element">currency_payment</span> using current Google Finance exchange rate;
• the customer is always charged in the payment currency (<span class="u-richtext-element">currency_payment</span>). If not porovided, ILS used as default.
• If the display currency and the payment currency are different, the webhook includes the <span class="u-richtext-element">currency_course</span> parameter with the conversion rate that was applied.

For example, for Europe customer you can display the price in EUR and charge in ILS. Or for customer from Canada display the price in CAD and charge in USD.

Supported display currencies

Australian dollar — AUD

Azerbaijani manat — AZN

Canadian dollar — CAD

Chinese Yuan — CNY

Euro — EUR

Georgian lari — GEL

Japanese yen — JPY

Israeli new shekel — ILS

Kazakhstani tenge — KZT

Norwegian krone — NOK

Pound sterling — GBP

Russian ruble — RUB

Thai baht — THB

Ugandan shilling — UGX

United Arab Emirates dirham — AED

United States dollar — USD

Ukrainian hryvnia — UAH

If the currency you need is not in the list, please contact support.

Examples of using <span class="u-richtext-element">currency_display</span> in API requests

Always send <span class="u-richtext-element">currency_display</span> even if it is matches <span class="u-richtext-element">currency_payment</span>.

Example 1

{  
  "items": [
    {
      "name": "Product name",
      "price": "100",
      "qty": "1",
      "vat": "0"
    }
  ],
  "currency_payment": "USD",
  "currency_display": "CAD"
  }

Allpay will convert 100 CAD to USD and the customer will be charged in USD.

At the time this article was written: 100 CAD = 72 USD, so the charge will be 72 USD.

If the account is not approved for USD, the system will automatically convert the amount to ILS (the default currency).

Example 2

{  
  "items": [
    {
      "name": "Product name",
      "price": "100",
      "qty": "1",
      "vat": "0"
    }
  ],  
  "currency_display": "CAD"
  }

Because <span class="u-richtext-element">currency_payment</span> is not provided, 100 CAD will be converted to ILS (the default currency), and the customer will be charged in ILS.

Example 3

{  
  "items": [
    {
      "name": "Product name",
      "price": "100",
      "qty": "1",
      "vat": "0"
    }
  ],  
  "currency_payment": "CAD"
  }

API will return error since <span class="u-richtext-element">currency_display</span> was not provided.

To test different currency combinations, use the Allpay API tester.

In <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Team</span> you can add employees as users of your Allpay account.

Access permissions

The <span class="u-richtext-element">Team</span> section is available only to the business owner. Only the owner can add users, edit their details and manage access.

Users you add have access to all other sections of the account. They cannot add other users or edit their details. Custom access permissions are not currently available.

Adding a user

1. Open <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Team</span> and click the plus button.
2. Enter the user’s full name and position on the team.
3. Add at least one contact for signing in: an email address, phone number or Telegram.

You can add multiple contacts, including several of the same type, such as multiple email addresses. The same contact cannot be linked to different users.

Verifying contacts

Each contact you add must be verified within 48 hours. To do this, the user must sign in to Allpay using that contact.

Allpay does not send automatic invitations, so let the employee know that they have been given access. You can copy the sign-in link from the user’s profile.

If the user does not verify the contact within this time, the business owner can extend the deadline by another 48 hours by clicking the corresponding button.

Updating details

The business owner can edit a user’s details by clicking “Edit” on the user’s card.

The business owner’s details and contacts can only be updated if the owner personally contacts Allpay Support.

Disabling a user

A user can sign in to the account while the “Account active” toggle on their card is enabled.

If you turn it off, the user will lose access to the account and be automatically signed out. If they previously connected the account to an AI assistant through MCP, that access will also be revoked.

The business owner cannot be disabled.

Activity history

You can view all users’ activity in the “Activity log” tab.

Access to multiple companies

If the same user contact is listed for several companies, the user can switch between them in the settings menu or the “Profile” section.

Contacting support

When contacting Allpay Support about your account, use a contact listed under your name in the “Team” section.

If a request comes from a contact that is not listed for the business owner or an employee in the “Team” section, Allpay Support may decline to disclose sensitive account information.

When creating a payment link, you can enable installment payments and set the maximum number of installments — up to 12. The customer can choose how many installments to split the total into, within the limit you set.

If the customer chooses two or more installments, their card will be charged and you will receive the funds in monthly installments until the full amount is paid.

There is no additional installment fee for either the business or the customer. If you want to receive the full amount upfront, you can activate the “Installments upfront” service, which carries an additional fee.

Installment payments are available only with credit cards issued in Israel.

<span class="u-richtext-counter">1</span> Create a payment link

When creating the link, open the <span class="u-richtext-label">More</span> section, select <span class="u-richtext-element">Installments</span> as the payment type, and specify the maximum number of payments the customer will be able to choose.

<span class="u-richtext-counter">2</span> Send the link to the customer

On the payment page, the customer will see an option to choose the number of payments. If they leave it as one payment, the full amount will be charged immediately.

Example

For a service costing 6,000₪, you enabled up to 5 installments. The customer chose to pay in 3 installments. At the time of payment, 2,000₪ will be charged, another 2,000₪ a month later, and the final 2,000₪ in the third month.

A receipt for installment payments is generated for the full amount immediately. The payment schedule is shown in the receipt.

If the installment payment fails

The most likely reasons are:

1. The customer’s card is not a credit card but a debit card;
2. The card was not issued by an Israeli bank;
3. The card’s credit limit (misgeret) is lower than the total payment amount.

Why installments are not available for foreign cards

Installment payments work only with Israeli credit cards within their credit limit. Since the system cannot manage credit limits of foreign banks, payment splitting on such cards is not supported.

This is a limitation of the financial system. In essence, installments are a form of credit. If the customer doesn’t have sufficient funds in their account, you (the business) still receive the next payment because the bank provides credit to the customer. Managing credit limits and collecting debts in case of nonpayment can only be guaranteed within the country.

If the customer cancels the card

You will continue receiving installment payments even if the customer closes or cancels the credit card that was used for the payment.