Kassa24 Terminal

Overview

Kassa24 Terminal is payment method to perform purchases via terminals by cash.

General information

Payment method type Terminals
Countries and regions KZ
Payment currencies KZT or USD*
Currency conversion on the provider side
Purchases +
Payouts
Stored credentials payments
Full refunds
Partial refunds
Chargebacks
Notes
Onboarding and access fee Refer to your key account manager ECommPay

* The customer can select any currency available in the terminal. On the provider side, all purchases are converted to USD and the payment platform and the web service use only USD. Refer to your ECommPay account manager for information about availability of payments in USD.

Interaction diagram

Payment processing by using the Kassa24 Terminal payment method requires merchant's web service, one of ECommPay interfaces, and the ECommPay payment platform, as well as Kassa24 Terminal service.

Operations support

  Interfaces Amounts, KZT Times*
Payment Page CMS Plug-ins Gate Dashboard (Old Dashboard) minimum maximum basic threshold
Purchases + 1 minute 36 days
* The basic and threshold times are defined as follows:
  • The basic time is the average estimated time between the moment a payment is initiated in the payment platform to the moment the payment result is sent to the initiator. The basic time evaluation is made on the assumption of normal operation of all technical facilities and communication channels and typical customer behaviour (if any input from customer is required). Use the basic time to estimate when to react to the absence of payment result notifications or when to check payment status.
  • The threshold time is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the initiator receives the callback with the payment result. A payment is automatically declined, if its waiting time exceeds the threshold time. For individual setting of the threshold time limit, contact ECommPay technical support.

Processing scenarios

In the Kassa24 Terminal method to perform a purchase operation customer needs to pay by cash in terminal.

Figure: Purchase by using Gate procedure diagram



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

Purchase by using Gate

General information

In the Kassa24 Terminal method, when processing a purchase by using Gate, the merchant web service is required to do the following:

  1. Process request for checking customer account existence.
  2. Send information about customer account existence.
  3. Process request for receiving payment identifier on the web service side.
  4. Send payment identifier.
  5. 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 sequence by using Gate via terminal

  1. Customer selects a web service, the personal account in which he wants to replenish, and then enters his credentials in the merchant system.
  2. The terminal sends request for checking customer account existence to the specified ECommPay URL.
  3. The payment platform performs the initial request processing that includes validation of the required parameters and signature.
  4. The payment platform sends request for checking customer account existence to the web service.
  5. The request is processed on the web service side.
  6. The web service sends response to the request.
  7. The payment platform sends customer account data to the Kassa24 Terminal service.
  8. The Kassa24 Terminal payment form is displayed to the customer.
  9. The customers pays by cash to replenish personal account.
  10. The payment is processed on the Kassa24 Terminal side.
  11. The Kassa24 Terminal service sends the payment result notification to the payment platform.
  12. The payment platform sends request to the web service for payment identifier on the web service side.
  13. The request is processed on the web service side.
  14. The web service sends payment identifier to the payment platform.
  15. Operation is created on the payment platform side.
  16. The payment platform sends the callback to the web service.
  17. The customer receives the payment result on the terminal display.

The sections that follow discuss in more details the request format and the Gate parameters to use in the Kassa24 Terminal 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 requests for checking account existence in the Kassa24 Terminal method:

  1. The verify request for checking account existence is sent by using HTTP method POST to the specified web service URL.
  2. The request contains the following required parameters:
    • action—operation type on the web service side, value is always verify
    • site_login—customer identifier on the web service side
    • site_id—the project ID obtained from ECommPay
    • siganture—signature created after you specify all the required parameters

    Figure: Example of a request for checking account existence

     {
        "action": "verify",   
        "site_id": "1487",
        "site_login": "123456789",
        "signature": "e19695449545fac562843ca06e7e0f3e51281ad6"
    }
  3. Response to the verify request must be synchronously sent and contain the following required parameters:
    • code—response code
    • currency—currency in the ISO-4217 alpha-3 format

    Figure: Example of the response

    {
        "code": 0,
        "error_description": "",
        "currency": "KZT"
    }

There are several things you must consider when using requests for payment identifier on the web service side:

  1. The check_deposit request for payment identifier is sent by using HTTP method POST to the specified web service URL.
  2. The request contains the following required parameters:
    • action—operation type on the web service side, value is always check_deposit
    • site_login—customer identifier on the web service side
    • site_id—the project ID obtained from ECommPay
    • amount—purchase amount in minor units
    • currency—currency in the ISO-4217 alpha-3 format
    • payment_group_id—payment method name, value is always kassa24;
    • signature—signature created after you specify all the required parameters

    Figure: Example of a request for payment identifier

    {
        "action": "check_deposit",   
        "site_id": "1487",
        "site_login": "123456789",
        "signature": "e19695449545fac562843ca06e7e0f3e51281ad6",
        "amount": "10000",
        "currency": "KZT",
        "payment_group_id":"kassa24"
    }
  3. Response to the check_deposit request must be synchronously sent and contain the following required parameters:
    • code—response code
    • external_id—payment ID unique within the project

    Figure: Example of the response

    {
        "code": 0,
        "external_id": "12365",
        "description": "sale"
    }

Callback format

The Kassa24 Terminal 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 KZT purchase in the 2275 project.

Figure: Example of a successful purchase callback

{
        "project_id": 2275,
        "customer": {
            "id": "4444"
        },
        "payment": {
            "id": "1549267511",
            "type": "purchase",
            "status": "success",
            "date": "2019-02-04T08:05:17+0000",
            "method": "kassa24",
            "sum": {
                "amount": 10000,
                "currency": "KZT"
            },
            "is_new_attempts_available": false,
            "attempts_timeout": 0,
            "description": ""
        },
        "customer_data": {
            "ip_address": "192.168.15.15"
        },
        "merchant_account_id": 2275,
        "operation": {
            "id": 8,
            "type": "sale",
            "status": "success",
            "date": "2019-02-04T08:05:17+0000",
            "created_date": "2019-02-04T08:05:13+0000",
            "request_id": "c4e54119785dd37f1883fb82102f9f585d6be2ff25d8d79c41e8",
            "sum_initial": {
                "amount": 10000,
                "currency": "KZT"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "KZT"
            },
            "provider": {
                "id": 2275,
                "payment_id": "1549267510",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "nOAt011EDZ9uw8JindTcrZnOr7F5M2ZObxBAqUPjHUv/L3A
                           jYNOdKvF9tFOER6QH/5L7e0d4Q8y8nCUs/2YqDA=="
    }

Related topics

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

Analysis of payments results

As with other payment methods ECommPay offers, when using the Kassa24 Terminal 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.