# 11.2. BLIK in the sandbox environment. To test BLIK transactions, use the following data. | Code | Behavior | |---------------|-----------------------------------------------| | 777000 | Completed | # Testing asynchronous errors The Axepta API enables you to test Blik payments by simulating asynchronous errors through the use of the amount, title, and blikCode parameters. # Throwing asynchronous errors using `blikCode` Here’s a table representation of the provided Blik codes and their statuses: | blikCode | Status | Status Code | |-----------|-----------------------------------|----------------------| | 999000 | SETTLED | | | 912111 | REJECTED | ALIAS_DECLINED | | 927111 | REJECTED | TAS_DECLINED | | 934111 | REJECTED | USER_DECLINED | | 969111 | REJECTED | SEC_DECLINED | | 956111 | REJECTED | SYSTEM_ERROR | | 961111 | REJECTED | GENERAL_ERROR | | 960111 | REJECTED | INSUFFICIENT_FUNDS | | 989111 | REJECTED | TIMEOUT | | 990111 | REJECTED | LIMIT_EXCEEDED | | 949111 | REJECTED | USER_TIMEOUT | | 902111 | REJECTED | ISSUER_DECLINED | - Important note! >Despite the transaction status being set to "Rejected", an additional asynchronous notification is sent at the end of the transaction process. This notification includes the relevant `StatusCode`. #Throwing asynchronous errors using `amount` Here’s a table representation of the provided amount values and their statuses. For testing errors with amounts, you should use the blikCode: 777 xxx (where xxx can be any digits). | amount | Status | Status Code | |-----------|---------------------------------|----------------------| | 28800 | REJECTED | ALIAS_DECLINED | | 19200 | REJECTED | TAS_DECLINED | | 14400 | REJECTED | USER_DECLINED | | 21600 | REJECTED | SEC_DECLINED | | 26400 | REJECTED | SYSTEM_ERROR | | 36000 | REJECTED | GENERAL_ERROR | | 12000 | REJECTED | INSUFFICIENT_FUNDS | | 31200 | REJECTED | TIMEOUT | | 9600 | REJECTED | LIMIT_EXCEEDED | | 33600 | REJECTED | USER_TIMEOUT | | 16800 | REJECTED | ISSUER_DECLINED | #Testing synchronous errors The Axepta API enables you to test Blik payments by simulating synchronous errors through the use of the blikCode value. #Throwing synchronous errors using blikCode Here’s a table representation of the provided blikCode values and transaction statuses: | blikCode | Status | Status Code | |-----------|---------------------------------|----------------------| | 123444 | REJECTED | ER_WRONG_TICKET |