Decline reasons
The list of possible codes is expanding. We are working to reduce the number of non-detailed declines.
| decline_reason value | Description |
|---|---|
| 100:general decline | Decline without detailed reason |
| 200:Not paid | Customer not paid in desired time |
| 200:Invalid customer data | Customer’s data not passed internal validation |
| 200:Customer reject to pay | Customer press “reject” on checkout page |
| 300:Channel is temporally unavailable | Payment channel disabled or issuing downtime |
| 300:Channel is temporally overloaded | The payment channel is receiving more requests than it can handle in-moment |
| 300:Channel general decline | Payment channel declines payment without detailed reason |
| 300:Channel reports invalid data | Customer’s data not passed in-channel validation |
| 300:Channel depleted | Channel was overloaded and issuing downtime |
| 900:No channel available | No active payment channel connected to you account |
| 900:Blocked by FRAUD-prevention system: count | FRAUD-prevention system blocks payment attempt because some customer`s count is high (for example: to much declined payments of the customer in short time) |
| 900:Blocked by FRAUD-prevention system: blacklist | FRAUD-prevention system blocks payment attempt because some customer is blacklisted |
| 900:Insufficient balance | Insufficient merchant balance |
| 900:Temporally system malfunction | Our system got internal fail with unexpected reason |
Network error 500 it isn't the reason for final status. Such an operation needs recheck status or contact technical support.