You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, even if I load the client SDK via api2.heartlandportico.com, it attempts to load subsequent images (credit card images, cvv.png, etc) via api2-c which Chrome will not load from.
@charlie-s The api2-c subdomain is preferred, but both are backed by our payment gateway. For the client library, we are working with our internal teams to get the certificate corrected for the api2-c subdomain, but this shouldn't affect server-side communication via Node.js as far as we've seen.
Both domains point to our payment gateway in its sandbox/certification environment, so at the end of the day, you're hitting the same service. The production environment would be on both the https://api2.heartlandportico.com and the https://api2-c.heartlandportico.com subdomains.
What is the correct
serviceUrl
to use for both certification/testing and production for Heartland Portico?The docs suggest
https://cert.api2.heartlandportico.com
while the tests in this repo suggesthttps://cert.api2-c.heartlandportico.com
.The text was updated successfully, but these errors were encountered: