Under international law, merchants are obliged to ensure that their clients' personal information and credit card details are processed accordingly before processing their transactions. Failure to comply with this can result in serious penalties and sanctions. However, some international merchant accounts still fail to comply with the law and visa checkout logos. This article briefly discusses the different possible failure cases where the card details has been processed incorrectly.
Visa checkout logos for debit and credit cards are sensitive data that is processed during card payments. If a merchant processes sensitive information, it is very important for the merchant to follow all the necessary procedures in implementing an effective authentication and security system. One of the most common Visa checkout logo issues occurs when the debit card data selected in the wallet is not correctly matched with the credit card data. In this case, the issuer may refuse to process the transaction or the issuer will return the money back to the client.
For standard Visa checkout, the issuer is legally bound to check the identity of the customer before processing the transaction. If the issuer suspects that the customer does not have the right to the money, then the card cannot be processed. The issuer is also obliged to inform the customer about the risk of unauthorized entry, including possible charges for accessing the account. If you want to avoid any unpleasant surprises, you should take extra precautions when selecting the payment method used by your merchant bank. Your choice of bank or financial institution plays a vital role in the security procedures followed. It is therefore advisable to choose a bank that is registered with the Payment Card Industry Data Security Standard (PCI DSSS).
When a payment is made through an in-app purchase, you can be rest assured that the authorization code is safely encrypted and may never be seen by anyone other than the authorized user. You will need to enter this code during the payment process in case the transaction is unsuccessful. To evade any type of charges from third parties, you should encrypt the authorization code. Once this is done, you can proceed to complete the transaction.
For a PC-to-PC transaction, there is another important option to avoid charges at the time of authorization: setting the paypage. The in this case, the user is required to enter the payment process code using the payment page generated. If no password is set in the paypage, you should automatically set a password on the connection. The PC client will prompt you to input a password as soon as a payment is processed.
In case, if you are processing payments through a mobile application, you should not use a different phone number for both in-app purchases and PC-to-PC transaction. The reasons are simple: this option is not supported by all devices and will result in the incompatibility between the payment process and the device. Furthermore, if you have integrated the button in your mobile application, it is strongly recommended to change the phone number used for the PC connection.
The third option is for users who have integrated the button in their mobile application. For such users, they are required to change the phone number used for the PC connection. The reasons are obvious: such users may not have access to the payment page on the mobile app. Therefore, they should use a different phone number for both the in-app purchase and the PC connection. As a result, every time a user clicks the button, the callid data is automatically redirected to the pay page and visa fee is debited from his or her account.
Finally, you must integrate the button according to the guidelines (see section 7 on page 7). In this case, the final process is quite similar to the first process. Only the third step is not covered. To complete this step, make sure that you have enabled the secure mode for the mobile application. The final step is to confirm whether the user has received the confirmation SMS and made any payment.