import_contacts
If you ever dealt with customers claiming that you charged them, but their transactions show as "canceled/declined" on the dashboard and you didn't get those amounts in your bank account, then this solution article is for you! This is a common issue and caused by many of the processors/banks, which ...
Mon, Jan 3, 2022 at 7:29 PM
import_contacts
Most probably this error happened because you are requesting to make payment with a currency that is not configured yet in your profile. In this article you will be going to know about: How to investigate the reason that caused this error? Reason #1: Using a currency that is not configured in your profile ...
Wed, Jan 19, 2022 at 8:15 PM
import_contacts
Most probably this error happened because either the customer's card issuing bank does NOT support 3DSecure authentication mode at all, or the customer's card does NOT (have active/enrolled in) 3DSecure authentication mode. In this article you will be going to know about: How to investigate the re...
Sun, Jan 16, 2022 at 9:21 PM
import_contacts
Most probably this error happened because the cardholder (your customer) is required to use a card that 3DS activated from his issuer bank which required a pass the 3DS authentication (OTP) for each payment to proceed. This means that he either has entered the wrong OTP (One Time Password) or triggered the cancel ...
Tue, Jan 11, 2022 at 9:30 AM
import_contacts
Most probably this error happened because the Issuer bank doesn't give the permission to authorize the transaction amount, even after passing the 3DSecure page, or the card is being restricted by the issuer. In this article you will be going to know about: How to investigate the reason that caused this e...
Thu, Sep 14, 2023 at 4:03 PM
import_contacts
Most probably this error happened because the acquirer bank does not support/enable the request's transaction type you have sent in the request payload, such as Refund, Sale, Auth, .. etc. To know more about "What is the different "tran_type" (transaction type)?" In this article you wil...
Fri, Feb 11, 2022 at 8:30 PM
import_contacts
Most probably this error happened because the cardholder (The merchant's customer) has not returned from the 3DS authentication process after redirection to his bank 3DSecure page. In this case, you may be will be reported by the customer that he had tried to make a payment and after redirecting to the 3DSecur...
Wed, Jun 29, 2022 at 1:31 PM
import_contacts
Most probably this error happened during the 3DS/authentication phase because either the customer's card issuing bank does NOT support 3DSecure authentication mode at all, or the customer's card does NOT (have active/enrolled in) 3DSecure authentication mode. In this article you will be going to know...
Wed, Oct 25, 2023 at 2:34 PM
import_contacts
Most probably this error happened during the 3DS/authentication phase because either the customer's card issuing bank does NOT support 3DSecure authentication mode at all, or the customer's card does NOT (have active/enrolled in) 3DSecure authentication mode. In this article you will be going to know ab...
Wed, Oct 25, 2023 at 2:38 PM
import_contacts
Most probably this error happened because either you are still in the onboarding stage and you are trying to perform live transactions (through a live profile) that are not accepted in the PayTabs system. In this article you will be going to know about: How to investigate the reason that caused this error? ...
Thu, Aug 8, 2024 at 12:43 PM