Help Center

В свойствах отклоненных платежей можно увидеть название ошибки и понять причину.

Коды ошибок

20004 Refusal by credit company. Please try a different card

Платёж не был одобрен банком, выпустившим карту. Для израильских карт это чаще всего связано с превышением кредитного лимита (мисгерет) или недостатком средств на счёте при оплате дебетовой картой. Для иностранных карт банк мог отклонить платёж, сочтя его подозрительным. В обоих случаях держателю карты следует обратиться в свой банк, чтобы уточнить причину отказа.

20010 Payment is not approved for debit cards

Попытка осуществить платеж в рассрочку по дебетовой карте. Такие платежи возможны только по кредитным картам и только выпущенным в Израиле. Больше информации.

The Apple Pay button allows for quick payments using iPhone, Mac, and other Apple devices.

To make the button appear on the payment page, you need to activate the module in the <span class="u-richtext-element">Modules</span> --> <span class="u-richtext-element">Apple Pay</span>.

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

Exceptions

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

• on payment pages with an installment option if the customer selects more than one installment payment;
• on payment pages of the "subscription" type.

Unsuccessful payments with the name «Applepay Payer»

Apple Pay transmits the customer's name to us only after a successful payment. Pressing the Apple Pay button initiates the payment process, and a transaction appears with the name "Applepay Payer" and the status "Unpaid". The customer then confirms the payment on their device, Apple Pay processes it, and returns the customer's name to us, which we display instead of "Applepay Payer", while the transaction status changes to "Paid successfully".

However, if the payment was not confirmed on the device or was not approved by Apple Pay, the customer's name will remain "Applepay Payer", and we will not see the reason for the decline.

In cases where the customer proceeds to payment from your website and has entered their name at the checkout stage, we will display it instead of "Applepay Payer".

You can request the customer's phone number, address, website, or other information by adding additional fields to the payment page.

This applies to payment links created through Allpay. If you are connected via the API, field setup is done on your website.

Adding input fields for payment links

1. Activating additional input fields  

Activate additional input fields in the <span class="u-richtext-element">Settings</span> ➙ <span class="u-richtext-element">Payment Links</span> section.  

2. Adding fields  

‍When creating a payment link, click <span class="u-richtext-element">Advanced</span>, then <span class="u-richtext-element">Manage Fields</span>. Add the required fields and their names, then click "Save".

The added fields will be available for ALL payment links.

3. Activating fields‍

Activate the toggle for the fields you want to display on the payment page for THIS SPECIFIC payment link.

If the field is also marked as required, the customer will not be able to proceed with the payment without filling it in.

4. After payment‍

The information entered by the customer is displayed in the transaction details on the main payment page. It is also included in payment notifications sent to Telegram, your email, and the customer.  

Field name translation

For payment links in multiple languages, field names can be translated.

In the <span class="u-richtext-element">Manage Fields</span> section, switch the language using the language selection menu and add a translation for each field.

How to insert a link  

HTML tags are allowed in input field names: <span class="u-richtext-element">a</span> for links, <span class="u-richtext-element">b</span> for bold text, <span class="u-richtext-element">i</span> for italics, and <span class="u-richtext-element">span</span> for applying custom styles.  For example, to insert a link into the name of a checkbox field, the name should look as follows:

Agree with <a href="https://allpay.co.il/terms">the terms</a>  

The result will look as follows:

«Agree with <a href="https://allpay.co.il/terms">the terms</a>»

Video tutorial

To check requests for payment creation via API, two methods are available.

Allpay API Tester

With Allpay API Tester, you can perform requests for new payment, refund, create subscription, and other operations in both live and test modes, emulating requests from your server.

Simply insert the API login/key of any integration created in the <span class="u-richtext-element">Settings</span> -> <span class="u-richtext-element">API Integrations</span> section, and fill out the form fields according to the API documentation.

If test mode is enabled for the integration, requests will be executed in the test environment.

API Tag

Each transaction processed via the API has an <span class="u-richtext-element">API</span> tag on it. By clicking on the tag, you can view headers and body of the associated request and response.

Israeli citizens are required to enter their Teudat Zehut number, which is included in the payment receipt.

Since payments can come from outside Israel, as well as from tourists or Israeli residents without a Teudat Zehut, the payment page includes a checkbox labeled “I am not an Israeli citizen”, which hides the Teudat Zehut input field.

If the payment page is accessed from outside Israel, this checkbox is enabled by default.

Hiding the field for payment links

The Teudat Zehut input field and the “I am not an Israeli citizen” checkbox can be completely hidden from the payment page. This is useful for those accepting payments exclusively from abroad.

To enable this, go to <span class="u-richtext-element">Settings</span> --> <span class="u-richtext-element">Payment Links</span> and activate the switch <span class="u-richtext-element">Hide Teudat Zehut input field</span>.

Make sure to consult your accountant before enabling this setting.

Hiding the field for API Payments

‍To pass the Teudat Zehut number or hide this field from the payment page, use the <span class="u-richtext-element">client_tehudat</span> parameter as described in the API documentation.

‍

1. Open this link in Safari: Allpay App
2. Go to your browser's menu and select Add to Home Screen.
3. Save it.

When creating a payment link, switch the selector from «I indicate the amount» to «Customer indicates amount» and provide the name of the product or service.

You can also add buttons with predefined amounts, allowing the payer to choose one or enter their own amount in the input field. To make one of the buttons preselected on the payment page, mark it with a star.

The payer will select the desired amount button or enter their own amount and proceed with the payment. The transaction will appear on the main payment screen like any other. еее

Passing the amount through a URL link

If you add <span class="u-richtext-element">?amount=AMOUNT</span> to the end of the URL link, the buttons and input fields will disappear, and the amount will be fixed.

For example, https://allpay.to/~pay/dynamic?amount=300

This helps avoid creating multiple payment links for a single service with a frequently changing price. You only need to create one link and insert the required amount into its URL when sending it to the customer.

In the article "Passing parameters through the payment link URL" you can learn about other options of this feature.

When designing a user account interface for managing tokens to charge a customer's card in line with your platform's pricing plan, it's essential to focus on user experience, transparency, and error handling.

Below are key recommendations to ensure an efficient and user-friendly interface:

Automate retries for failed charges

If a charge fails due to insufficient funds or other errors, automate the retry process to increase the likelihood of successful payment.

Recommended schedule: Attempt the charge up to 7 times, with a 1-day interval between each attempt.

If all attempts fail, terminate the rebilling process and notify the user.

Notify users about retries and allow them to top up their account or update their payment method before the next attempt.

Provide a manual retry option

Include a button that allows users to manually retry a failed payment.

This empowers users to resolve issues on their own after addressing payment failures (e.g., topping up their card).

Ensure the section with this button remains accessible, even during failed transactions.

Display refunds in transaction history

If a refund is processed, make sure it is clearly displayed in the transaction history.

Include details such as the refunded amount, reason for the refund, and the associated transaction.

It improves transparency and helps users easily track their financial activity.

Allow linking of multiple cards

Enable users to add a second card as a backup payment method.

Attempt to charge the primary card first. If it fails, automatically charge the backup card.

This reduces the likelihood of payment failures, ensuring uninterrupted service for the user.

Easy access to unsubscribe

Make the unsubscribe button visible and easy to find.

Do not automatically delete a user’s saved card unless explicitly requested. This allows users to easily return and reactivate their subscription without having to re-enter card details.

Clearly display plan and charge information

Provide detailed information about charges directly in the interface.

Show the base subscription cost, applicable taxes, fees, and any other components that make up the total charge.

This reduces confusion and prevents complaints by keeping the user fully informed.

Real-time notifications

Notify users via email or in-app messages for important events, such as failed charges, refunds, or subscription renewals.