All Systems Operational
Gateway Production
?
Operational
Reporting Production
Operational
Reporting API Production
?
Operational
Reporting Worker Legacy Gateway Production
?
Operational
Reporting Worker Payment Fusion Gateway Production
?
Operational
Transactions Reporting Production
?
Operational
Terminal Provisioning Production
?
Operational
Terminal Updater Production
?
Operational
Transaction Broker Production
?
Operational
Gateway Sandbox
?
Operational
Reporting Sandbox
Operational
Reporting API Sandbox
?
Operational
Reporting Worker Legacy Gateway Sandbox
?
Operational
Reporting Worker Payment Fusion Gateway Sandbox
?
Operational
Transactions Reporting Sandbox
?
Operational
Terminal Provisioning Sandbox
?
Operational
Terminal Updater Sandbox
?
Operational
Transaction Broker Sandbox
?
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Scheduled Maintenance
Release: Transaction Broker v1.52.0
Mar 18, 01:00-02:00 PDT
We are preparing to update Transaction Broker in the Sandbox environment. Please refer to the production maintenance notification for information about this release.
The service is expected to remain available during the maintenance period.
Posted on Mar 17, 11:01 PDT
The service is expected to remain available during the maintenance period.
Posted on Mar 17, 11:01 PDT
Release: Transaction Broker v1.52.0
Mar 19, 01:00-02:00 PDT
Transaction Broker is being updated to improve performance, stability, and resolve inconsistencies in the API documentation.
Bug fixes
* Fixes an issue where the transaction type could be set to “Save Only” as part of a Confirm Amount workflow. Transaction Broker will now return an error when combining um_command: 'save' with confirm_amount: true.
Documentation updates
* The POST /transactions/adjust endpoint has been updated to ensure consistency when used, and to promote proper use of adjustments. This endpoint will add the new_tip amount to the original amount of the transaction, which is returned as the auth_amount in the response.
* Existing integrations are not affected by these changes. With new integrations, adjusts should only be used to add a tip to a transaction. Adjusting the balance independent of tipping and negative adjustments should not be performed.
* original_amount — This parameter is introduced as an alias of new_amount to better reflect the expected value. new_amount is still available on the endpoint.
* The description for the command parameter for POST /transactions/process/ach has been updated to reflect the allowed values.
* The receipt_ref_num was incorrectly shown as required on GET /transactions/receipt/render. The required indicator has been removed.
Other
* Improves monitoring of the Transaction Broker API that checks the health status of additional endpoints.
The service is expected to remain available during the maintenance period.
Posted on Mar 13, 15:13 PDT
Bug fixes
* Fixes an issue where the transaction type could be set to “Save Only” as part of a Confirm Amount workflow. Transaction Broker will now return an error when combining um_command: 'save' with confirm_amount: true.
Documentation updates
* The POST /transactions/adjust endpoint has been updated to ensure consistency when used, and to promote proper use of adjustments. This endpoint will add the new_tip amount to the original amount of the transaction, which is returned as the auth_amount in the response.
* Existing integrations are not affected by these changes. With new integrations, adjusts should only be used to add a tip to a transaction. Adjusting the balance independent of tipping and negative adjustments should not be performed.
* original_amount — This parameter is introduced as an alias of new_amount to better reflect the expected value. new_amount is still available on the endpoint.
* The description for the command parameter for POST /transactions/process/ach has been updated to reflect the allowed values.
* The receipt_ref_num was incorrectly shown as required on GET /transactions/receipt/render. The required indicator has been removed.
Other
* Improves monitoring of the Transaction Broker API that checks the health status of additional endpoints.
The service is expected to remain available during the maintenance period.
Posted on Mar 13, 15:13 PDT
Database Maintenance
Mar 31, 00:00-02:00 PDT
Transaction Broker (Production)
We are scheduling a maintenance period for the Transaction Broker database. Maintenance will occur within the scheduled window and downtime is expected to be less than 15 minutes. Subscribers will receive additional notifications at the start, and during the maintenance period.
Posted on Mar 2, 16:26 PST
We are scheduling a maintenance period for the Transaction Broker database. Maintenance will occur within the scheduled window and downtime is expected to be less than 15 minutes. Subscribers will receive additional notifications at the start, and during the maintenance period.
Posted on Mar 2, 16:26 PST
Control Center Maintenance (Sandbox)
Apr 2, 00:00-01:00 PDT
The operating environment for Control Center is being updated to the latest stable version, including updates to dependent components. We are not expecting any downtime during the maintenance period.
Posted on Mar 26, 13:50 PDT
Posted on Mar 26, 13:50 PDT
Control Center Maintenance (Production)
Apr 7, 00:00-01:00 PDT
The operating environment for Control Center is being updated to the latest stable version, including updates to dependent components. We are not expecting any downtime during the maintenance period.
Posted on Mar 26, 13:51 PDT
Posted on Mar 26, 13:51 PDT