Alfa-Click

Overview

Note:

Two technical implementations are currently supported for working with the Alfa-Click method: the new one described in this section and the old one described in the section Alfa-Click (legacy).

Details about the difference between these implementations and how to switch from the old implementation to the new one should be clarified with the ECommPay key account manager.

Alfa-Click is a payment method that allows customers to make payments through Alfa-Bank online banking. Purchases are performed by using Payment Page and Gate, refunds—by using Gate.

General information

Payment method type Online banking
Countries and regions RU, KZ
Payment currencies EUR, KZT, RUB, USD
Currency conversion
Purchases +
Payouts
Stored credentials payments
Full refunds +
Partial refunds +
Chargebacks
Notes
Onboarding and access fee Refer to your key account manager ECommPay

Interaction diagram

Payment processing through the Alfa-Click payment method requires merchant's web service, one of the interfaces and the payment platform of ECommPay, as well as bank technical facilities.



Operations support

  Interfaces Amounts, RUB
Payment Page CMS Plug-ins Gate Dashboard minimum maximum
Purchases + + 1.00
Full refunds +
Partial refunds +

Processing scenarios

For the Alfa-Click method, there are two options to perform a purchase: to redirect a customer to the Alfa-Click service or to generate and display the instructions to a customer to finish the purchase independently, a refund is performed with the notification of a customer via web service.

Figure: Purchase by using Payment Page with redirection



Figure: Purchase by using Payment Page with instruction



Figure: Purchase by using Gate with redirection



Figure: Purchase by using Gate with instruction



Figure: Refund by using Gate procedure diagram



The sections that follow provide detailed information about what you need to perform payments and how you can analyse the information on payments and operations.

Purchase by using Payment Page

General information

In the Alfa-Click method, there are two options to perform a purchase: to redirect a customer to the Alfa-Click service or to generate and display the instructions to a customer to finish the purchase independently. In any scenario to perform a purchase by using Payment Page, the merchant web service should send a request with all the required parameters and signature to the ECommPay URL and get the callback with the payment result from the payment platform. When opening Payment Page, you can have Payment Page opened with the Alfa-Click method selected. For more information about preselecting payment methods, see in Preselecting payment method.

The full sequences and particularities of the purchase process are provided below.



Figure: Purchase sequence by using Payment Page with redirection

  1. Customer initiates payment on the merchant's web service side.
  2. The web service sends the request for Payment Page opening to the specified ECommPay URL.
  3. The request for opening is redirected to the payment platform.
  4. The payment platform performs the initial request processing that involves validation of the required parameters and signature.
  5. Requested Payment Page is generated into the ECommPay payment platform as specified in the project settings and the request parameters.
  6. Payment Page is displayed to the customer.
  7. The customer selects the Alfa-Click payment method.
  8. The payment platform receives the purchase request for payment processing.
  9. The payment platform performs the internal purchase request processing and sends it to the Alfa-Click service.
  10. The purchase request is processed on the Alfa-Click service side.
  11. The Alfa-Click service generates the data for redirecting the customer to its website form and sends it to the payment platform.
  12. The payment platform sends the redirection data to Payment Page.
  13. The customer is redirected to the Alfa-Click website.
  14. The customer completes all the payment steps required.
  15. The payment is processed on the Alfa-Click service side.
  16. The result is displayed to the customer on the Alfa-Click service.
  17. The customer is redirected to Payment Page.
  18. The Alfa-Click service sends the payment result to the payment platform.
  19. The payment platform sends a callback with the payment result to the web service.
  20. The payment platform sends the result to Payment Page.
  21. A page with the payment result information is displayed to the customer on Payment Page.


Figure: Purchase sequence by using Payment Page with instructions

  1. A customer initiates a purchase on the merchant's web service.
  2. The web service sends the request for Payment Page opening to the specified ECommPay URL.
  3. The request for opening is redirected to the payment platform.
  4. The payment platform performs the initial request processing that involves validation of the required parameters and signature.
  5. Requested Payment Page is generated into the ECommPay payment platform as specified in the project settings and the request parameters.
  6. Payment Page is displayed to the customer.
  7. The customer selects the Alfa-Click method.
  8. The form for entering the login in Alfa-Click service is displayed to the customer on Payment Page.
  9. The customer enters the login.
  10. The payment instruction is generated and displayed to the customer on Payment Page.
  11. The payment platform receives the purchase request for payment processing from Payment Page.
  12. The payment platform performs the internal purchase request processing and sends it to the Alfa-Click bank service.
  13. The bank service processes the purchase request.
  14. The bank service forms a bill for the customer. The invoice is valid for 7 days.
  15. The customer independently redirects to the bank website to complete all the payment steps required by paying the bill or sending the SMS to the bank.
  16. The payment is processed on the bank side.
  17. A page with the payment result information is displayed to the customer on Alfa-Click service.
  18. The Alfa-Click service sends the result notification to the payment platform.
  19. The payment platform sends a callback with the payment result to the web service.

The sections that follow discuss in more details the request format and the Payment Page parameters to use in the Alfa-Click payment method and provide the information on the format of callbacks with payment results. For the general information on how to use the API, see Payment Page API Description.

Request format

There are several things you need to consider when using the Alfa-Click method:

  1. You must provide values for the basic minimum of parameters. Listed below are the parameters that are mandatory for any payment method:
    • customer_id—the unique ID of the customer within your project
    • project_id—the project ID obtained from ECommPay
    • payment_id—payment ID unique within the project
    • payment_currency—payment currency in ISO-4217 alpha-3 format
    • payment_amount—payment amount in minor units
  2. The currency of payment can only be EUR, KZT, RUB, or USD.
  3. Additionally you must use the customer_account_number parameter—the customer account number in the Alfa-Click service.
  4. To preselect Alfa-Click as the payment method on Payment Page for customers, pass the code alfa-click in the force_payment_method parameter in the request for opening.
  5. If required, you can also add any other additional parameters Payment Page supports. For information about all parameters available in the Alfa-Click method, see Payment Page invocation parameters.
  6. After you specify all the parameters you need, you must create the signature for the request. For instructions on how to sign a payment request, see Signature generation and verification.

Thus, a correct payment request in the Alfa-Click method must include project, customer and payment IDs, the currency and the amount of a payment, the account number of a customer, and the signature as shown in the following example:

EPayWidget.run(
    { payment_id: 'X03936', 
      payment_amount: 10000, 
      payment_currency: 'RUB', 
      project_id: 35,
      customer_id: '123', 
      customer_account_number: 'u_customer',
      signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y1Y4HASCQ9tT4DqtVUkDJrOcZzUCwX6R\/ekpZhkIQg=="
    }
)

For information about all parameters available in the Alfa-Click method , see Payment Page invocation parameters.

Callback format

The Alfa-Click method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.

The following is the example of a callback with an information about successful 100,00 RUB purchase by using account number account1 made by the customer in the 386 project.

Figure: Example of a successful purchase callback

 {
        "project_id": 386,
        "payment": {
            "id": "EP1bb6-c379",
            "type": "purchase",
            "status": "success",
            "date": "2019-03-04T11:07:22+0000",
            "method": "alfa-click",
            "sum": {
                "amount": 10000,
                "currency": "RUB"
            },
            "description": ""
        },
        "account": {
            "number": "account1"
        },
        "operation": {
            "id": 632,
            "type": "sale",
            "status": "success",
            "date": "2019-03-04T11:07:22+0000",
            "created_date": "2019-03-04T11:07:08+0000",
            "request_id": "e0865f7f",
            "sum_initial": {
                "amount": 10000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "RUB"
            },
            "provider": {
                "id": 1310,
                "payment_id": "94b4a6a43480d57ee45ab107",
                "date": "2018-10-26T07:25:18+0000",
                "auth_code": "",
                "endpoint_id": "alfabank"
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "yMGGZSFFOatC0/gyFF2zlFgFfslBksxuYqVTjQ0T0DMIA9evlziWay30F+QBQ=="
    }

The following is the example of a callback for a purchase declined due to insufficient funds on customer account.

Figure: Example of a declined purchase callback

 {
        "project_id": 386,
        "payment": {
            "id": "EP1bb6-c379",
            "type": "purchase",
            "status": "decline",
            "date": "2019-03-04T11:07:22+0000",
            "method": "alfa-click",
            "sum": {
                "amount": 10000,
                "currency": "RUB"
            },
            "description": ""
        },
        "account": {
            "number": "account1"
        },
        "operation": {
            "id": 632,
            "type": "sale",
            "status": "decline",
            "date": "2019-03-04T11:07:22+0000",
            "created_date": "2019-03-04T11:07:08+0000",
            "request_id": "e0865f7f",
            "sum_initial": {
                "amount": 10000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "RUB"
            },
            "provider": {
                "id": 1310,
                "payment_id": "94b4a6a43480d57ee45ab107",
                "date": "2018-10-26T07:25:18+0000",
                "auth_code": "",
                "endpoint_id": "alfabank"
            },
            "code": "20105",
            "message": "Insufficient funds on customer account"
        },
        "signature": "yMGGZSFFOatC0/gyFF2zlFgFfslBksxuYqVTjQ0T0DMIA9evlziWay30F+QBQ=="
    }

Related topics

The following topics might be useful when implementing payments through Payment Page:

Purchase by using Gate

General information

In the Alfa-Click method, there are two options to perform a purchase: to redirect a customer to the Alfa-Click service or to generate and display the instructions to a customer to finish the purchase independently. When processing a purchase by using Gate with redirection, the merchant web service should send a request with all the required parameters and signature to the ECommPay URL and get the callback with the payment result from the payment platform. In the case of displaying instructions, the merchant web service should send a request with all the required parameters and signature to the ECommPay URL, prepare and display the instructions to the customer, and get the callback with the payment result from the payment platform. The full sequences and particularities of the purchase processes are provided below.



Figure: Purchase sequence by using Gate with redirection

  1. A customer initiates a purchase through Alfa-Click on the merchant's web service side.
  2. The web service sends the request for processing the purchase by using Gate to the specified ECommPay URL.
  3. The payment platform receives the request for processing the purchase from Gate.
  4. The payment platform performs the initial request processing that includes validation of the required parameters and signature.
  5. The payment platform sends the response with request receipt confirmation and correctness check result to the web service. For more information, see Response format.
  6. The payment platform performs the internal payment request processing and redirects the request to the Alfa-Click service.
  7. The request is processed on the Alfa-Click side.
  8. The Alfa-Click service sends the data for redirecting the customer to the Alfa-Click service to the payment platform.
  9. The payment platform sends the callback with the redirection data in the redirect_data object to the web service.
  10. The customer is redirected from the web service to the Alfa-Click service.
  11. The customer completes all the payment steps required.
  12. The payment is processed on the Alfa-Click side.
  13. The result is displayed to the customer.
  14. The customer is redirected to the merchant's web service.
  15. The Alfa-Click service sends the payment result notification to the payment platform.
  16. The ECommPay payment platform sends a callback to the web service.
  17. The customer receives the payment result on the web service.


Figure: Purchase sequence by using Gate

  1. A customer initiates a purchase through Alfa-Click on the merchant's web service side.
  2. The web service sends the request for processing the purchase by using Gate to the specified ECommPay URL.
  3. The payment platform receives the request for processing the purchase from Gate.
  4. The payment platform performs the initial request processing that includes validation of the required parameters and signature.
  5. The payment platform sends the response with request receipt confirmation and correctness check result to the web service. For more information, see Response format.
  6. The payment instruction is generated and displayed to the customer on web service.
  7. The payment platform performs the internal payment request processing and redirects the request to the Alfa-Click bank service.
  8. The bank service processes the purchase request.
  9. The bank service forms a bill for the customer. The invoice is valid for 7 days.
  10. The customer independently redirects to the bank website to complete all the payment steps required by paying the bill or sending the SMS to the bank.
  11. The payment is processed on the bank side.
  12. A page with the payment result information is displayed to the customer on Alfa-Click service.
  13. The bank service sends the payment result notification to the payment platform.
  14. The ECommPay payment platform sends a callback to the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the Alfa-Click payment method and provide the information about formats of the data for redirecting customers and the information about the format of callbacks with payment results. The general information about working with API see in the API Description section.

Request format

There are several things you must consider when using purchase requests in the Alfa-Click method:
  1. You perform purchase by sending the request to /v2/payment/online-banking/alfa-click/sale by using POST (HTTP) method. This endpoint refers to the online banking group: /v2/payment/online-banking/{payment_method}/sale
  2. The following objects and parameters must be specified in the request:
    • Object general—general purchase information:
      • project_id—project identifier
      • payment_id—unique payout identifier
      • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification
    • Object customer—customer information:
      • id—the unique ID of the customer within your project
      • account_id—login in the Alfa-Click service
      • ip_address—customer IP address
      • phone—phone number (required only for customers from Kazakhstan)
    • Object payment—purchase information:
      • amount—purchase amount
      • currency—purchase currency in the ISO-4217 alpha-3 format
  3. The currency of payment can only be EUR, KZT, RUB, or USD.
  4. If required, you can also add any other additional parameters Gate supports.

Thus, a correct payment request in the Alfa-Click method must include project, customer and payment IDs, the currency and the amount of a payment, IP address and account number of a customer, and the signature as shown in the following example:

Figure: Purchase request example

{
    "general": {
        "project_id": 35,
        "payment_id": "Payment 12",
        "signature": "2tlMuYxLW9Yu6RETr8pdCfmi0UPE8euD+o4EVPjLyfbOQ+9ajAteg5lPk96Q=="
  },
    "customer": {
        "id": "123",
        "account_id": "account_1",
        "ip_address": "1.1.1.1" 
  },
    "payment": {
        "amount": 10000,
        "currency": "RUB"
  }
}

Formats of the data for payment completing

Since there are two scenarios for customers to finish a payment by using the Alfa-Click service, you can contact the ECommPay key account manager for advice and choose the most convenient scenario. The format of data for customer redirection and an example of instructions for displaying to the customer are shown below.

To redirect a customer from the web service to the Alfa-Click site, you must receive a callback from the payment platform containing the URL for redirection in the redirect_data.url parameter and data to be sent in the request body in the redirect_data.body parameter, and use these parameters when opening the HTML page using the method specified in the redirect_data.method parameter.

The following is the callback fragment containing the redirection data.

"redirect_data": {
                    "body": {
                        "redirectType": "redirect"
                    },
                    "method": "GET",
                    "url": "https://alfa-click.ru/checkout/payments/?orderId=2540-a000-1fc"
                },

To complete the payment by using the instruction, you must generate and display it to a customer describing further actions. The following text is an example of such instruction: “How to pay. Alfa Bank will sent the message to confirm the payment. Replay to it, and the money will be debited from your account. If the message is not received (or you receive the message with the bill information), pay the bill via Alfa-Click or Alfa-Mobile.” The Alfa-Click service logo should be added in the instruction. More information you can obtain from the ECommPay key account manager.

Callback format

The standard format for callbacks is used to deliver purchase results from Alfa-Click. For more information, see Callbacks.

The following is the example of a callback with an information about successful 100,00 RUB purchase from the account number account1 made by the customer in the 386 project.

Figure: Example of a succeed purchase callback

 {
        "project_id": 386,
        "payment": {
            "id": "EP1bb6-c379",
            "type": "purchase",
            "status": "success",
            "date": "2019-03-04T11:07:22+0000",
            "method": "alfa-click",
            "sum": {
                "amount": 10000,
                "currency": "RUB"
            },
            "description": ""
        },
        "account": {
            "number": "account1"
        },
        "operation": {
            "id": 632,
            "type": "sale",
            "status": "success",
            "date": "2019-03-04T11:07:22+0000",
            "created_date": "2019-03-04T11:07:08+0000",
            "request_id": "e0865f7f",
            "sum_initial": {
                "amount": 10000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "RUB"
            },
            "provider": {
                "id": 1310,
                "payment_id": "94b4a6a43480d57ee45ab107",
                "date": "2018-10-26T07:25:18+0000",
                "auth_code": "",
                "endpoint_id": "alfabank"
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "yMGGZSFFOatC0/gyFF2zlFgFfslBksxuYqVTjQ0T0DMIA9evlziWay30F+QBQ=="
    }

The following is the example of a callback for a purchase declined due to insufficient funds on customer account.

Figure: Example of a declined purchase callback

 {
        "project_id": 386,
        "payment": {
            "id": "EP1bb6-c379",
            "type": "purchase",
            "status": "decline",
            "date": "2019-03-04T11:07:22+0000",
            "method": "alfa-click",
            "sum": {
                "amount": 10000,
                "currency": "RUB"
            },
            "description": ""
        },
        "account": {
            "number": "account1"
        },
        "operation": {
            "id": 632,
            "type": "sale",
            "status": "decline",
            "date": "2019-03-04T11:07:22+0000",
            "created_date": "2019-03-04T11:07:08+0000",
            "request_id": "e0865f7f",
            "sum_initial": {
                "amount": 10000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "RUB"
            },
            "provider": {
                "id": 1310,
                "payment_id": "94b4a6a43480d57ee45ab107",
                "date": "2018-10-26T07:25:18+0000",
                "auth_code": "",
                "endpoint_id": "alfabank"
            },
            "code": "20105",
            "message": "Insufficient funds on customer account"
        },
        "signature": "yMGGZSFFOatC0/gyFF2zlFgFfslBksxuYqVTjQ0T0DMIA9evlziWay30F+QBQ=="
    }

Related topics

The following topics might be useful when implementing payments through Gate:

Refund by using Gate

General information

Alfa-Click supports full and partial refunds processing. To perform a refund through the Alfa-Click method, merchant's web service sends a request with all the required parameters and signature to ECommPay URL, and receives a callback with the payment result. The full sequence of the payout process is provided below.



Figure: Refund sequence by using Gate

  1. A customer orders a refund on the merchant's web service side.
  2. Merchant's web service sends the request for the refund processing by using Gate to the appropriate ECommPay URL.
  3. Gate redirects the request to the ECommPay payment platform.
  4. The payment platform performs all the necessary checks and processes the request.
  5. The reply with the request processing results is sent to the merchant's web service. For more information, see Response format.
  6. The payment platform redirects the refund request to the Alfa-Click service.
  7. The payment is processed on the Alfa-Click side.
  8. Alfa-Click sends the result notification to the payment platform.
  9. The payment platform sends a callback with the payment result to the web service.
  10. The customer receives the refund result from the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the Alfa-Click payment method and provide the information on the format of callbacks with refund results.

Request format

There are several things you must consider when using refund requests in the Alfa-Click method:
  1. You perform purchase by sending the request to /v2/payment/online-banking/alfa-click/refund by using POST (HTTP) method. This endpoint refers to the online banking group: /v2/payment/online-banking/{payment_method}/refund
  2. The following objects and parameters must be specified in any request:
    • Object general—general refund information:
      • project_id—project identifier
      • payment_id—unique refund identifier
      • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification
    • Object customer—customer information:
      • ip_address—customer IP address
    • Object payment—refund information:
      • description—comment or description
      • amount—refund amount in minor units (mandatory for partial refund only)
      • currency—refund currency in ISO-4217 alpha-3 format (mandatory for partial refund only)
  3. If required, you can also add any other additional parameters Gate supports.

Thus, a correct refund request in the Alfa-Click method must include project and payment IDs, customer IP address, currency and amount of the refund, as shown in the following example:

Figure: Example of a refund request

{
   "general": {    
    "project_id": 239,    
    "payment_id": "refund_02",   
    "signature": "of8k9xerKSK4XL1QFaDH3p9Mh0CIcjmOwSwKJ7KLTZYO56lCv+f1M0Sf/7eg=="
  },  
   "customer": {    
     "ip_address": "1.2.3.4" 
  },  
   "payment": {    
     "amount": 50000,    
     "currency": "RUB",
     "description": "refund_02"
 }
}

Callback format

The Alfa-Click method uses the standard format for callbacks to deliver refund results. For more information, see Callbacks.

The following is the example of a callback with an information about successful 100,00 RUB partial refund for the customer account account1 in the 386 project.

Figure: Example of a successful refund callback

{
        "project_id": 386,
        "payment": {
            "id": "EP1bb6-c379",
            "type": "purchase",
            "status": "partially refunded",
            "date": "2019-03-04T11:16:29+0000",
            "method": "alfa-click",
            "sum": {
                "amount": 50000,
                "currency": "RUB"
            },
            "description": ""
        },
        "account": {
            "number": "account1"
        },
        "operation": {
            "id": 633,
            "type": "refund",
            "status": "success",
            "date": "2019-03-04T11:16:29+0000",
            "created_date": "2019-03-04T11:16:25+0000",
            "request_id": "88c5433b45f91",
            "sum_initial": {
                "amount": 10000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "RUB"
            },
            "provider": {
                "id": 1310,
                "payment_id": "94b4a6a434857ee45ab107",
                "date": "2019-03-04T11:16:28+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "NPKaC8A2wQehyGWVYTVTQ14HE4JBB+H2FVHbS1YTT9VOHG1VFJ5zqg=="
    }

The following is the example of a callback for a refund declined due to the refund amount is more than init amount.

Figure: Example of a declined refund callback

{
        "project_id": 386,
        "payment": {
            "id": "EP1bb6-c379",
            "type": "purchase",
            "status": "success",
            "date": "2019-03-04T11:16:29+0000",
            "method": "alfa-click",
            "sum": {
                "amount": 50000,
                "currency": "RUB"
            },
            "description": ""
        },
        "account": {
            "number": "account1"
        },
        "operation": {
            "id": 633,
            "type": "refund",
            "status": "decline",
            "date": "2019-03-04T11:16:29+0000",
            "created_date": "2019-03-04T11:16:25+0000",
            "request_id": "88c5433b45f91",
            "sum_initial": {
                "amount": 100000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 100000,
                "currency": "RUB"
            },
            "provider": {
                "id": 1310,
                "payment_id": "94b4a6a434857ee45ab107",
                "date": "2019-03-04T11:16:28+0000",
                "auth_code": ""
            },
            "code": "3283",
            "message": "Refund amount more than init amount"
        },
        "signature": "NPKaC8A2wQehyGWVYTVTQ14HE4JBB+H2FVHbS1YTT9VOHG1VFJ5zqg=="
    }

Related topics

The following topics might be useful when implementing payments through Gate:

Testing

General information

For the Alfa-Click method the testing of purchases by using Payment Page and Gate..

Testing can be performed within a test project, to enable and disable the testing availability, contact ECommPay technical support via support@ecommpay.com.

When performing a test payment, take into account that you must specify the identifier of the test project in the requests, the currency can only be RUB, and the interfaces of the payment forms emulator of Payment Page and Alfa-Click may differ from the ones used in the production environment.



Test payments statuses

When testing purchases, the final payment status is determined by the amount specified in the request:

  • decline status with 40000 or 40400 amount
  • success status with any other amount

Purchases by using Payment Page

To perform a test purchase by using Payment Page, do the following:

  1. Send a correct test request for Payment Page opening to the payment platform.
  2. If the alfa-click method was not specified in the request—select the method on the emulator page.
  3. Click the Success or Decline button (depending on the amount specified in the request).
  4. Accept a callback with information about the payment result.

If, while on the web page of the Alfa-Click payment form emulator, the Success or Decline button is not clicked within 30 minutes, the payment status is set to decline and the corresponding callback is sent from the payment platform side (regardless of the amount indicated in the request).

The full information about purchase process by using Alfa-Click through Payment Page is provided in the section Purchase by using Payment Page.

Purchases by using Gate

To perform a test purchase by using Gate, do the following:

  1. Send a correct test request for purchase to the payment platform.
  2. Accept a callback with redirection data.
  3. Go to the received URL and click the Success or Decline button (depending on the amount specified in the request).
  4. Accept a callback with information about the payment result.

If, while on the web page of the Alfa-Click payment form emulator, the Success or Decline button is not clicked within 30 minutes, the payment status is set to decline and the corresponding callback is sent from the payment platform side (regardless of the amount indicated in the request).

The full information about purchase process by using Alfa-Click through Gate is provided in the section Purchase by using Gate.

Analysis of payments results

As with other payment methods ECommPay offers, when using the Alfa-Click method, you have several options to analyse the information about payments and operations performed by using the method—alone or in conjunction with other methods.

You can load and analyse all the necessary information in Dashboard, for instance you can use the analytic panels on the Analytics tab to this end.

Also, you can export the information for further analysis by using third party analytical tools. The following options are available:

  • Dashboard allows you to download reports in CSV and XLS formats—by using the tools on the Payments tab. You can perform export as a one-time download to your local computer or have payment data regularly exported and delivered to email addresses you specify.
  • Data API allows you to have payment information exported in JSON format and delivered to a URL you specify. The payment information is exported by using the /operations/get queries.

If you have any further questions regarding payment data analysis, contact ECommPay technical support.