If you are experiencing a problem with your Salesforce Commerce Cloud integration, there are several ways how you can troubleshoot the issue yourself. Before you contact our Support Team:<\/p>\n
The Adyen Payment cartridge does not make use of the Salesforce Commerce Cloud cache system.<\/p>\n
When troubleshooting, we still recommend that you clear the caches in Salesforce Commerce Cloud, for example in case a third-party cartridge is using the cache system.<\/p>\n
To clear the caches:<\/p>\n
The Adyen Payment cartridge is often used in combination with other cartridges that can impact your checkout flow or the backend processes.<\/p>\n
When using third-party cartridges, make sure that Adyen's cartridges are the first in the Cartridges<\/strong> box<\/a>.<\/p>\n When troubleshooting our cartridge, make sure to temporarily disable any third-party cartridge.<\/p>\n If you applied any customizations to the cartridge, the error might be related to the customization. You can check whether the issue is related to your custom code based on the way you implemented the customizations:<\/p>\n If you implemented the customizations in a separate cartridge as recommended in our customization guide<\/a>, you can temporarily remove this cartridge from your cartridge path to see if the error persists.<\/p>\n<\/li>\n If you have added custom code in one of the Adyen cartridges, check if it persists on a cleanly installed<\/a> cartridge. If you cannot reproduce the issue with a clean version, it is most likely a customization issue.<\/p>\n<\/li>\n<\/ul>\n Errors are logged by Salesforce Commerce Cloud in your Salesforce Business Manager. To find the logs:<\/p>\n If no errors are shown in the above logs, you can also check your console logs by inspecting the browser.<\/p>\n Learn how to troubleshoot the following common errors:<\/p>\n If a payment method is not showing up in your checkout, check the following:<\/p>\n Configuration errors include issues with the services, for example:<\/p>\n If you experience such issues, it is likely that the metadata was not loaded correctly.<\/p>\n We recommend that you:<\/p>\n This error indicates that there is an issue with the cartridge configuration.<\/p>\n This error is specific to PayPal, and indicates that the capture setting in your code does not match the capture setting on Adyen's side.<\/p>\n To resolve the issue, change the capture setting in your code to SALE<\/strong>.<\/p>\n Check if your current error is a known issue in the cartridge, and resolved in a later version. You can find the known issues and fixes either in our technical release notes on GitHub<\/a>, or in our commercial release notes<\/a>.<\/p>\n To find out which version of the cartridge you are using:<\/p>\n Go to the open issues in our GitHub<\/a>, and see if there is an open issue related to your error. If that is the case, you can leave a comment there to have direct contact with our dev teams.<\/p>\n If the problem still persists after you have followed the above steps, you can either:<\/p>\nStep 3: Check for customizations<\/h2>\n
\n
Step 4: Check Salesforce Commerce Cloud logs<\/h2>\n
\n
\nThis opens a page with all the logs.<\/li>\n<\/ol>\nStep 5: Check common errors<\/h2>\n
\n
Payment methods not showing up<\/h3>\n
\n
\/paymentMethods<\/code> API request include the correct country\/region and currency combination for the payment method? Use the service-adyen<\/code> log files<\/a> to look this up.<\/li>\n\/paymentMethods<\/code> API response? Use the service-adyen<\/code> log files<\/a> to look this up.<\/li>\n<\/ul>\nConfiguration errors<\/h3>\n
\n
\n
Errors when placing orders<\/h3>\n
No user found for OriginKey on validation<\/em><\/h4>\n
\n
Expected intent from order api call to be authorize, got capture<\/em><\/h4>\n
Step 6: Check our release notes<\/h2>\n
\n
\nThis opens the Payment Details<\/strong> page.<\/li>\n
\nThe cartridge version is shown under Payment Device Version<\/strong>.<\/li>\n<\/ol>\nStep 7: Check open issues in GitHub<\/h2>\n
Step 8: Contact us<\/h2>\n
\n
See also<\/h2>\n