Purchase

When performing a purchase, the customer follows the payment instructions displayed on the checkout page or in your system (when performing the purchase by using Gate).

Countries and regions Russian Federation
Payment currencies RUB
Payment amount limits Contact your key account manager at Monetix for details. Also you can check the payment amount limits in your project by using Dashboard.
Payment processing time Contact your key account manager at Monetix for details.
Currency conversion On the Monetix side
Refund
Onboarding and access fee Contact your key account manager at Monetix for details.
Special considerations
  • The payment details have an expiration date. If the customer makes a payment after payment details are expired, the payment will be declined or assigned an intermediate status until the conflict is resolved manually by the Monetix technical support specialists.
  • The payment details must be used for purchase only once. The customer has to initiate a new purchase for performing future payments.
  • If the customer enters an amount which is different from the amount specified in the purchase request, the payment processing will proceed as described in Handling payments with amount changed by customer. Contact your key account manager at Monetix for more information.

Operations support

Interfaces
Payment Page Gate Dashboard
Purchase

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 then click the Payment methods tab.

The following sections provide more information about the payment processing flow and the analysis of completed payments.

Purchase by using Payment Page

General information

To perform a purchase by using Payment Page with the P2P transfers in Russia payment method:

  1. Send a request with all the required parameters and signature to the Monetix URL.
  2. Accept the callback with the purchase result from the payment platform.

The following figure shows the complete purchase processing flow in the P2P transfers in Russia payment method.

Figure 1. Purchase processing steps for a purchase by using Payment Page
  1. The customer initiates a purchase in your system.
  2. Your system sends the request for the purchase through Payment Page to the Monetix URL.
  3. The checkout page is displayed to the customer.
  4. The customer chooses to make a purchase with the P2P transfers in Russia payment method.
  5. The payment platform forwards the request to the provider service.
  6. The provider service generates the payment instructions to show to the customer and sends them to the payment platform.
  7. The checkout page displays the payment instructions to the customer.
  8. The customer completes the purchase.
  9. The provider service sends the purchase result information to the payment platform.
  10. The payment platform sends a callback with the payment result to your system.
  11. The payment platform displays the payment result to the customer on the checkout page.

Request

The following table lists the parameters that you need to include in the request for purchase through the checkout page with the P2P transfers in Russia payment method.

Table 1. Basic parameters of requests to Payment Page

strictly required—the parameter must be in the initial request.

optional—the parameter is optional but adding it to the request either makes the payment process more customer-friendly or helps to increase the percentage of successful payments.
ParameterDescription

project_id
integer
strictly required

Project ID you obtained from Monetix when integrating.

Example: 1234

payment_id
string
strictly required

Payment ID unique within your project.

Example: payment_47

customer_id
string
strictly required

Unique ID of the customer within your project.

Example: customer_123

customer_first_name
string
strictly required

Customer's first name.

Example: John

customer_last_name
string
strictly required

Customer's last name.

Example: Doe

customer_email
string
strictly required

Customer's email.

Example: johndoe@example.com

payment_currency
string
strictly required

Code of the payment currency in the ISO-4217 alpha-3 format.

Example: RUB

payment_amount
integer
strictly required

Payment amount in minor currency units without any decimal point or comma except for the cases when the currency doesn't have any minor currency units.

If the currency doesn't have any minor units (i.e. the number of digits for minor currency units is zero), set this parameter to the amount in the major currency units. To check whether the currency has any minor units, see Currency codes.

Example: 100.00 RUB must be sent as 10000

force_payment_method
string
optional

Parameter that allows you to enforce the P2P transfers in Russia payment method for your customer and skip the page with payment method selections.

To enforce the P2P transfers in Russia payment method and skip the page with payment method selection, add the force_payment_method parameter to the request and set its value to card-p2p. For more information about enforcing payment methods, see Preselecting payment methods.

Example: force_payment_method: 'card-p2p'

signature
string
strictly required

Signature created after you've specified all the request parameters. For more information about signature generation, see Signature generation and verification.
You can also add any other optional parameters to the request, if necessary. For the list of all the parameters possible in requests to Payment Page, see Payment Page invocation parameters.

Here is an example of the data from a request to open the checkout page by using EPayWidget:

EPayWidget.run(
	{
		project_id: 1234,
		payment_id: 'payment_47',
		customer_id: 'customer_123',
		customer_first_name: 'John',
		customer_last_name: 'Doe',
		customer_email: 'johndoe@example.com',
		payment_currency: 'RUB',
		payment_amount: 10000,
		force_payment_method: 'card-p2p',
		signature: 'kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y19vySO/RLUkDJrOcZzUCwX6R/ekpZhkIQg=='
	}
)

Callback

In the P2P transfers in Russia payment method, the payment platform returns the purchase result in a callback. For the information about the callback structure, see Callbacks in Payment Page.

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

Figure 2. Example of the data from a successful purchase callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "method": "card-p2p",
        "sum": {
            "amount": 10000,
            "currency": "RUB"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "sale",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 10000,
            "currency": "RUB"
        },
        "sum_converted": {
            "amount": 10000,
            "currency": "RUB"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

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

Figure 3. Example of the data from a declined purchase callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "method": "card-p2p",
        "sum": {
            "amount": 10000,
            "currency": "RUB"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "sale",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 10000,
            "currency": "RUB"
        },
        "sum_converted": {
            "amount": 10000,
            "currency": "RUB"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

Related topics

Purchase by using Gate

General information

To perform a purchase by using Gate with the P2P transfers in Russia payment method:

  1. Send a request with all the required parameters and signature to the Monetix URL.
  2. Show the screen with payment instructions to the customer.
  3. Accept the callback with the purchase result from the payment platform.

The following figure provides the details of the purchase processing flow in the P2P transfers in Russia payment method.

Figure 4. Purchase processing flow when performing a purchase by using Gate
  1. The customer initiates a purchase in your system.
  2. Your system sends the purchase request to the Monetix payment platform.
  3. The payment platform sends you a response in which it acknowledges your request and provides the request validation result. (For more information about the response format, see Response structure.)
  4. The payment platform processes the request and forwards it to the provider service.
  5. The provider service generates the payment instructions to show to the customer and sends them to the payment platform.
  6. The payment platform forwards the instructions to your system in the display_data array.
  7. Your system displays the payment instructions to the customer.
  8. The customer completes the purchase.
  9. The provider service informs the payment platform about the purchase result.
  10. The payment platform sends the callback with the payment result to your system.
  11. Your system sends the payment result to the customer.

Request

This section provides the instructions on how to build the request for purchase with the P2P transfers in Russia payment method.

HTTP request method POST
Request body format JSON
API endpoint /v2/payment/card-p2p/sale
Table 2. Basic parameters of a purchase request

strictly required—the parameter must be in the initial request.
ObjectParameterDescription

general
object
strictly required

project_id
integer
strictly required

Project ID you obtained from Monetix when integrating.

Example: 1234

payment_id
string
strictly required

Payment ID unique within your project.

Example: payment_47

signature
string
strictly required

Signature created after you've specified all the request parameters. For more information about signature generation, see Signature generation and verification.

customer
object
strictly required

id
string
strictly required

Unique ID of the customer within your project.

Example: customer_123

ip_address
string
strictly required

IP address of the customer's device.

Example: 198.51.100.47

first_name
string
strictly required

Customer's first name.

Example: John

last_name
string
strictly required

Customer's last name.

Example: Doe

email
string
strictly required

Customer's email.

Example: johndoe@example.com

account
object
strictly required

bank_id
integer
strictly required

Customer's bank ID. Pass this parameter in the request if your customer chooses a specific bank to make the purchase with. For possible values, see Supported payment options.

Example: 69492

payment
object
strictly required

currency
string
strictly required

Code of the payment currency in the ISO-4217 alpha-3 format.

Example: RUB

amount
integer
strictly required

Payment amount in minor currency units without any decimal point or comma except for the cases when the currency doesn't have any minor currency units.

If the currency doesn't have any minor units (i.e. the number of digits for minor currency units is zero), set this parameter to the amount in the major currency units. To check whether the currency has any minor units, see Currency codes.

Example: 100.00 RUB must be sent as 10000

by_method
string
strictly required

Code of the payment option your customer chooses to make the payment. Note that some of the payment options might be unavailbale. To get the current list of payment method options, contact your key account manager at Monetix or use the Gate API (for the information about building a request for available payment options, see Supported payment options).

Possible values:

  • card-p2p—if the customer chooses Transfer to card
  • sbp-p2p—if the customer chooses Transfer by phone number
  • sbp-qr—if the customer chooses Transfer by QR code
  • bank-transfer/russia—if the customer chooses Transfer by account number
  • one-click-p2p—if the customer chooses One Click

Example: card-p2p

You can also add any other optional parameters to the purchase request, if necessary. For the list of all the parameters available in Gate, see API Reference.

Here is an example of the data from a request to initiate a purchase with the P2P transfers in Russia payment method:

Figure 5. Example of the purchase request body
{
    "general": {
        "project_id": 1234,
        "payment_id": "payment_47",
        "signature": "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y19vySO/RLUkDJrOcZzUCwX6R/ekpZhkIQg=="
    },
    "customer": {
        "id": "customer_123",
        "ip_address": "198.51.100.47",
        "first_name": "John",
        "last_name": "Doe",
        "email": "johndoe@example.com"
    },
    "account": {
        "bank_id": 69492
    },
    "payment": {
        "currency": "RUB",
        "amount": 10000,
        "by_method": "card-p2p"
    }
}

Displaying the payment instructions to the customer

After receiving and processing your purchase request, the payment platform sends you the callback with the data for displaying the payment instructions to the customer.

Use the data from the display_data array to display the payment instructions to the customer.

Table 3. Description of the display_data array.
ElementDescription
{ 
	"type": "add_info", 
	"title": "receiver_name", 
	"data": "Mark Doe" 
}
 Payment recipient's full name.

Example: Mark Doe

 
{ 
	"type": "add_info", 
	"title": "receiver_account", 
	"data": "1234567890123456" 
}
 Payment recipient's card number.

Example: 1234567890123456

 
{ 
	"type": "add_info", 
	"title": "bank_name", 
	"data": "Sberbank" 
}
 Payment recipient's bank name.

Example: Sberbank

 
{ 
	"type": "add_info", 
	"title": "bank_bic", 
	"data": "123456789" 
}
 Payment recipient's bank RCBIC (Russian Central Bank Identification Code).

Example: 123456789

 
{ 
	"type": "add_info", 
	"title": "amount", 
	"data": 10000 
}
 Purchase amount in minor currency units without any decimal point or comma.

Sometimes it is impossible to perform purchase for the amount specified in the request due to technical issues on the provider side. In such cases, the Monetix payment platform can send you several available amounts in the display_data array instead of declining the payment. The available amounts are separated by a semicolon.

{ 
	"type": "add_info", 
	"title": "amount", 
	"data": "10100;9900" 
}

You should allow the user to select one of the proposed new amounts. After that, the customer receives a notification with the changed amount (for more information, see Handling payments with amount changed by customer).

To enable this feature, please contact your Monetix key account manager.

Example: 10000

{ 
	"type": "add_info", 
	"title": "currency", 
	"data": "RUB" 
}
 Code of the purchase currency in the ISO-4217 alpha-3 format.

Example: RUB

 
{ 
	"type": "add_info", 
	"title": "lifetime", 
	"data": 480 
}
 Lifetime of the payment instructions (in seconds).

Example: 480

 
{ 
	"type": "add_info", 
	"title": "qr_data", 
	"data": "https://example.com/qr" 
}
 Link to the QR code for payment.

Example: https://example.com/qr

 
{ 
	 "type": "add_info", 
	 "title": "deep_link", 
	 "data": "https://example.com/page/pdl/example" 
}
Link for opening the page with the redirect to the provider app for payment.

Example: https://example.com/page/pdl/example

Here is an example of the callback snippet with the data for displaying the payment instructions to the customer.

"display_data": [
	{
		"type": "add_info", 
		"title": "receiver_name", 
		"data": "Mark Doe" 
	}, 
	{ 
		"type": "add_info", 
		"title": "receiver_account", 
		"data": "1234567890123456" 
	}, 
	{ 
		"type": "add_info", 
		"title": "bank_name", 
		"data": "Sberbank" 
	}, 
	{ 
		"type": "add_info", 
		"title": "bank_bic", 
		"data": "123456789" 
	}, 
	{ 
		"type": "add_info", 
		"title": "amount", 
		"data": 10000 
	}, 
	{ 
		"type": "add_info", 
		"title": "currency", 
		"data": "RUB" 
	}, 
	{ 
		"type": "add_info", 
		"title": "lifetime", 
		"data": 480 
	}, 
	{ 
		"type": "add_info", 
		"title": "qr_data", 
		"data": "https://example.com/qr" 
	} 
]

Here is an example of the callback snippet with the data for displaying the page with redirect to the customer.

"display_data": [
	{
		"type": "add_info", 
		"title": "receiver_name", 
		"data": "Mark Doe" 
	}, 
	{ 
		"type": "add_info", 
		"title": "receiver_account", 
		"data": "1234567890123456" 
	}, 
	{ 
		"type": "add_info", 
		"title": "bank_name", 
		"data": "Sberbank" 
	}, 
	{ 
		"type": "add_info", 
		"title": "bank_bic", 
		"data": "123456789" 
	}, 
	{ 
		"type": "add_info", 
		"title": "amount", 
		"data": 10000 
	}, 
	{ 
		"type": "add_info", 
		"title": "currency", 
		"data": "RUB" 
	}, 
	{ 
		"type": "add_info", 
		"title": "lifetime", 
		"data": 480 
	}, 
	{ 
		"type": "add_info", 
		"title": "deep_link", 
		"data": "https://example.com/page/pdl/example" 
	} 
]
Note: There are some specifics concerning the payment instructions display:
  • The structure of the display_data array depends on the value you submit in the payment.by_method parameter of your purchase request. The example above contains all the possible elements the payment platform may send in callbacks to your system. Note that when performing payments, you'll receive callbacks with only some of the elements of the display_data array given in the article.
  • The payment details should be displayed to the customer only while it is valid (within its lifetime). The payment details should be hidden after the period of its validity is expired.

Supported payment options

When performing a purchase by using Gate with the P2P transfers in Russia payment method, your system should request that the customer choose their preferable payment option and then it should send the code of this payment option and the ID of your customer's bank (if necessary) to the payment platform in the request.

The table below lists the payment options available for purchase in the P2P transfers in Russia payment method.

Table 4. Supported payment options
Transfer to cardTransfer by phone numberTransfer by QR codeTransfer by account numberOne Click
Sberbank
T-Bank
VTB
Other bank
Faster Payments System

If the customer chooses a particular bank in your system, pass the ID of this bank in your purchase request to the payment platform. If the customer chooses Other bank or Faster Payments System options, there is no need to submit an ID of a bank.

The table below lists the banks available for purchase in the P2P transfers in Russia payment method.

Table 5. Banks available for purchase
Bank ID
Alfa-Bank 75232
Gazprombank 55171
Promsvyazbank 65311
Russian Agricultural Bank 64311
SberBank 69492
T-Bank 69502
VTB 55151

The tables with available payment options and the list of banks are provided for informational purposes only. They may change without notice. To get the current list of payment options and banks the P2P transfers in Russia payment method supports, send a request to the payment platform.

The request format and structure should be the following:

HTTP request method POST
Request body format JSON
API endpoint /v2/info/available_p2p_method_list
Table 6. Parameters required in the request to get the list of payment options and banks available in the payment method

strictly required—parameter is required in the initial request.
Object Parameter Description

general
object
strictly required

project_id
integer
strictly required

 Project ID you obtained when integrating with Monetix.

Example: 123

payment_id
string
strictly required

 Payment ID unique within the project.

If the payment is not yet created, set this parameter to a unique value.

Example: payment_47

signature
string
strictly required

 Signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification.

payment
object
strictly required

amount
integer
strictly required

 Payment amount in minor currency units without any decimal point or comma except for the cases when the currency doesn't have any minor currency units.

If the currency doesn't have any minor units (i.e. the number of digits for minor currency units is zero), set this parameter to the amount in the major currency units. To check whether the currency has any minor units, see Currency codes.

Example: 100.00 RUB must be sent as 10000

currency
string
strictly required

 Code of the purchase currency in the ISO-4217 alpha-3 format.

Example: RUB
You can also add any other optional parameters to the request, if necessary. For the list of all the parameters available in Gate, see API Reference.

Here is an example of the data from the request for the list of payment options and banks available in the P2P transfers in Russia payment method.

Figure 6. Example of the data from a request for the list of supported payment options and banks
{
	"general": {
	    "project_id": 200, 
	    "payment_id": "ORDER_155860015", 
	    "signature": "K6jllym+PtObocZtr345st...=="
	},   
	"payment": { 
	    "amount": 1500, 
	    "currency": "RUB"
	}
}

Here is an example of the data from a response with the list of supported payment options and banks.

Note: The list of parameters in the elements of arrays may change. The absence of data about supported banks in the array means there aren't any supported banks for this payment option and there is no need to submit the ID of the bank in the request.
Figure 7. Example of the data from a response with the list of supported payment options and banks
[ // Array with infrormation about supported payment options   
  { // Element containing information about one payment option 
    "card-p2p": [ // Array with infrormation about supported banks for a specific payment option   
      {
        "id": 69492, // Bank ID 
        "abbr": "SBR", // Bank shortcut name (for internal use) 
        "name": "Sberbank", // General bank name 
        "nativeName": "Сбербанк", // Native bank name 
        "currencies": [ // Array with currencies supported by the bank   
          {
            "id": 643, // Currency ID in the payment platform 
            "alpha_3_4217": "RUB", // Alphabetic code of payment currency in ISO-4217 alpha-3 format 
            "number_3_4217": "643", // Numeric code of payment currency in ISO-4217 alpha-3 format 
            "exponent": 2 // Number of decimal places after decimal point   
          } 
        ]   
      },   
      {
        "id": 69502, 
        "abbr": "TBANK", 
        "name": "T-Bank", 
        "nativeName": "Т-Банк", 
        "currencies": [   
          { 
            "id": 643, 
            "alpha_3_4217": "RUB", 
            "number_3_4217": "643", 
            "exponent": 2   
          } 
        ]   
      } 
    ]   
  },   
  { 
    "sbp-p2p": [] // The absence of data about supported banks in the array means   
  }              // there aren't any supported banks for this payment option 
]               // and there is no need to submit the ID of the bank in the request

Callback

In the P2P transfers in Russia 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 8. Example of the data from a successful purchase callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "method": "card-p2p",
        "sum": {
            "amount": 10000,
            "currency": "RUB"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "sale",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 10000,
            "currency": "RUB"
        },
        "sum_converted": {
            "amount": 10000,
            "currency": "RUB"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

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

Figure 9. Example of the data from a declined purchase callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "method": "card-p2p",
        "sum": {
            "amount": 10000,
            "currency": "RUB"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "sale",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 10000,
            "currency": "RUB"
        },
        "sum_converted": {
            "amount": 10000,
            "currency": "RUB"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

Related topics