Cash payments in different Eastern European and Central Asian countries

Overview

Cash payments in different Eastern European and Central Asian countries is a payment method that allows customers to make payments in cash via terminals and ATMs that support cash deposits. You can perform purchases through this method by using Payment Page and Gate.

General information

Payment method type cash payments
Countries and regions AM, BY, GE, KZ, LV, MD, RU, TJ, UA
Payment currencies KZT (for KZ), EUR (for LV), USD (for AM, BY, GE, MD, TJ), RUB (for RU), UAH (for UA)
Currency conversion
Purchases +
Payouts
Stored credentials payments
Full refunds
Partial refunds
Chargebacks  
Special considerations
Obtaining access to the payment method and access fee refer to your ECommPay key account manager

Interaction diagram

Payment processing through the Cash payments in different Eastern European and Central Asian countries payment method requires merchant's web service, one of the interfaces and the payment platform of ECommPay, as well as provider technical facilities.



Operations support

  Interfaces Amounts, RUB
Payment Page CMS Plug-ins Gate Dashboard (Old Dashboard) minimum maximum
Purchases + + 1.00 15,000.00

Processing scenarios

In the Cash payments in different Eastern European and Central Asian countries method, to perform a purchase operation, you need to redirect a customer to the provider service.

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 Cash payments in different Eastern European and Central Asian countries method, when processing 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 Cash payments in different Eastern European and Central Asian countries method selected. For more information about preselecting payment methods, see in Preselecting payment methods. The full sequence and particularities of the purchase process are provided below.



Figure: Purchase by using Payment Page

  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 Cash payments in different Eastern European and Central Asian countries method.
  8. The payment platform receives the purchase request for payment processing from Payment Page.
  9. The payment platform performs the internal purchase request processing and sends it to the provider service.
  10. The purchase request is processed on the provider service side.
  11. The provider 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 customer redirection data to Payment Page.
  13. The customer is redirected to the provider website.
  14. The customer performs the payment at one of the available terminals or ATMs.
  15. The payment is processed on the provider side.
  16. The customer is redirected to Payment Page.
  17. The provider service sends the result notification to the payment platform.
  18. The payment platform sends a callback with the payment result to the web service.
  19. The payment platform sends the result to Payment Page.
  20. A page with the payment result information is displayed to the customer on Payment Page.

The sections that follow discuss in more details the request format and the Payment Page parameters to use in the Cash payments in different Eastern European and Central Asian countries 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 Cash payments in different Eastern European and Central Asian countries method:

  1. You must provide values for the basic minimum of parameters. Listed below are the parameters that are mandatory for any payment method:
    • 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 currency units
    • customer_id—ID of the customer within the project
  2. Additionally the following parameter must be used—customer_phone (the phone number of the customer, must be specified using a country code and without punctuation or special characters, for example 79031234567). If the request is missing the parameter, on Payment Page the additional field is displayed to the customer to input missing data. For more details, see Submission of additional payment information.
  3. The currencies of payment can only be KZT (for KZ), EUR (for LV), USD (for AM, BY, GE, MD, TJ), UAH (for UA).
  4. If you need to have payment form displayed with the Cash payments in different Eastern European and Central Asian countries method selected, set the force_payment_method parameter to cis-cash.
  5. If required, you can also add any other additional parameters Payment Page supports.
  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 Cash payments in different Eastern European and Central Asian countries method must include project, customer, and payment IDs, the currency and the amount of a payment, as well as the phone number of the customer, as shown in the following example:

EPayWidget.run(
    { payment_id: 'X03936', 
      payment_amount: 10000, 
      payment_currency: 'KZT', 
      project_id: 35, 
      customer_id: 'customer1',
      customer_phone: '79251234567',
      signature: "kUi2x9dKHAVNU0FYUkDJrOcZzUCwX6R\/ekpZhkIQg=="
    }
)

For information about all parameters available in the Cash payments in different Eastern European and Central Asian countries method, see Payment Page invocation parameters.

Callback format

The Cash payments in different Eastern European and Central Asian countries 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 1.00 KZT purchase made in the 386 project.

Figure: Example of a successful purchase callback

{
    "project_id": 386,
    "payment": {
        "id": "ORDER_110035_37773821",
        "type": "purchase",
        "status": "success",
        "date": "2021-03-18T08:00:42+0000",
        "method": "cis",
        "sum": {
            "amount": 100,
            "currency": "KZT"
        },
        "description": ""
    },
    "account": {
        "number": "12345"
    },
    "customer": {
        "phone": "79031234567"
    },
    "operation": {
        "id": 932,
        "type": "sale",
        "status": "success",
        "date": "2021-03-18T08:00:42+0000",
        "created_date": "2021-03-18T08:00:36+0000",
        "request_id": "a2e86976c15c47c14e5146cb833b8f75ebe62e-00000001",
        "sum_initial": {
            "amount": 100,
            "currency": "KZT"
        },
        "sum_converted": {
            "amount": 100,
            "currency": "KZT"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 2994,
            "payment_id": "5aaa9090d1d4a12f3aefddfeb9e4b347",
            "auth_code": "",
            "endpoint_id": "cash",
            "date": "2021-03-18T08:00:41+0000"
        }
    },
    "signature": "KrxiE3eybtg9ALpT+FLgAyjV8wLf+jj55rhGGWAn3gsXk0FgeRGUL+Q=="
}

The following is the example of a callback for a declined purchase.

Figure: Example of a declined purchase callback

{
    "project_id": 386,
    "payment": {
        "id": "ORDER_78064508",
        "type": "purchase",
        "status": "decline",
        "date": "2021-03-18T08:01:45+0000",
        "method": "cis",
        "sum": {
            "amount": 11900,
            "currency": "KZT"
        },
        "description": ""
    },
    "account": {
        "number": "123456"
    },
    "customer": {
        "phone": "79031234567"
    },
    "operation": {
        "id": 933,
        "type": "sale",
        "status": "decline",
        "date": "2021-03-18T08:01:45+0000",
        "created_date": "2021-03-18T08:01:44+0000",
        "request_id": "0a53ba5fde280cccd348481c268f164159-00000001",
        "sum_initial": {
            "amount": 11900,
            "currency": "KZT"
        },
        "sum_converted": {
            "amount": 11900,
            "currency": "KZT"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 2994,
            "payment_id": "d0e725fcafe227fc6b07813cb4288069",
            "auth_code": "",
            "endpoint_id": "cash",
            "date": "2021-03-18T08:01:44+0000"
        }
    },
    "signature": "Vl6REJeT/BaO67IYM8hcTwiTJ...uKZsudzyxAqtbU/HcvQ=="
}

Related topics

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

Purchase by using Gate

General information

In the Cash payments in different Eastern European and Central Asian countries method, when processing a purchase by using Gate, the merchant web service is required to do the following:

  1. Send a request with all the required parameters and signature to the ECommPay URL.
  2. Perform the redirection of a customer to the provider service.
  3. Get the callback with the payment result from the payment platform.

The following diagram provides the detailed picture of the payment processing procedure.



Figure: Purchase by using Gate

  1. A customer initiates a purchase through Cash payments in different Eastern European and Central Asian countries 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 provider service.
  7. The request is processed on the provider side.
  8. The provider service sends the data for redirecting the customer to the provider 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 provider service.
  11. The customer performs the payment at one of the available terminals or ATMs.
  12. The payment is processed on the provider side.
  13. The customer is redirected to the merchant's web service.
  14. The provider service sends the payment result notification to the payment platform.
  15. The payment platform sends a callback to the web service.
  16. The customer receives the payment result on the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the Cash payments in different Eastern European and Central Asian countries payment method and provide the information on the format of callbacks with purchase results.

Request format

There are several things you must consider when using purchase requests in the Cash payments in different Eastern European and Central Asian countries method:
  1. You perform purchase by sending the /v2/payment/cash/cis/sale request by using POST (HTTP) method. This request refers to the online banking requests group: /v2/payment/cash/{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—ID of the customer within the project
      • ip_address—customer IP address
    • Object payment—purchase information:
      • amount—purchase amount in minor currency units
      • currency—purchase currency in the ISO-4217 alpha-3 format
  3. Additionally it is recommended to specify the phone number of the customer in the phone parameter of the customer object. If the request is missing the parameter, the parameter is sent in the clarification callback. For more details, see Submission of additional payment information.
  4. The currencies of payment can only be KZT (for KZ), EUR (for LV), USD (for AM, BY, GE, MD, TJ), UAH (for UA).
  5. If required, you can also add any other additional parameters Gate supports.

Thus, a correct payment request in the Cash payments in different Eastern European and Central Asian countries method must include project, payment and customer IDs, customer phone number, currency and amount of the purchase, as shown in the following example:

Figure: Example of a purchase request

{
    "general": {
        "project_id": 35,
        "payment_id": "Payment 12",
        "signature": "2tlMuYxLW9Yu6ReuD+o4EVPjLyfbOQ+9ajAteg5lPk96Q=="
  },
    "customer": {
        "ip_address": "1.1.1.1",
        "id": "123",
        "phone": "79251234567"
  },
    "payment": {
        "amount": 10000,
        "currency": "KZT"
  }
}

Formats of the customer redirection data

To redirect a customer from the web service to the provider 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": {
            "method": "GET",
            "body": {...},
            "url": "http://example.com/example/a/acs/29d7454b70adad712aa5b536d449c7f7"
        }

Callback format

The Cash payments in different Eastern European and Central Asian countries 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 1.00 KZT purchase made in the 386 project.

Figure: Example of a successful purchase callback

{
    "project_id": 386,
    "payment": {
        "id": "ORDER_110035_37773821",
        "type": "purchase",
        "status": "success",
        "date": "2021-03-18T08:00:42+0000",
        "method": "cis",
        "sum": {
            "amount": 100,
            "currency": "KZT"
        },
        "description": ""
    },
    "account": {
        "number": "12345"
    },
    "customer": {
        "phone": "79031234567"
    },
    "operation": {
        "id": 932,
        "type": "sale",
        "status": "success",
        "date": "2021-03-18T08:00:42+0000",
        "created_date": "2021-03-18T08:00:36+0000",
        "request_id": "a2e86976c15c47c14e5146cb833b8f75ebe62e-00000001",
        "sum_initial": {
            "amount": 100,
            "currency": "KZT"
        },
        "sum_converted": {
            "amount": 100,
            "currency": "KZT"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 2994,
            "payment_id": "5aaa9090d1d4a12f3aefddfeb9e4b347",
            "auth_code": "",
            "endpoint_id": "cash",
            "date": "2021-03-18T08:00:41+0000"
        }
    },
    "signature": "KrxiE3eybtg9ALpT+FLgAyjV8wLf+jj55rhGGWAn3gsXk0FgeRGUL+Q=="
}

The following is the example of a callback for a declined purchase.

Figure: Example of a declined purchase callback

{
    "project_id": 386,
    "payment": {
        "id": "ORDER_78064508",
        "type": "purchase",
        "status": "decline",
        "date": "2021-03-18T08:01:45+0000",
        "method": "cis",
        "sum": {
            "amount": 11900,
            "currency": "KZT"
        },
        "description": ""
    },
    "account": {
        "number": "123456"
    },
    "customer": {
        "phone": "79031234567"
    },
    "operation": {
        "id": 933,
        "type": "sale",
        "status": "decline",
        "date": "2021-03-18T08:01:45+0000",
        "created_date": "2021-03-18T08:01:44+0000",
        "request_id": "0a53ba5fde280cccd348481c268f164159-00000001",
        "sum_initial": {
            "amount": 11900,
            "currency": "KZT"
        },
        "sum_converted": {
            "amount": 11900,
            "currency": "KZT"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 2994,
            "payment_id": "d0e725fcafe227fc6b07813cb4288069",
            "auth_code": "",
            "endpoint_id": "cash",
            "date": "2021-03-18T08:01:44+0000"
        }
    },
    "signature": "Vl6REJeT/BaO67IYM8hcTwiTJ...uKZsudzyxAqtbU/HcvQ=="
}

Related topics

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

Testing

General information

For the Cash payments in different Eastern European and Central Asian countries method the testing of purchases by using 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 available currencies are EUR, KZT, RUB, UAH, USD, the interface of the payment forms emulator of the method Cash payments in different Eastern European and Central Asian countries may differ from the one 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 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.

The full information about purchase process by using the method Cash payments in different Eastern European and Central Asian countries 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 Cash payments in different Eastern European and Central Asian countries 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 (Old Dashboard), for instance you can use the analytic panels in the Analytics section for this purpose.

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

  • Dashboard (Old Dashboard) allows you to download reports in CSV format by using the tools in the Reports section. You can perform export as a one-time or regular download of data to your local computer.
  • 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 means of sending requests to the /operations/get endpoint.

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