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
In general, if you don't fully understand the contents of this article you are most likely not impacted and you have nothing to worry about!
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 beamstream.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 - wait for reissue 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 we will provide you with a download link for reissued beanstream.com SSL certificates here on June 20th.
If you are not sure whether or not that is the case please use the steps below to verify.
Verify your payment API connection
In order to verify whether or not you are storing the current beanstream.com certificate for validation purposes we will provide a separate temporary endpoint with the new certificate to confirm.
We will provide further instructions on June 20th.
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.
- June 20th: New beanstream.com SSL certificate and temporary endpoint for testing available
- July 18th: Beanstream.com SSL certificate changed at 9:00 a.m. PDT