Payment processing

User choose operation type and payment method. Depends on the selected operation type, Cashier will send request to the gaming server: check_deposit or request_payout.

Deposit possibility check (check_deposit)

Request is sent by the Cashier to the gaming server (Merchant).

Parameter	Format	Mandatory	Description	Example
action	varchar(64)	Yes	Strong: check_deposit	check_deposit
site_id	integer	Yes	Your site_id	332
site_login	varchar(128)	Yes	Login of the user making the payment	user_test
amount	integer	Yes	Amount to be paid in minor units, e.g. for USD - in cents. Mandatory parameter in a new order.	10000
currency	string(3) (ISO 4217)	Yes	Operation currency	USD
payment_group_id	integer	Yes	Payment group identifier	6
payment_type_id	integer	Yes	Payment type identifier	18
signature	SHA-1	Yes	Request signature, see Request signature generating rules	d9f5713990de5c6e32169dba1f0102f540018975
customer_purse	string	No	User's wallet/account identifier in the payment system.	555555...4444
customer_ip	inet (ipv4 or ipv6)	No	User's IP in the ipv4 or ipv6 format	127.0.0.1
source_type	integer	No	Client interface type	4
transaction_id	string	No	Internal transaction identifier.	1234567890
merchant_purse	string	No	Merchant's wallet/account identifier in the payment system.	0x12312412541251

To the request check_deposit your server should respond to the Cashier - approve or decline payment, according to the Error codes:

Respond code	Description
0	This amount can be deposited, payment must be made by the order external_id
500	Error, description is in the error_description field

Your server’s response to the Cashier must be in the JSON format:

Parameter	Format	Description	Example
code	integer	Respond code from the above mentioned list	0
external_id	varchar(256)	Unique order number, by which payment will be processed. Mandatory for the code = 0	order_123456
error_description	varchar(1024)	Error description in the message (Code 500 description)	User not found

Pay-out possibility check (request_payout)

Request is sent by the Cashier to the Merchant's server.

Parameter	Format	Mandatory	Description	Example
action	varchar(64)	Yes	Strong: request_payout	request_payout
site_id	integer	Yes	Your site_id	332
site_login	varchar(128)	Yes	User’s login	user_test
amount	integer	Yes	Amount to be paid in minor units, e.g. for USD - in cents. Mandatory parameter in a new order.	10000
currency	string(3) (ISO 4217)	Yes	Operation currency	GBP
payment_group_id	integer	Yes	Payment group identifier	6
customer_purse	string	Yes	User's wallet/account identifier in the payment system.	555555...4444
remember_customer_purse	bool	Yes	A sign to save user's wallet/account number for further instant payment. Possible values: 0 - not to save, 1 - to save	0
signature	SHA-1	Yes	Request signature, see Request signature forming rules	d9f5713990de5c6e32169dba1f0102f540018975
payment_type_id	integer	No	Payment type identifier	18
customer_ip	inet (ipv4 or ipv6)	No	User's IP in the ipv4 or ipv6 format	127.0.0.1
transaction_id	string	No	Internal transaction identifier..	1234567890

To the request_payout Your server should respond to the Cashier - approve or decline pay-out, according to the codes:

Respond code	Description
50	Withdrawal will carried out by the Merchant's manager after processing
402	Insufficient funds
500	Error, error's description in the error_description field

Successful withdrawal request confirmed by response code - 50

Your server’s respond should be in JSON format:

Parameter	Format	Description	Example
code	integer	Respond code from the above mentioned list	50
external_id	varchar(256)	Unique order number, by which payment will be processed. Mandatory for the code = 50	order_123456
error_description	varchar(1024)	Error description in the message (Code 500 description)	User not found