search

Fiserv / Support

To create support tickets for tenants
9 stars 4 forks source link

Carat Payments, powered by Fiserv Commerce Hub Magento extension is not working #715

Open nitin-havaldar opened 1 week ago

nitin-havaldar commented 1 week ago

Product

Commerce Hub

Page

Magento Admin Panel

Description

We have recently purchased the Carat Payment Extension powered by Fiserv Commerce Hub from https://commercemarketplace.adobe.com/paradoxlabs-carat.html#product.info.details.support, after installing this extension, we have tried placing an order from the Magento admin & noticed the attached error & it is not proceeding further.

Please find the attached screenshot where the credentials are correct.

image

Please find the attached screenshot about the error in detail

Screenshot 2024-06-03 at 4 07 24 PM (1)

We have contacted the vendor of this extension i.e paradoxlabs, but they have informed us to contact Fiserv Commerce Hub as the issue is appearing from their iFrame.

I have replicated the same issue on the Magento Native 2.4.5-P8 version & still error is coming from the below JS file https://cert.api.fiservapps.com/ch/payments-vas/v1/card-form/assets/main.83d49f311c7ea057.js

Expected Behaviour

Extension should work without any errors

Operating system

macOS Ventura 13.6.7

Browser

Google Chrome Version 125.0.6422.142 (Official Build) (x86_64)

Region

No response

minh-pham1 commented 1 week ago

Hello! Redirecting this inquiry to @wwfiserv as this is outside of our jurisdiction.

wwfiserv commented 1 week ago

@nitin-havaldar I am unaware of this module as we currently don't have any certified 3rd party modules approved by Commerce Hub. I have forwarded the information to our SDK dev team to see if there is something going on.

wwfiserv commented 4 days ago

@nitin-havaldar sorry for the delay, unfortunately paradoxlabs didn't work with our implementation team, so we have no way to know how they integrated. Additionally it appears they are using our older v1 of our implementation which we will be sunsetting in favor of v2. Currently it appears the way credentialing is setup isn't working, you will need to contact the merchant account representative who can open an implementation ticket to have a set of API credentials manually created for cert.