Praxis Wiki logo

Agent API {payout-split}

Split Payout is a way to process the customer's payout request in several payouts having the smaller amounts.

{danger.fa-exclamation} IMPORTANT #1: Split payout is not compatible with some PSPs.

{danger.fa-exclamation} IMPORTANT #2: Split payout creates a new payout request having the same payment method and using the same customer's payment details.


Name URL


Variable Type Description
merchant_id varchar(50) Required. Merchant API client account identifier
frontend varchar(50) Required. Frontend in which the payout has been requested and will be processed
amount int(20) Required. Payment amount in cents.
Please note: for certain currencies (see full list here) there is a fraction other than 100 cents per unit, this is important if you multiply by 100 to send the amount in cents
currency varchar(10) Required. Payment currency
gateway varchar(50) Required. Gateway (processor configuration) hash to be used for processing (available options can be seen at Admin service, for more details please contact [email protected] for root account access)
reference_id varchar(50) Required. Original transaction identifier from
order_id varchar(50) Required. Transaction identifier in your system
pp varchar(50) Required. Processor name to be used for processing (available options can be seen at BO in a dropdown list of processors. given during the final step - payout processing form submission)
timestamp int(11) Required. Request time. URL will be active during 1 min after this time
version varchar(3) Required. API version
signature varchar(96) Required. sha256-encoded representation of the concatenation of request parameters and secret


Variable Type Description
status int Required.
- 0 if the request was successful
- Negative integer if internal server/network error occurs
- Positive integer if application/logical error occurs
description varchar(256) Required. Accurate description of the result. Return the actual error for any exception as it helps to diagnose issues in production
trace_id int(11) Required. Transaction identifier in
transaction_id varchar(50) Required. Transaction identifier in PSP
transaction_status varchar(16) Required.
- pending - processing initiated, final response expected from PSP
- approved - processing was successful
- declined retry - processing failed and will be reattempted
- declined - processing failed
- cancelled - processing cancelled by the merchant or client
- pending async - customer action expected (3D Secure, etc.)
- requested - merchant action expected (approval)
payment_processor varchar(25) Required. Gateway doing the processing
error_code int(10) Optional. Error code for rejected transactions
error_details varchar(256) Optional. Error description for rejected transactions
version varchar(3) Required. API version
signature varchar(96) Required. sha384 HASH code of response (same algorithm as request signature)



For example below: Merchant Secret = "MerchantSecretKey"

curl -X POST \ \
-H 'Content-Type: application/json' \
-H 'cache-control: no-cache' \
-d '{
    "frontend":"Integration TEST USD",
    "gateway": "dM-4p5ZORnROeCnnLmm3fBO-WkghMNhr",

Response (OK)

    "error_details":"[TEST] Transaction status: approved",

Response (Declined)

    "error_details":"[TEST] Transaction status: declined",

Please refer to How to Build Signature for details on signing the request.

You are currently viewing version 3.3 Latest version here