Bambora’s ongoing commitment to providing seamless payment services requires us to perform
maintenance to our production environment.
Therefore, we’re in touch to inform you of an upcoming change to Bambora Online services and scheduled downtime, to all online services, in the early hours of Sunday, March 8.
This time will be used to perform production compliance maintenance. To minimise impact to you and your customers, this important maintenance will result in an outage between midnight and 0400 AEDT on Sunday, March 8. If necessary, subsequent maintenance has been scheduled for Sunday, March 22.

Below is a timeline to clarify the process taken by the Bambora team during the scheduled maintenance.
2300 AEDT Saturday, March 7: Maintenance window opens
0000 AEDT Sunday, March 8: Outage window opens
0400 AEDT Sunday, March 8: Outage window closes; status update provided
0600 AEDT Sunday, March 8: Maintenance window closes

We appreciate your understanding and patience as we plan and perform this maintenance.
Below are frequently asked questions and answers that may assist you further, but if you have any questions regarding this maintenance activity please contact support on:
Email: support.apac@bambora.com
Phone: Australia - 1300 721 163 / New Zealand - 0508 477 477

FAQs
Does this only affect taking payments?
During the scheduled outage, ALL payment channels and ALL Bambora Online services will be
Unavailable i.e. Integrated & Custom Checkout, Standard Checkout & Invoice Pay, API Webservices, Mobile SDK, Batch processing, Bambora BackOffice (PRM), IVR (Australia & New Zealand), Bambora Fraud Defend (ReD, 3DS), Access IPG, Access Optus, transaction processing, SFTP

How long will I be unable to take payments?
Although a 4-hour outage window has been scheduled (midnight – 0400 AEDT Sunday, March 8),
Bambora will endeavour to minimise this window to reduce impact.

What will happen if customers attempt a transaction during the scheduled maintenance?
Integrated, Custom Checkout, Standard Checkout & Invoice Pay – if you don’t elect to put up your
own maintenance page, the “bambora” service will redirect to a dedicated web page (status page)
API Webservices - error logs should pick up 503 errors
Mobile SDK - error logs should pick up 503 errors
Batch processing - should refer to method of submission (API, Back Office or SFTP)
Bambora Backoffice – this will redirect to a dedicated web page (status page)
IVR – unless a change is self-managed by you on your IVR line, we expect your customers will receive
a busy signal
Bambora Fraud Defend – intermittent connectivity as test transactions are performed

How will vendor interfaces be affected?
Transaction processing across all bank links – all services will be unavailable with brief periods of
connectivity as test transaction are performed
SFTP – “operation timed out” messaging will appear in client logs as the server will be shut down; this will prevent automated batches and files from being loaded and processed