Cash-in Kazakhstan

Overview

Cash-in Kazakhstan is payment method to perform purchases via terminals in Kazakhstan.

Payment method type Terminal
Countries and regions Kazakhstan
Payment currencies KZT
Currency conversion On the provider side
Purchases
Payouts
COF payments
Full refunds
Partial refunds
Chargebacks
Notes
  • Purchases via terminals are performed with cash
  • Provider limits monthly payment amount within 12,500,000.00 KZT
Onboarding and access fee Refer to your key account manager at Monetix

Operations support

Interfaces Payment amounts, KZT Times
Payment Page Gate Dashboard minimum maximum basic threshold
Purchases 1.00 500,000.00 * *

* For more information, refer to your Monetix key account manager.

You can check the payment amount limits in your project by using Dashboard. To check your payment amount limits, go to Dashboard, select the Projects section and click the Payment methods tab.

Processing scenarios

In the Cash-in Kazakhstan method to perform a purchase operation customer needs to pay by cash in terminal.

Figure 1. Purchase by using Gate procedure diagram

Purchase by using Gate

General information

In the Cash-in Kazakhstan 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 2. 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 Monetix 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 Cash-in Kazakhstan service.
  8. The Cash-in Kazakhstan payment form is displayed to the customer.
  9. The customers pays by cash to replenish personal account.
  10. The payment is processed on the Cash-in Kazakhstan side.
  11. The Cash-in Kazakhstan 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 Cash-in Kazakhstan payment method and provide the information on the format of callbacks with purchase results.

Requests

Request verify for checking account existence

  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:
    • type—operation type on the web service side, value is always verify
    • customer_id—customer identifier on the web service side
    • project_id—the project ID obtained from Monetix
    • signature—signature created after you specify all the required parameters
    Figure 3. Example of a request for checking account existence
    {
        "type": "verify",
        "project_id": 1234,
        "customer_id": "johndoe@example.com",
        "signature": "lY0LTSAz85R7zGce5qfYGacOuYlHGWqkMcQlqUmkQ0YYLWRg=="
    }

Request check_deposit for payment identifier

  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:
    • type—operation type on the web service side, value is always verify
    • customer_id—customer identifier on the web service side
    • project_id—the project ID obtained from Monetix
    • amount—purchase amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency have no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
    • currency—currency in the ISO-4217 alpha-3 format
    • payment_method—terminal name, value is always kassa24
    • signature—signature created after you specify all the required parameters
    Figure 4. Example of a request for payment identifier
    {
        "type": "check_deposit",
        "project_id": 1234,
        "customer_id": "johndoe@example.com",
        "amount": 10000,
        "currency": "KZT",
        "payment_method": "kassa24",
        "signature":"lY0LTSAzpR7zGce5qfYGacOuYlHGWqkMcmkQ0YYLWRg=="
    }

Responses

Response format for the verify request

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 5. Example of the response
{
    "code": 0,
    "currency": "KZT",
    "additional_customer_id": "HFVDW42345"
}

Response format for the check_deposit request

Response to the check_deposit request must be sent by using HTTP method POST and contain the following required parameters:

  • code—response code
  • payment_id—payment ID unique within the project
Table 1. Allowed response codes
Code Description
0 Successful operation
400 Signature is invalid
404 Account does not exist
500 General error. The reason should be specified in the errors.message parameter
Figure 6. Example of the response
{
    "code": 0,
    "payment_id": "test2345",
    "description": "test payment via terminal"
}

Callback

In the Cash-in Kazakhstan payment method, the payment platform returns the purchase result in a callback. For the information about the callback structure, see Callbacks in Gate.

The following is an example of a callback body with the information about a successfully completed purchase.

Figure 7. Example of the data from a successful purchase callback
{
    "project_id": 1234,
    "payment": {
        "id": "1556624104",
        "type": "purchase",
        "status": "success",
        "date": "2024-04-30T11:35:06+0000",
        "method": "kassa24",
        "sum": {
            "amount": 10000,
            "currency": "KZT"
        },
        "description": ""
    },
    "account": {
        "number": "6552"
    },
    "operation": {
        "id": 36011000001676,
        "type": "sale",
        "status": "success",
        "date": "2024-04-30T11:35:06+0000",
        "created_date": "2024-04-30T11:35:05+0000",
        "request_id": "cea199572b36a148f0c20d105b0ee0abf737e06e512e8",
        "sum_initial": {
            "amount": 10000,
            "currency": "KZT"
        },
        "sum_converted": {
            "amount": 10000,
            "currency": "KZT"
        },
        "provider": {
            "id": 1217,
            "payment_id": "2024290410",
            "auth_code": ""
        },
        "code": "0",
        "message": "Success"
    },
    "signature": "jvqLGHIaGdHeF68GtTxAtVFCGzkLxOCFU1crar0RmQpLy8Yw=="
}

Related topics

Analysis of payments results

As with other payment methods Monetix offers, when using this method, you have several options to analyze the information about payments and operations.

You can load and analyze all the necessary information in Dashboard (dash-light.trxhost.com), 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 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 Monetix technical support.