Troubleshoot E-commerce Integration Errors
Description
Troubleshoot some of the more common e-commerce integration errors
What's in this article?
The table below outlines some of the more common errors you may come across while creating your e-commerce integration.
| Common Error | Troubleshooting |
|---|---|
| Pointing to the correct endpoints in the wrong environment | Verify that you are using the appropriate endpoints (URL) in the payload for the test and production environments. Required endpoints are integration-specific and can be found in the guide for the method in which you have chosen to integrate. Refer to the appropriate guide for your integration: · Hosted Payments Page Integration Guide · Microform Integration Guide · Checkout API Developer's Guide · Card Not Present (CNP) Integration Toolkit (REST API) Developer's Guide |
| Incorrect e-commerce key generated from the right location | Check Key Management to confirm that the correct key type has been created. · Secure Acceptance integrations (HPP and Checkout API) should create the key in the profile. · REST API integrations use key management. · Microform must generate a certificate. · All methods should have generated an API key. |
| Profile not activated | For Hosted Payments Page and Checkout API, confirm that your profile was activated. The generated keys are active immediately, however, the profile must be manually activated. If you edit the profile, you will have to promote it to active again. |
| Transposing the Access Key and Secret Key in a REST API integration (Keys are not pasted accurately.) | Verify that you have pasted the correct key into the correct field within your e-commerce solution configuration screens where you have set up payments. These settings will ask for both the Access and Secret keys and they can easily be pasted into the wrong fields. NOTE: Hosted Payments Page (HPP) and Checkout API integrations only require the SHA2 key created in the Profile. |
| Security Keys expired | Keys generated through the Bank of America Gateway expire every three years after creation. The status of keys can be viewed in Key Management. If the key is expired, you must generate a new key as a replacement. |
| Invalid settings within the profile | Review your settings to ensure accuracy. |
| Merchant Notifications or Customer Response Page fail | If you are using merchant notifications or customer response pages, verify that you have placed a valid URL in the settings for these objects. Settings can be found within the Secure Acceptance profile. |