Payment Widget Review (H2C)

The HighHelp payment widget (hereinafter referred to as the widget) is a hosted HighHelp payment page that opens in the payer’s browser and displays the payment form. The widget is used in H2C integration scenarios, when the frontend and interaction with the payment form are on the HighHelp side, and the merchant system only manages the creation of applications and processing of results.

Detailed definitions of terms are provided in the sectionGlossary. For general integration concepts, seeBasic Concepts.

When to use the widget

It is advisable to use the widget in the following cases:

  • There is no need to develop your own payment form.

  • Reduces security compliance work as payment details are entered on HighHelp's side.

  • We need a single form of payment for different countries and payment methods.

  • It is important to quickly start accepting payments with minimal changes on the front end.

If you need full control over the interface and business logic, you can use H2H integration instead of a widget. See sectionH2H Integration Overview.

Supported Scenarios

The widget supports two main types of scenarios:

  • P2P transfers via widget.

  • Internet payments (ECOM) via widget.

P2P via widget

The widget allows you to make P2P transfers (payin) in a number of countries. For each country there is a separate section with query parameters, examples and a list of supported methods.

See the following sections:

List of available methods that can be specified in the fieldpayment:widget_method, given in sectionWidget Methods.

Internet payments (ECOM) via widget

The scenario is described in detail in the sectionInternet payments via widget.

General scheme of widget operation

Below is the general procedure for processing payment through the widget. For a specific set of fields and response structure, see the profile sections for P2P and ECOM.

  1. The merchant system creates an application via API in H2C mode.

    • The request specifies:

      • cash register IDproject_id;

      • payment parameters (amount, currency, payment type);

      • widget method in fieldpayment:widget_method;

      • Alert URLsmerchant_callback_url, merchant_success_callback_url, merchant_decline_callback_url.

    • Authentication and signature are performed according to the rules from the sectionAuthentication and Signature.

  2. HighHelp accepts the request, performs checks and creates a payment request.

    • The response returns the data necessary to open the widget's payment page.

    • The structure of the response depends on the scenario and is described in the corresponding P2P or ECOM section.

  3. The frontend or backend of the merchant opens the payment page of the widget for the user.

    • The client is redirected to the transmitted URL or the widget opens in a separate window tab.

    • All payment forms and details are entered on the HighHelp side.

  4. The client enters payment information and passes the necessary checks.

    • For some operations, additional authentication may be performed (for example, 3-D Secure).

    • If necessary, additional redirects are used, described in the profile sections.

  5. HighHelp completes processing the application and updates its status.

    • Statuses and error codes are described in the sectionStatus codes.

    • Payment information is available via the API and in the merchant's account.

  6. The merchant's system receives a notification about the result.

    • Alert types and body structure depend on the scenario (P2P or ECOM).

    • It is recommended to implement digital signature verification and protection against duplicate processing.

Requirements and dependencies

For the widget to work correctly you must:

  • Use HTTPS for all URLs sent tomerchant_callback_url, merchant_success_callback_url, merchant_decline_callback_url.

  • Configure authentication of API requests according to sectionAuthentication and Signature.

  • Consider the list of supported countries and languages:

  • Transfer amounts in fractional currency units according to the rules fromCurrency codes.

Next steps

To implement integration through a widget, study sequentially: