Change Details

For each direct transactions, before making call to processor, we check if some of our blocking conditions should be applied. Here are the rules: - We maintain our own db of restricted CC's so every time some transaction end up with restricted code, we hash that CC and store it into our DB. In case of additional attempts with the same CC (no matter of user), we block such attempts (Code 670: Your credit card is blocked. Please try another card.) - We maintain our own list of [[ https://m1.dvipadmin.com/payment_bin_filters | blocked bins ]]. Transactions for those bins are blocked and we're returning proper error code as defined in blocked bin list. (Default Code: 616: Your credit card cannot be processed by our system. Please try another card.). Additional codes can be 650-657 depending of bin. - We also block Maestro cards per system according to [[ https://m1.dvipadmin.com/payment_bin_filters | this list ]]. (Code 618: Maestro card currently not supported, please try a Visa or Mastercard.) - In cases when there was NSF transaction within last hour, transaction for that CC will be blocked (Code: Code 617: Your credit card is temporary blocked by our system. Please try another card.) - For INR transactions, if there was previous failed transaction attempt with the same CC, we block any further attempt with that CC (Code: 670: Your credit card is blocked. Please try another card.). For each of rules above, "fake" transaction will be saved and on DGVIP admin those transactions will be marked as SKIPPED. There are also two blocking mechanism where we currently don't store "fake" transactions: - Each user is allowed max 5 failed transactions attempts per hour. In case of any additional attempt we return Code: 604 'Too many attempts') - Each user is allowed only one step down within 24 hours. In case of additional transaction attempt after failed step down, we return Code 604: Too many attempts).

For each direct transactions, before making call to processor, we check if some of our blocking conditions should be applied. Here are the rules: - We maintain our own db of restricted CC's so every time some transaction end up with restricted code, we hash that CC and store it into our DB. In case of additional attempts with the same CC (no matter of user), we block such attempts (Code 670: Your credit card is blocked. Please try another card.) - We maintain our own list of [[ https://m1.dvipadmin.com/payment_bin_filters | blocked bins ]]. Transactions for those bins are blocked and we're returning proper error code as defined in blocked bin list. (Default Code: 616: Your credit card cannot be processed by our system. Please try another card.). Additional codes can be 650-657 depending of bin. - We also block Maestro cards per system according to [[ https://m1.dvipadmin.com/payment_bin_filters | this list ]]. (Code 618: Maestro card currently not supported, please try a Visa or Mastercard.) - In cases when there was NSF transaction within last hour, transaction for that CC will be blocked unless the amount is lower than with previous NSF transaction (Code: Code 617: Your credit card is temporary blocked by our system. Please try another card.) - For INR transactions, if there was previous failed transaction attempt with the same CC, we block any further attempt with that CC (Code: 670: Your credit card is blocked. Please try another card.). For each of rules above, "fake" transaction will be saved and on DGVIP admin those transactions will be marked as SKIPPED. There are also two blocking mechanism where we currently don't store "fake" transactions: - Each user is allowed max 5 failed transactions attempts per hour. In case of any additional attempt we return Code: 604 'Too many attempts') - Each user is allowed only one step down within 24 hours. In case of additional transaction attempt after failed step down, we return Code 604: Too many attempts).

For each direct transactions, before making call to processor, we check if some of our blocking conditions should be applied. Here are the rules: - We maintain our own db of restricted CC's so every time some transaction end up with restricted code, we hash that CC and store it into our DB. In case of additional attempts with the same CC (no matter of user), we block such attempts (Code 670: Your credit card is blocked. Please try another card.) - We maintain our own list of [[ https://m1.dvipadmin.com/payment_bin_filters | blocked bins ]]. Transactions for those bins are blocked and we're returning proper error code as defined in blocked bin list. (Default Code: 616: Your credit card cannot be processed by our system. Please try another card.). Additional codes can be 650-657 depending of bin. - We also block Maestro cards per system according to [[ https://m1.dvipadmin.com/payment_bin_filters | this list ]]. (Code 618: Maestro card currently not supported, please try a Visa or Mastercard.) - In cases when there was NSF transaction within last hour, transaction for that CC will be blocked unless the amount is lower than with previous NSF transaction (Code: Code 617: Your credit card is temporary blocked by our system. Please try another card.) - For INR transactions, if there was previous failed transaction attempt with the same CC, we block any further attempt with that CC (Code: 670: Your credit card is blocked. Please try another card.). For each of rules above, "fake" transaction will be saved and on DGVIP admin those transactions will be marked as SKIPPED. There are also two blocking mechanism where we currently don't store "fake" transactions: - Each user is allowed max 5 failed transactions attempts per hour. In case of any additional attempt we return Code: 604 'Too many attempts') - Each user is allowed only one step down within 24 hours. In case of additional transaction attempt after failed step down, we return Code 604: Too many attempts).