Help Center

Found 100 out of 200

Accepting payments in USD and EUR

In addition to shekels, Allpay supports payments in US dollars (USD) and euros (EUR).

Available payment currencies are shown in the <span class="u-richtext-element">Settings</span> ➙ <span class="u-richtext-element">Permissions</span> section.

By default, only payments in shekels are enabled after registration. To accept payments in USD or EUR, a separate permission must be requested.

Before requesting permission to accept payments in foreign currencies

In many cases, accepting payments in shekels is sufficient for a business. However, if your customers are located in Europe, the US, or other countries, it may be more convenient for them to view prices in USD or EUR.

For this purpose, we offer a special feature — currency display conversion. This means the customer will see the payment amount in, for example, euros, but the actual charge will be made in shekels based on their bank’s exchange rate.

No permission is required to use this feature — it is already available.
‍

More details: How to display the payment amount in USD or EUR.

We recommend using this solution in most cases.

Requesting permission to accept payments in foreign currencies

Go to <span class="u-richtext-element">Settings</span> ➙ <span class="u-richtext-element">Modules</span> and activate the “USD & EUR” module.

To activate it, you’ll need to upload a bank letter with the details of your foreign currency account. The letter must:

  • Include the account number in IBAN format
  • Include your name (or company name) and Teudat Zehut number (or company number)

Examples of bank letters:‍ Discount, Leumi, Hapoalim.

The confirmation letter can be downloaded from your bank's online account or obtained by visiting the bank in person. Letters that do not meet the above requirements will not be accepted.

The letter will be forwarded to the relevant credit company (Isracard or CAL — depending on how your business is connected to the Allpay system) with a request to approve foreign currency operations for your account.

The average approval time is 2–4 business days.

Allpay cannot guarantee approval for foreign currency transactions; however, we do everything possible to ensure that all our customers receive the necessary authorization.

When a business website has an English version and clearly displays products or services with prices in USD or EUR, it increases the likelihood of approval.

Once the approval is granted, the module status will change to “Active” and you will receive a notification. Please make sure notifications are enabled under <span class="u-richtext-element">Settings</span> ➙ <span class="u-richtext-element">Notifications</span>.

How to accept payments in foreign currency

When creating a payment link, you will see an option to switch the payment currency.

Payment link in USD

When creating payments via API, you can pass the values "USD" or "EUR" in the <span class="u-richtext-element">currency</span> parameter.

Commission and withdrawals

We do not charge any additional commission for foreign currency payments — standard rates apply.

However, your bank may charge a fee for receiving currency withdrawals. These withdrawals are made via the SWIFT system and go through a chain of three banks: our bank, your bank’s foreign branch, and your bank in Israel. The total fee per withdrawal can reach up to $40. We cannot influence this fee, but you can ask your bank for better terms.

For this reason, withdrawals are made starting from 100 USD/EUR. Any amount below 100 USD/EUR will be carried over to the next withdrawal.

Receipts

According to the law, official receipts (kabalot and heshbonit mas) must be issued in shekels.

Therefore, for foreign currency payments, the service price in the receipt appears in the payment currency, while the VAT amount and total are shown in shekels based on the current exchange rate. We use exchange rates from Google Finance.

If your customer needs a receipt showing the total amount in the original payment currency (not in shekels), a copy can be downloaded from the EasyCount or Morning dashboard.

Keep reading
Profile
Payment links
Documents

Hosted Fields: how to embed payment form on a website

Hosted Fields allow you to embed card input fields on your website or app, fully adapting them to the system's design. They create a seamless interface experience and eliminate the need to redirect the customer to an external payment page. This improves usability and conversion rates.

The input fields for the card number, expiration date, and CVC are represented as an iFrame. We provide the ability to fully customize their CSS and embed them on your site as a single frame.

Tutorial

Setup

<span class="u-richtext-counter">1</span> In the <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Integrations</span> → <span class="u-richtext-element">My sites</span> enable Hosted Fields for the required integration.

<span class="u-richtext-counter" id="domains">2</span> Click <span class="u-richtext-element">Hosted Fields settings</span> and specify the domains where Hosted Fields will be used. Enter each domain or subdomain on a separate line without “https://”, for example: <span class="u-richtext-element">mysite.com</span>. To allow all subdomains, use the <span class="u-richtext-element">*</span> wildcard, for example: <span class="u-richtext-element">*.mysite.com</span>.

If needed, adjust the CSS styles for the input fields.

<span class="u-richtext-counter">3</span> On your website’s payment page, place an iFrame, assign any custom value to its <span class="u-richtext-element">id</span> parameter, and in the <span class="u-richtext-element">src</span> parameter specify the payment URL (payment_url) returned by Allpay in response to a payment creation request (see Payment request section in the API Reference). Payment URLs can also be generated using the Allpay API Tester.‍

<span class="u-richtext-counter">4</span> Add the following script to the payment page:

1<script src="https://allpay.to/js/allpay-hf.js"></script>
2    <script>
3    let Allpay = new AllpayPayment(
4        {
5            iframeId: 'iframe_id',
6            onSuccess: function() { alert('Payment success'); },
7            onError: function(error_n, error_msg) { alert('Payment error: ' + error_n + ' (' + error_msg + ')'); }
8        }
9    );
10    </script>

‍

In the script, replace the following parameters with your own:

  • <span class="u-richtext-element">iframeId</span> — the id value of your iFrame.
  • <span class="u-richtext-element">onSuccess</span> — the handler for successful payment completion (what should happen after successful payment).
  • <span class="u-richtext-element">onError</span> — the handler for payment errors. For example, you can display the payment error message on the page.

<span class="u-richtext-counter">5</span> To initiate the process, execute the function <span class="u-richtext-element">Allpay.pay()</span>, for example, by assigning it to the "Pay" button:

<button onclick="Allpay.pay();">Pay</button>

Installments

If you enabled the installment option for the customer when creating the payment by passing a value in the <span class="u-richtext-element">inst</span> parameter, a field for selecting the number of payments will automatically appear in the frame.

Quick Pay Buttons

Apple Pay and Bit buttons will not be displayed in preview mode or within the iFrame if they are not activated in the <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Modules</span>.

Additionally, these buttons are not displayed in test mode. As well as in live mode for installment or subscription payments.

Apple Pay button

For the Apple Pay button to work correctly, complete the following two steps:

<span class="u-richtext-counter">1</span>Add the <span class="u-richtext-element">allow="payment *"</span> attribute to the <span class="u-richtext-element">iframe</span> tag. Example:

<iframe id="myPaymentIframe" allow="payment *" src="..." >

<span class="u-richtext-counter">2</span>Upload the Apple Pay certificate to your domain’s server. The certificate and installation instructions are available in the Hosted Fields settings in your Allpay account.

<span id=google-pay>Google Pay button</span>

For the Google Pay button to work on your domain, the domain must be verified by Google, after which your Google Merchant ID must be added to the payment system.

<span class="u-richtext-counter">1</span>Create a profile in the Google Pay & Wallet Console.

<span class="u-richtext-counter">2</span>In Google Pay API → Web integration, enter your domain and select Gateway as the integration type.

<span class="u-richtext-counter">3</span>Upload screenshots of the buyflow from your website. After activating Google Pay in Allpay’s payment modules, the Google Pay button will appear but will not work yet. This will allow you to take screenshots of the Item selection, Pre-purchase screen, and Payment method screen.

For the Google Pay API payment screen, upload a screenshot of the error that appears when you click the button. For the Post-purchase screen, upload a screenshot of your successful payment page, even if it does not mention Google Pay.

<span class="u-richtext-counter">4</span>Submit your application and wait for Google’s approval. The review may take several business days.

<span class="u-richtext-counter">5</span>Copy your Google Merchant ID and enter it in the Hosted Fields settings in your Allpay account. It may take several days for the ID to be configured in the payment system, after which Google Pay payments will start working.

Your website may not pass Google’s review if it does not comply with the Google Pay and Wallet API's Acceptable Use Policy or the Google’s Terms of Service.

If you represent a nonprofit organization (amuta) follow Google’s instructions.

Embedding in a mobile app (WebView)

If you embed the payment page in a mobile app using a WebView (android.webkit.WebView or WKWebView), some payment methods may not work correctly. For example, Bit or 3D Secure verification may redirect the user to a payment or banking app using special links such as <span class="u-richtext-element">intent://</span>

Unlike a standard browser, WebView does not always handle these redirects automatically. As a result, the external app may not open, preventing the user from completing the payment.

We recommend opening the payment page using a system browser component:

  • Chrome Custom Tabs on Android;
  • SFSafariViewController on iOS.

These components behave similarly to a standard mobile browser and provide better support for redirects to payment and banking apps.

If you need to use WebView, handle navigation within the mobile app:

  • open regular <span class="u-richtext-element">http://</span> and <span class="u-richtext-element">https://</span> links inside the WebView;
  • pass links that use other schemes to the operating system so it can open the appropriate app;
  • if the required app is not installed, use the provided fallback link to open the browser, App Store, or Google Play.

This limitation is related to how WebView handles external links, not to Hosted Fields itself.

Keep reading
API

Google Pay

The Google Pay button allows Android users to make quick payments from both mobile devices and computers.

To display the button on the payment page, activate the Google Pay module under <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Payment modules</span> → <span class="u-richtext-element">Google Pay</span>.

Exceptions

Since Google Pay does not allow card details to be saved for future charges, the button will be hidden:

  • on payment pages offering installments if the customer selects more than one payment;
  • on subscription payment pages.

Israeli ID Number

Google Pay does not provide the customer’s Israeli ID number, so it will not appear on the payment document. Asking customers to enter their Israeli ID number before clicking the Google Pay button defeats the purpose of quick payment. If collecting this number is mandatory, it is better not to use Google Pay.

Developers

If Google Pay is enabled in the payment module settings, the button will be displayed by default on payment pages created via the API. To hide the button, use the <span class="u-richtext-element">show_googlepay</span> parameter as described in the documentation.

If you use Hosted Fields to display the payment form directly on your website without redirecting the customer, your domain must be verified by Google before the Google Pay button can be used. Learn more in the Hosted Fields article.

The Google Pay button is not available in test mode.

Keep reading
Payment methods

Apple Pay

The Apple Pay button allows customers to pay quickly using an iPhone, Mac, or another Apple device.

To display the button on the payment page, activate the module under <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Payment modules</span> → <span class="u-richtext-element">Apple Pay</span>.

The button is displayed only when the payment page is opened on an Apple device with a payment method added.

Exceptions

Since Apple Pay does not allow card details to be saved for future charges, the button will be hidden:

  • on payment pages offering installments if the customer selects more than one payment;
  • on subscription payment pages.

Israeli ID number

Apple Pay does not provide the customer’s Israeli ID number, so it will not appear on the payment document. Asking customers to enter their Israeli ID number before clicking the Apple Pay button defeats the purpose of quick payment. If collecting this number is mandatory, it is better not to use Apple Pay.

Unsuccessful payments under the name “Applepay Payer”

Apple Pay provides us with the customer’s name only after a successful payment.

Clicking the Apple Pay button initiates the payment process and creates a transaction under the name “Applepay Payer” with the status “Unpaid.” The customer then confirms the payment on their device. Apple Pay processes the payment and returns the customer’s name, which we display instead of “Applepay Payer,” while the transaction status changes to “Paid successfully.”

However, if the payment is not confirmed on the device or is declined by Apple Pay, the customer’s name will remain “Applepay Payer,” and we will not receive the reason for the decline. If the customer proceeds to payment from your website and entered their name during checkout, we will display that name instead of “Applepay Payer.”

Developers

If Apple Pay is enabled in the payment module settings, the button will be displayed by default on payment pages created via the API. To hide the button, use the <span class="u-richtext-element">show_applepay</span> parameter as described in the documentation.

The Apple Pay button is not available in test mode.

If you use Hosted Fields to display the payment form directly on your website without redirecting the customer, you will need to place an Apple certificate on your server before the Apple Pay button can be used. Learn more in the Hosted Fields article.

Keep reading
Payment methods
Payment links

Weekly payouts

Weekly (accelerated) payouts let you receive money more often than with the standard once-a-month schedule.

How it works

After a customer makes a payment, it is processed within 3–7 business days. Immediately after processing, the payment is added to your payout balance and becomes available for transfer to your bank account.

Every Monday, an automatic payout of available funds is executed. As a rule, the money appears in your bank account within three business days.

If needed, you can request a payout manually without waiting for Monday.

Examples

  • A payment made on Sunday and processed on Thursday will be included in the payout on the nearest Monday.
  • A payment made on Friday and processed on Tuesday will skip the Monday that fell within the processing period and will be paid the next Monday, unless you request the payout earlier manually.

Requirements

Before enabling the module, three conditions must be met:

  1. Business owner must be at least 21 years old.
  2. Using Allpay for at least three months.
  3. Total turnover of at least 15,000 ILS during that time.

These criteria help assess your business’s payment activity and reduce chargeback risks — situations where a business receives a large payout and the cardholder reports an unauthorized charge.

The module applies only to payments received after it is activated (it is not retroactive).

Activation

The module is enabled in <span class="u-richtext-element">Settings</span> ➙ <span class="u-richtext-element">Payment modules</span> ➙ <span class="u-richtext-element">Weekly payouts</span>

After you request activation, we will send documents for signature. Once the acquiring institution approves them, the module will be turned on. The review usually takes 5–7 business days.

After approval, payouts will automatically switch from monthly to weekly.

Deactivation

You can deactivate the module in the same section. Deactivation takes 5-7 business days. After that you will receive e-mail notification.

Reactivation is only possible after 30 days.

Fees

Since weekly payouts are considered accelerated, the credit company charges an additional fee on each payment. The fee amount and the calculation method are shown on the pricing page.

The fee is charged even if you temporarily use the manual payout mode, because the accelerated processing has already been completed and the payment is available for payout.

To stop paying the additional fee and return to the standard monthly schedule, disable the weekly payouts module. The new terms apply only to payments made after the module is disabled.

Notifications and documents

Payout notifications are sent by e-mail and in Telegram if these options are enabled in <span class="u-richtext-element">Settings</span> ➙ <span class="u-richtext-element">Notifications.</span>

On the 11th day of each month, the payout history shows a monthly payment breakdown and a fee receipt, which can be used for accounting.

Keep reading
Payouts

Chargeback (transaction dispute)

Chargeback comes from the English words «charge» (debit) and «back» (return), which literally means «return of funds back». This term refers to the procedure by which a bank refunds money to the payer after funds were mistakenly or fraudulently withdrawn from their account.

It is a consumer protection mechanism that allows the cancellation of credit or debit transactions and the return of funds if the customer did not authorize the purchase, did not receive the goods or services, or if billing errors occurred.

Participants in a chargeback

The chargeback process involves:

  • Customer: Initiates the chargeback through the issuing bank (the bank that issued the card).
  • Issuing bank: Conducts the investigation and, if necessary, refunds the money to the customer. In Israel, the issuing banks can be Isracard, CAL, MAX and few others.
  • Merchant (seller): Must provide evidence of the legitimacy of the transaction. If the chargeback is justified, the merchant refunds the money to the bank.

Possible reasons for a chargeback

  • The customer requested a refund because they did not recognize a charge in the bank statement or forgot about an actual payment.
  • The goods or services were not provided by the merchant.
  • Fraudulent charges were made on the card without the customer’s knowledge (the card was stolen or compromised).

Chargeback procedure

After the customer files a request, the issuing bank opens a case, determines the reason for the chargeback, and decides whether to return the money to the customer or leave it with the merchant. As part of the investigation, the bank will contact the merchant and request proof of service delivery.

In Israel, according to the Payment Services Law of 2020, if a transaction is considered an «insufficient documentation transaction» (i.e., made without the physical presence of the card, which applies to all online payments), the customer receives a full refund if they contact the issuing bank within 30 days of receiving the charge notification.

Thus, the law provides significant protection for the consumer but can also lead to fraud and cancellations of legitimate transactions where the customer actually received the agreed service. Therefore, merchants are advised to collect and keep evidence of goods or services provided to the customer, especially for large amounts (e.g., contracts, receipts, emails, delivery confirmations).

If the bank establishes that the funds were withdrawn from the customer’s card illegally, they will be returned to the customer and deducted from the merchant’s balance.

Risks for merchants

Frequent chargebacks can have serious consequences for merchants. The main risk is financial loss due to refunds to customers. However, that is not the only risk:

  • Fines and fees: Banks may impose fines for each chargeback, increasing financial pressure on the business.
  • Deterioration of banking relationships: Frequent chargebacks can damage relationships with acquiring banks. This can lead to higher fees, worse cooperation terms, or even termination of the contract.
  • Risk of being blacklisted: A high chargeback rate can result in being added to blacklists of payment systems, making it difficult to work with new acquirers and other financial institutions.
  • Loss of reputation: Frequent chargebacks can damage the merchant’s reputation, creating distrust among customers and partners.

Tips for prevention

To minimize chargeback risks, merchants should take the following measures:

  • Use secure payment methods: Activate 3DS for payments — a two-factor authentication method where the bank asks the customer to confirm the payment via the banking app or by entering an SMS code.
  • Improve communication with customers: Quick and transparent communication helps avoid misunderstandings. It is important to respond to customer inquiries promptly and provide full information about goods and services.
  • Collect and store evidence: Systematically keep all documents confirming the provision of services or delivery of goods. This will help protect the business in case of a chargeback.
  • Clear refund policy: A transparent and easy-to-understand return policy can reduce the number of chargebacks, as customers will know how to return a product or cancel a service.

Fee

A fee is charged by the credit card company for reviewing each chargeback case, in accordance with the pricing.

Display in the interface and documents

If a chargeback was requested for a payment, a new transaction with a negative amount and the label <span class="u-richtext-element" style="background-color: rgba(221, 94, 94, 0.4)">chargeback</span> will appear on the payments screen.

A refund document will also be created: a credit invoice and/or a receipt with a negative amount — depending on the business type and the type of the previously issued document.

If the business disputed the chargeback and the dispute was resolved in favor of the business, the funds will be returned. In this case, a new transaction with a positive amount and the label <span class="u-richtext-element" style="background-color: rgba(68, 203, 138, 0.5)">chargeback reverse</span> will appear on the payments screen.

A new income document will also be created: a receipt or a tax invoice/receipt — depending on the business type and document settings.

Keep reading
Payouts
Security

Bit

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

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.

No payment from Bit balance. The charge is made from the card linked to Bit. If the card has insufficient funds or the credit limit is exceeded, the payment will fail.

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.

Keep reading
Payment links
Payment methods

Plan and billing

In Allpay, the plan is billed monthly. After registration, there is a 7-day trial period.

All paid services and modules are charged to the plan balance. Once a month, the outstanding amount is automatically paid: first from the payout balance, and if there are not enough funds there, then from the linked card.

Subscription fee vs processing fee

The subscription fee and payment processing fee are different charges.

The subscription fee is deducted once a month from your payouts or charged to the linked card. The payment processing fee is charged separately for each transaction, and the remaining amount is credited to the payout balance.

Trial period and billing date

After registration, every client gets a 7-day trial period. At the end of the trial period, the system will charge the subscription fee for the next billing period.

The date of the first charge becomes the fixed monthly billing date for the plan. It does not change in the future.

For example, if you registered on March 10, the trial period will end on March 17. On that day, the system will charge the first payment for the next billing period. The following charges will take place on the 17th of each month.

How the plan balance works

In the standard scenario, the plan balance does not need to be topped up in advance.

All paid services and modules that you activate during the month are charged to the balance in <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Plan</span> → <span class="u-richtext-element">Billing</span>, creating an outstanding balance.

When the billing date arrives, the outstanding balance is paid using the funds available for payout, and the plan balance becomes zero again.

If there are not enough funds on the ILS payout balance, for example, if you did not accept any payments during the month, the system will charge the linked card.

If the card charge fails, an outstanding debt is created on the plan balance. In other words, the balance remains negative until the debt is paid.

If a new module with a subscription fee is activated in the middle of a billing period, its cost is calculated proportionally to the time remaining until the next billing date.

In some cases, the plan balance can be topped up in advance by bank transfer through support. This is usually used by companies that do not have a corporate card.

Canceling your Allpay subscription

You can cancel your subscription at any time. To do this, click “Disable all” in <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Plan</span>.

After cancellation, the service will continue to work and payments will continue to be processed until the end of the paid period. After that, the service will be disabled, and no new debt will be charged for the next billing period.

The “Disable all” button disables all paid services at once:

  • main payment processing service;
  • Subscriptions module;
  • Shopify module, if it was active;
  • other paid modules, if they were active.

If you want to disable only one module, you need to do this in <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Payment modules</span>

After the service is disabled, your account and payment history are saved. If needed, you will still be able to log in to your account and view previous transactions. The service can always be activated again to resume accepting payments.

If there is an outstanding debt on the plan balance when the service is reactivated, the system will immediately try to pay it: first from the payout balance, and if there are not enough funds, then from the linked card or a newly added card.

Failed charges

If the system cannot charge any of the payment methods, an error message will appear in the Allpay interface. An email is also sent for each failed charge.

The system makes four charge attempts in total:

  • Attempt 1 — the first failed charge.
  • Attempt 2 — 2 days after the first attempt.
  • Attempt 3 — 10 days after the first attempt.
  • Attempt 4 — one month after the first attempt.

Until the final charge attempt, the service continues to work as usual. If the debt is not paid after the fourth attempt, the service will be suspended.

The unpaid debt will remain on the plan balance. It must be paid before you can continue using the service.

Four charge attempts during the month give you enough time to fix the issue without losing the ability to accept payments or create documents.

You can view the charge attempt history in <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Plan</span> → <span class="u-richtext-element">Payment methods</span>

How to pay an outstanding debt

To pay an outstanding debt, add a valid card in <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Plan</span> → <span class="u-richtext-element">Payment methods</span>, or open the menu of an already linked card by clicking the three dots and select “Try again”.

Before trying again, make sure the reason for the error has been fixed. For example, check that the card has enough funds, is not blocked, and is allowed for online payments.

You can also accept new payments so that they cover the plan debt. However, it is important to remember that each payment is processed for 3–5 days before it reaches the payout balance.

Payment methods

Charging from the payout balance is the default main payment method for all users who use the payment processing service.

The bank card that you added during registration or linked later becomes the backup payment method for the plan.

In <span class="u-richtext-element">Settings</span> → <span class="u-richtext-element">Plan</span> → <span class="u-richtext-element">Payment methods</span>, you can:

  • delete a card;
  • add a backup card;
  • set a card as the main payment method;
  • manually retry the charge if there was an error.

You can add a new card and set it as the main payment method. In this case, the payout balance charge method and the previous card will become backup payment methods.

The system first tries to charge the main method, and if the charge fails, it automatically tries to charge the backup methods.

Keep reading
Pricing
Travolta confused - no search results
No results found.
Subscribe for important updates (ad-free)
Subscribe
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

FAQ

Found 100 out of 200
No items found.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Travolta confused - no search results
No results found.

Start accepting payments

Connect a sales channel for your business today
Free sign up
7-day trial
Cancel anytime
Sign up

Currencies

Payments in ILS, USD and EUR without conversion and in any other currency with deposit in ILS.

Recurrent billing

Streamline recurring billing: automate customer card charges for subscriptions.

Weekly payouts

Option to receive payouts to a bank account weekly instead of monthly.

Apple Pay, Google Pay and Bit

Fast and convenient payment methods with no additional fees.