Please note that the information in this article is of a technical nature.
- API integrations towards api.na.bambora.com
- Web terminal
- Virtual terminal
- Sage 50
Anyone who has actively taken the extra step of manually storing the beanstream.com SSL certificate to validate during their API calls towards beanstream.com endpoints.
What will happen if I don't do anything
If you are storing the old beanstream.com SSL certificate for validation during your API call, all of your API calls will fail after the certificate change on the July 18th.
Preferred solution - change to api.na.bambora.com today
Update your API integration endpoints from the www.beanstream.com domain to the api.na.bambora.com domain and download the na.bambora.com SSL certificates from the links below.
Alternative solution - use reissued of beanstream.com certificates
The old beanstream.com certificate was issued by Symantec. Google will distrust all Symantec certificates as of August 2018. Therefore a new certificate from a different issuer is required.
If you know that you are currently storing the certificate the new certificate is now available for download below.
Note: The certificate change on www.beanstream.com will occur on July 18th at 9:00 a.m. PT
Verify your payment API connection
If you want to test your certificate validation with the new certificate prior to July the 18th you can do so by pointing your integration to temp-ssl-test.beanstream.com and validate the new certificates available found above.
When will the cert change happen
As some network configurations may require that this change is precisely timed we will perform the change on July 18th 2018 at 9 a.m. PST sharp.
- July 18th: Beanstream.com SSL certificate changed at 9:00 a.m. PT
June 20th: New beanstream.com SSL certificate and temporary endpoint for testing available