Assembly Payments 장애 기록

1. 2026년 9월 22일 오전 2:56 UTCinvestigating

   Zai 엔지니어는 상류 카드 결제 문제의 재발을 감지했습니다. 모든 거래가 영향을받지 않는 동안, 일부 오류는 make payment 및 책임 endpoints를 사용할 때 다시 경험할 수 있습니다. 우리의 팀은 우리의 상류 공급자와 이 문제점의 우선염 해결책에 접촉합니다. 우리는 더 많은 정보를 사용할 수 있기 때문에 업데이트를 계속 공유 할 것입니다. 우리는 이 recurrence를 통해 일해서 저희와 가진 방위를 감사하십시오.

2. 2026년 9월 22일 오전 4:57 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 9월 22일 오전 5:22 UTCresolved

   우리의 상류 공급자는 카드 지불 사건을 해결했습니다. make payment, 요금 및 카드 계정 생성 엔드포인트는 이제 정상적으로 작동하며, 더 이상 높은 오류를 볼 수 없습니다. 우리는 서비스를 밀접하게 감시하는 것을 계속할 것입니다. 이 해결 된 동안 당신의 인내에 감사드립니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 25일 오후 11:35 UTCinvestigating

   현재 Zai Dashboard https://dashboard.hellozai.com이 액세스 할 수있는 문제가 있습니다. 사용자는 이 시간에 포털을 통해 계정 데이터를 로그 또는 볼 수 없습니다. 현재 활동: 우리의 공학 팀은 문제점을 확인하고 해결책에 적극적으로 일하고 있습니다. 우리는 더 많은 정보로 업데이트를 제공 할 것입니다. 다음 업데이트: 내 [30/60] 분 또는 해상도. 우리는 모든 불편을 위해 사과합니다. 이것은 우리가 가득 차있는 서비스를 복원하는 동안 당신의 인내력을 원인과 평가할 수 있습니다.

2. 2026년 8월 25일 오후 11:52 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 15일 오전 2:16 UTCinvestigating

   현재 NPP Payouts에 영향을 미치는 문제점을 경험하고 있습니다. 결과적으로 NPP 지급은 지연되거나 사용할 수 없습니다. 침입을 최소화하기 위해, 영향을받은 지불금은 직접 입력을 통해 리디렉션되고 처리됩니다. Direct Entry 지불은 표준 처리 시간에 적용되며 NPP 지불금보다 더 오래 정착 할 수 있습니다. 우리의 엔지니어링 팀은 문제를 해결하고 가능한 한 빨리 정상적인 NPP Payout 서비스를 복원하기 위해 적극적으로 노력하고 있습니다. 더 많은 정보로 업데이트를 계속 제공 할 것입니다.

2. 2026년 7월 15일 오전 2:41 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 23일 오후 10:21 UTCinvestigating

   우리는 현재 우리의 지불 인프라의 일부에 영향을 미치는 제 3 자 전력 붕괴로 인해 중재 거래 승인 문제 및 토큰화 요청 오류를 경험하고 있습니다. 결과적으로, 일부 거래 승인은 쇠퇴하거나 오류를 반환 할 수 있습니다 "공정 요청에 사용할 수 없습니다". 서비스 몇 가지 영향을받는 시스템에 복원 된, 우리의 카드 공급자는 전체 서비스를 복원하는 데 계속. 우리는 상황을 감시하고 더 많은 업데이트를 제공 할 것입니다.

2. 2026년 6월 23일 오후 10:39 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 4일 오전 12:18 UTCmonitoring

   Overnight, we experienced a temporary issue with card tokenisation services of an upstream provider. This caused some card payments and card storage attempts to fail between 10:42pm Sunday 3 May and approximately 12:15am Monday 4 May. The issue has now been resolved and services are operating normally. • You can safely retry any card card storage requests that were affected. • Our technical teams are currently verifying the status of payments processed during this incident and we’ll provide further guidance on next steps regarding payment retries as soon as possible. We’re sorry for this disruption and appreciate your understanding.

2. 2026년 5월 4일 오전 3:19 UTCresolved

   Payments processed during this incident have now been verified by our team. If possible, it is safe to retry any payments that were declined during this period.

1. 2026년 4월 17일 오전 2:32 UTCidentified

   We are currently experiencing a delay affecting settlement processing for some BPAY transactions. Zai did not receive the expected BPAY settlement file at 8:30pm on 16 April 2026. Our banking partner is actively investigating this as a priority. We expect the file to be sent and processed today, with affected funds to be credited to each user's wallet on the next banking day, Monday 20 April 2026. We will provide a further update within the next two hours. We apologise for the inconvenience and appreciate your patience.

2. 2026년 4월 17일 오전 4:40 UTCresolved

   The previously missing BPAY settlement file has now been delivered to Zai by our banking partner and successfully processed. Affected funds will be available in user wallets on the next banking day, Monday 20 April 2026. No further impact is expected. We apologise again for any inconvenience caused and appreciate your patience while we worked with our banking partner to resolve this issue.

1. 2026년 3월 17일 오전 9:26 UTCidentified

   Pre-live maintenance is continuing to extend past the planned window - we will update when possible. Expect intermittent outages in the prelive API until this maintenance is completed.

2. 2026년 3월 17일 오전 10:10 UTCresolved

   These activities are now complete.

1. 2026년 3월 12일 오전 3:41 UTCinvestigating

   We are currently investigating a potential issue affecting an upstream provider's processing of American Express payment authorisations.

2. 2026년 3월 12일 오전 4:54 UTCmonitoring

   The issue has been resolved and service has been restored. Our teams are continuing to monitor closely to ensure ongoing stability. During the incident, American Express payment authorizations were impacted. Customers attempting to process payments with American Express cards may have experienced failed payment attempts. We recommend retrying any failed transactions. Our team is reviewing the status of affected payments, and if we identify cases requiring further action, we will contact the relevant customers directly. We apologize for the inconvenience and appreciate your patience while we worked to restore service.

3. 2026년 3월 12일 오전 7:42 UTCresolved

   The latest instance of this error was detected at ~3:05pm AEDT. Our ongoing monitoring confirms no further impact from this earlier upstream interruption to American Express transactions.

1. 2026년 3월 10일 오후 11:21 UTCinvestigating

   Some instability with PayTo services is being observed, and we are working internally to identify and rectify the underlying issue as soon as possible.

2. 2026년 3월 11일 오전 12:17 UTCmonitoring

   We have resolved the issue and are continuing to monitor the system to ensure stability. During the incident, some “Create PayTo Agreement” and “Initiate PayTo Payment” requests may have failed. Our team is currently reviewing the status of any affected transactions. If we identify impacts requiring action, we will contact the relevant customers directly with further information.

3. 2026년 3월 11일 오전 3:25 UTCresolved

   We have not observed any further impact since the service was stabilised, and this incident is now closed. Based on our review of affected transactions, the overall impact has been downgraded to Minor. We are continuing to investigate the status of a small number of affected transactions and will contact impacted customers directly if further information or action is required. If you have any concerns in the meantime, please contact our Technical Support team at [email protected].

1. 2025년 11월 25일 오후 11:16 UTCinvestigating

   Our upstream Cards processing provider has informed us of an incident causing potential latency to Cards transactions. We are working closely with our upstream provider to monitor their resolution of this issue. We will provide an update in 1 hour, or as soon as we have more information to share.

2. 2025년 11월 26일 오전 12:19 UTCinvestigating

   Our upstream cards processing provider has confirmed they are still working on their network issue, which may cause transaction latency, declines, or errors. We will continue to monitor their resolution of this incident and provide an update within the next 90 minutes, or as soon as we have updates to share. We apologise again for the impact this may cause.

3. 2025년 11월 26일 오전 12:26 UTCresolved

   Our upstream cards processing provider has informed us that the network latency issues they were experiencing have now been resolved and cards processing should be restored to normal. Zai will continue to closely monitor for any recurrence. We apologise for the impact this may have caused.

1. 2025년 8월 31일 오후 10:33 UTCinvestigating

   Zai Engineers have detected a recurrence of the upstream card payment issue experienced on Friday. While not all transactions are impacted, some errors may again be experienced when using the make_payment and charges endpoints. Our team is in contact with our upstream provider to prioritise resolution of this issue. We’ll continue to share updates as soon as more information is available. Thank you for bearing with us as we work through this recurrence.

2. 2025년 9월 1일 오전 12:01 UTCinvestigating

   Our investigation shows the impact is less severe than the partial outage experienced on Friday, however is still causing failures to some transactions. We are in close contact with our provider who is actively investigating the problem.

3. 2025년 9월 3일 오전 1:13 UTCmonitoring

   Our investigation with our provider has confirmed this issue only affects payments using cards that were added to Zai’s system during the previous upstream outage on Friday 29 August. Cards added before or after the outage are unaffected and can be used to transact successfully. * As a workaround, if possible, impacted payers may re-add their card and retry their payment. * If re-adding the card is not possible, we are continuing to work with our provider to restore functionality for the affected cards. Given this workaround, we will close this incident, but a further update will be posted here once the permanent fix has been installed by our provider. If you're not already subscribed to receive updates, you may follow this incident for alerts. We apologise for this trailing impact from Friday's upstream incident.

4. 2025년 9월 3일 오후 11:55 UTCresolved

   Our provider has released a fix for the issue affecting payment cards added to Zai's system during the outage window on Friday 29 August. Transactions on these cards should be successful going forward. We have not detected any further instances of the "HTTP 400" error since this fix was put in place, however if you continue to experience problems with card payments, please contact our Support team at [email protected]. We apologise again for the extended impact caused by our provider's prior incident.

1. 2025년 8월 29일 오전 12:41 UTCinvestigating

   We are currently experiencing a partial issue with card payments. While not all transactions are affected, you may encounter errors when using the make_payment and charges endpoints. This is due to an ongoing issue with our upstream provider. We are actively communicating with the provider and will share updates as soon as we receive further information. Payments can be retried once resolved if necessary. Thank you for your patience.

2. 2025년 8월 29일 오전 2:58 UTCidentified

   Our upstream provider is actively working on a fix, and we are in close contact with them as they progress.

3. 2025년 8월 29일 오전 5:49 UTCidentified

   Our upstream provider is continuing to work on resolving the issue as a priority. Based on latest updates, we currently anticipate service restoration by 5:40pm AEST, and we'll continue to provide updates if this changes. We understand how disruptive this is for those customers affected and sincerely appreciate your patience while we work toward full restoration.

4. 2025년 8월 29일 오전 6:23 UTCmonitoring

   Our upstream provider has implemented a fix, and we are closely monitoring the situation to ensure services remain stable. We’ll continue to provide updates until we are confident the issue is fully resolved.

5. 2025년 8월 29일 오전 7:01 UTCresolved

   Our upstream provider has confirmed that they have resolved today’s partial cards processing issue, and we have monitored that services have been operating normally since 3:59pm AEST. We know how disruptive this has been for impacted customers and sincerely apologise for the interruption. Thank you for your patience while we worked with our provider to restore service. Impacted customers may choose to retry any failed transactions.

1. 2025년 7월 17일 오전 3:44 UTCidentified

   We’re currently experiencing performance issues with our Production APIs. Our team is working to restore normal service levels. We apologise for any inconvenience and will provide more updates as they become available. This is impacting some customers but not all. We are aware of the cause and working on putting the fix in place currently.

2. 2025년 7월 17일 오전 4:03 UTCresolved

   This incident has been resolved and we are continuing to monitor.

1. 2025년 7월 6일 오전 10:40 UTCinvestigating

   We’re currently investigating issues with our Dashboard and Supplementary Data API endpoint. We apologise for any inconvenience and will post further updates as they become available.

2. 2025년 7월 6일 오후 10:30 UTCinvestigating

   We’re currently investigating issues with our Dashboard. The issue with the Supplementary Data API endpoint has been resolved. We apologise for any inconvenience and will continue to provide updates as they become available.

3. 2025년 7월 6일 오후 11:36 UTCresolved

   The issues affecting the Dashboard and Supplementary Data API endpoint have now been fully resolved. All systems are operating normally. We appreciate your patience and apologise for any inconvenience caused.

1. 2025년 4월 28일 오전 3:16 UTCinvestigating

   We’re currently investigating a service interruption with our Production API specifically in creation of new Virtual Accounts causing an increased rate of activation failure statuses. As we investigate please note that any Virtual Account creations that fail activation can be retried. We apologise for any inconvenience and will provide more updates as they become available.

2. 2025년 4월 28일 오전 6:04 UTCresolved

   This incident has been resolved.

1. 2025년 3월 2일 오후 10:02 UTCinvestigating

   We’re currently investigating a potential service interruption with our Card Payments. Some proportion of card payments are failing. We apologise for any inconvenience. We will provide more updates as they become available.

2. 2025년 3월 2일 오후 10:21 UTCinvestigating

   We’re experiencing a service outage with our Card Payments. Our team is currently working to restore the service. We apologise for any inconvenience and will provide more updates as they become available.

3. 2025년 3월 2일 오후 11:13 UTCinvestigating

   We’re experiencing a service outage with our Card Payments and registering new Credit Cards in the API. Our team is currently working to restore the service. We apologise for any inconvenience and will provide more updates as they become available.

4. 2025년 3월 2일 오후 11:24 UTCmonitoring

   Service has been restored, we are continuing to monitor this incident actively.

5. 2025년 3월 2일 오후 11:49 UTCresolved

   This incident has been resolved. We are still monitoring.

1. 2025년 1월 29일 오후 10:03 UTCidentified

   We’re currently investigating a potential service interruption with our Production APIs. We apologise for any inconvenience and will provide more updates as they become available. This is an intermittent issue causing Virtual Account and PayId registration failures.

2. 2025년 1월 29일 오후 10:56 UTCresolved

   This incident has been resolved.

1. 2025년 1월 8일 오전 5:32 UTCinvestigating

   We’re currently investigating a potential service interruption with our Production APIs. We apologise for any inconvenience and will provide more updates as they become available. This is specifically impacting registrations of new PayIds and Virtual Accounts.

2. 2025년 1월 8일 오후 10:16 UTCresolved

   This incident was due to a 3rd party integration and was resolved by the 3rd party.

1. 2024년 11월 21일 오전 7:13 UTCinvestigating

   Connectivity issues with our upstream partner are again causing disruption to our Virtual Accounts registration APIs. Resolution of the issue is ultimately outside our control, however we will continue to monitor the situation closely. Further updates will be posted ASAP.

2. 2024년 11월 21일 오전 7:15 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2024년 11월 21일 오전 7:19 UTCinvestigating

   Apologies, the last status update was in error. The issue remains unresolved, and we are continuing to monitor.

4. 2024년 11월 21일 오전 8:18 UTCresolved

   This incident has been resolved.

1. 2024년 11월 21일 오전 2:46 UTCinvestigating

   We are currently experiencing connectivity issues with an upstream provider, impacting our ability to register new Virtual Accounts. The team are working on this on highest priority, and will advise as further information becomes available.

2. 2024년 11월 21일 오전 3:15 UTCmonitoring

   We continue to experience connectivity issues - but the issue is reduced with only some requests now being impacted. Reducing the severity of this incident as we continue to monitor.

3. 2024년 11월 21일 오전 3:52 UTCresolved

   Connectivity issues with upstream provider are now resolved.