Additional deposits callbacks
In cases where deposits from the user are found on the Cactus platform (for example, if a deposit is made twice for one invoice)
In these instances, Cactus operators will create an invoice of their own, and a callback (described below) will inform the merchant about the additional deposit
Callbacks parameters
is_payout
No
bool
whether the transaction is a payment
false
site_login
Yes
string
User login on the merchant's website
test_login
invoice_id
Yes
int
Unique id in the cactus system
905910
method
Yes
string
Type of method used in the invoice
card
amount
Yes
int
Transaction amount in order currency in minor units, for example for US dollars - in cents
10000
description
Yes
string
Description of cases of exceptions. The value is empty if the response is successful
Manual created payment
site_id
Yes
int
Site ID
123
signature
Yes
string
f4eb33161e94aa8d816a9d053e7008f6ae9237c
status
Yes
Enum
Operation status
4
received_amount
Yes
int
Final payment amount (if payment is unsuccessful, returns 0) minor units
10000
received_currency
Yes
string
Currency in which the payment will be made
KZT
currency
Yes
string
Currency
KZT
Example of success response
Description in exceptional cases
Payout Invoice status set to Success by user {user}
The Cactus operator ({user}) has manually set the status of the payout invoice to 'Success'
Manual created payment
The Cactus operator has manually made an invoice for the lost accrual
Last updated