SBP Sale Request Parameters

Parameter Name	Description	Value
client_orderid	Unique order identifier assigned by Connecting Party.	Necessity: Required Type: String Length: 128
order_desc	Brief order description.	Necessity: Required Type: String Length: 64k
amount	Amount to be charged. The amount has to be specified in the highest units with . delimiter. For instance, 10.5 for USD means 10 US Dollars and 50 Cents.	Necessity: Required Type: Numeric Length: 10
currency	Currency the transaction is charged in (See: Currency codes). Sample values are: USD for US Dollar EUR for European Euro.	Necessity: Required Type: String Length: 3
address1	Payer’s address line 1.	Necessity: Required Type: String Length: 50
city	Payer’s city.	Necessity: Required Type: String Length: 50
zip_code	Payer’s ZIP code.	Necessity: Required Type: String Length: 10
country	Payer’s country. Please see Country codes for a list of valid country codes.	Necessity: Required Type: String Length: 2
phone	Payer’s full international phone number, including country code.	Necessity: Required Type: String Length: 15
email	Payer’s e-mail address.	Necessity: Required Type: String Length: 50
ipaddress	Payer’s IP address, included for fraud screening purposes.	Necessity: Required Type: String Length: 45
control	Checksum generated by SHA-1. Control string is represented as concatenation of the following parameters: 1. <ENDPOINTID | ENDPOINTGROUPID> (See: Request URL) 2. Request parameter: client_orderid 3. Request parameter: amount (in minor units) 4. Request parameter: email 5. merchant_control (Control key assigned to Connecting Party account in the Payneteasy gateway system).	Necessity: Required Type: String Length: 40
redirect_url	URL, where the Payer is redirected to upon completion of the transaction. Please note that redirection is performed in any case, no matter whether transaction is approved, declined in any other final status. Connecting Party must not use the parameters come along with the redirect HTTP Request to treat the status of the transaction. Instead Connecting Party can utilize server_callback_url or status API command. Pass http://https://doc.payneteasy.com if you have no need to return payer anywhere. Use either redirect_url or combination of redirect_success_url and redirect_fail_url, not both.	Necessity: Optional Type: String Length: 1024
cell_phone	Payer’s full international cell phone number, including country code.	Necessity: Optional Type: String Length: 15
site_url	The URL of the E-commerce entity, where the payment is originated from.	Necessity: Optional Type: String Length: 128
purpose	Destination to where the payment goes. It is useful for the Connecting Party’s who let their payers to top up their accounts with bank card (Mobile phone accounts, game accounts etc.). Sample values are: +7123456789; gamer0001@ereality.com etc. This value can be used by the fraud monitoring system.	Necessity: Optional Type: String Length: 128
server_callback_url	URL, where the transaction status is sent to. Connecting Party may use server callback URL for custom processing of the transaction completion, e.g. to collect payment data in the Connecting Party’s information system. For the list of parameters which come along with server callback to server_callback_url refer to Connecting Party callback parameters.	Necessity: Optional Type: String Length: 1024
merchant_data	Custom Connecting Party details, which can be attached to the transaction and passed back in the status response, Connecting Party callback parameters or server_callback_url. Additional information of transaction which may be useful in Connecting Party’s external system, e.g. VIP customer, TV promo campaign lead. Information returns in Status response and Connecting Party Callback.	Necessity: Optional Type: String Length: 64k
dapi_imei	Unique device identifier.	Necessity: Optional Type: String Length: 32