CALLBACKS
Example of a callback notification
POST
JSON Request Params
id
string
Transaction ID on the BOVA side
merchant_id
string
Your transaction number
status
string
Transaction status
message
string
Rejection reason text for the request, with or without a dispute.
Possible reasons for request rejection:
1) Transaction cancellation without dispute, reasons:
declined by timeout— payment timeout exceededdeclined by anti fraud— cancelled by anti-fraud systemdeclined by user— cancelled by the user on the form or via API
2) Transaction cancellation with dispute, reasons:
payment not found— payment was not foundfake proof— fake receipt (mostly applies to PDFs)invalid proof datetime— receipt date does not match the requestinvalid proof requisites— incorrect payment detailsbank account blocked— bank account is blocked, review period extended
currency
string
Transaction currency
payment_method
string
Payment method
amount
decimal
Transaction amount in USDT after conversion at the exchange rate
fiat_amount
decimal
Actual credited amount in the transaction currency upon successful completion
old_fiat_amount
decimal
Transaction amount specified at creation in the specified currency (immutable)
rate
decimal
Conversion rate currency/USDT
service_commission
decimal
Merchant commission percentage
reсipient_card_number_type
string
sberpay
Headers
Content-Type
string
Always application/json
Signature
string
Signature of the request, generated using your api_key to identify the callback notification as sent by us.
You must compare the signature with your own — they must match.
Example Request:
Status description:
successed
final
Successfully credited
accepted_successed
final
Successfully completed after dispute confirmation
repeated_accepted_successed
final
Successfully completed after repeated dispute confirmation
failed
final
Rejected due to timeout, credit not found
closed_failed
final
Rejected after dispute was denied
repeated_closed_failed
final
Rejected after repeated dispute was denied
Last updated