Payments

This section provides answers to questions on how to initiate and process payments.

This section provides answers to questions on how to initiate and process payments boosting payment acceptance rates and addressing typical and atypical tasks. The questions of this group focus on how to minimise payment rejections by specifying parameters properly.

Why do I have to specify a payment method when opening Payment Page?

Short answer: this simplifies the customer scenario in the payment form, making it more user-friendly by allowing them to choose a payment method directly in the web service or by selecting the preferred method for them.

Figure 1. Detailed answer

The Payment Page payment form opens by default after the customer selects a payment method on the payment method selection page.

The Payment Page payment form opens by default after the customer selects a payment method on the payment method selection page. However, this functionality may not always be relevant. This maybe the case when the customer selects a payment method before opening Payment Page, or when they need a specific payment method for payment operations in a particular region. In such cases, requests for opening Payment Page contain the force_payment_method parameter which opens the Payment Page form with a preselected payment method. As a rule, it is the form where the customer enters payment information and other requested details and confirms the payment operation.

Along with that, there are other features that can be useful for optimising customer scenarios and use of payment methods—for example, limiting the list of payment methods (using the hide parameter).

What can be specified in the payment description?

Short answer: if this parameter is mandatory, it must contain the reason for processing the operation; if this parameter is optional, it can contain any additional information.

Figure 2. Detailed answer
Payment requests contain the description parameter that can be mandatory (for example, with refunds) or optional depending on a payment method and type of operation. If you want to know in what cases this parameter is required, see the sections with the descriptions of payment methods.
  • If description is mandatory, its value must contain an explanation for the operation.
  • If description is optional, its value can contain any additional information about the payment.

If descriptions are provided in requests, they are used in callbacks, displayed in the Dashboard interface, and can be helpful for merchants in payment analysis.