Xendit Outage History

Xendit degraded · 1 active incident View live status →

There were 30 Xendit outages since April 16, 2026 totaling 6h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.xendit.co

Minor May 3, 2026

Payouts Disruption in Thailand

Detected by Pingoru
May 03, 2026, 07:50 PM UTC
Resolved
May 03, 2026, 08:00 PM UTC
Duration
10m
Affected: TH All Destinations
Timeline · 2 updates
  1. identified May 03, 2026, 07:50 PM UTC

    Dear valued customers, We are currently seeing delays in processing Payouts to the following THB destinations due to system issues with our partner. TH_BBL: All amount

  2. resolved May 03, 2026, 08:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 3, 2026

EWALLET LINKAJA Indonesia Disruption

Detected by Pingoru
May 03, 2026, 04:59 PM UTC
Resolved
May 03, 2026, 05:03 PM UTC
Duration
3m
Affected: E-Wallets - LinkAja
Timeline · 2 updates
  1. identified May 03, 2026, 04:59 PM UTC

    Dear Valued Customers, We have detected issues with LINKAJA EWALLET payments due to a disruption on our partner's end. Impact: - We are seeing issues with completion of payments on LINKAJA - Merchants will be able to initiate transactions successfully, but are likely to receive delayed callbacks for payment completion. - Market: Indonesia - Impact: successful payment rate dropped below normal threshold We are currently in the process of investigating and will keep this page updated as we learn more and restore these services. In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Advise end users to complete payments via an alternative eWallet provider until the resolution of the issue. - Reconciliation of the status of transactions which have been initiated after the incident will be required. We will work with our eWallet provider and provide additional information in due course. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 03, 2026, 05:03 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 3, 2026

DIRECT_DEBIT MAYBANK2U Malaysia Disruption

Detected by Pingoru
May 03, 2026, 04:07 PM UTC
Resolved
May 03, 2026, 04:39 PM UTC
Duration
32m
Affected: Direct Debit - MAYBANK2U
Timeline · 2 updates
  1. identified May 03, 2026, 04:07 PM UTC

    Dear Valued Customers, We have detected issues with DIRECT_DEBIT MAYBANK2U payments due to disruption on our partner's end. Impact: - We are seeing issues with completion of payments. We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Customers may use other payment methods in the meantime. - It is recommended to wait for the channel to stabilize before retrying the transaction. - If a customer encounters any failed transactions but were debited, a reversal will be processed within the next 5 business days. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 03, 2026, 04:39 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 3, 2026

VIRTUAL_ACCOUNT MANDIRI Indonesia Disruption

Detected by Pingoru
May 03, 2026, 03:29 PM UTC
Resolved
May 03, 2026, 03:32 PM UTC
Duration
2m
Affected: Virtual Account - Mandiri
Timeline · 2 updates
  1. identified May 03, 2026, 03:29 PM UTC

    Dear Valued Customers, We have detected issues with VIRTUAL_ACCOUNT MANDIRI payment due to disruption on our partner's end. Impact: - The created virtual accounts cannot be paid - The successful virtual accounts payment will take longer to process We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Advise your payers to use other payment channels Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 03, 2026, 03:32 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 3, 2026

DIRECT_DEBIT BANK_OF_AYUDHYA Thailand Disruption

Detected by Pingoru
May 03, 2026, 09:08 AM UTC
Resolved
May 03, 2026, 09:13 AM UTC
Duration
4m
Affected: Direct Debit - Bank of Ayudhya
Timeline · 2 updates
  1. identified May 03, 2026, 09:08 AM UTC

    Dear Valued Customers, We have detected issues with DIRECT_DEBIT BANK_OF_AYUDHYA payments due to disruption on our partner's end. Impact: - We are seeing issues with completion of payments. We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Customers may use other payment methods in the meantime. - It is recommended to wait for the channel to stabilize before retrying the transaction. - If a customer encounters any failed transactions but were debited, a reversal will be processed within the next 5 business days. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 03, 2026, 09:13 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 3, 2026

DIRECT_DEBIT KRUNGTHAI_BANK Thailand Disruption

Detected by Pingoru
May 03, 2026, 09:08 AM UTC
Resolved
May 03, 2026, 09:13 AM UTC
Duration
4m
Affected: Direct Debit - Krungthai Bank
Timeline · 2 updates
  1. identified May 03, 2026, 09:08 AM UTC

    Dear Valued Customers, We have detected issues with DIRECT_DEBIT KRUNGTHAI_BANK payments due to disruption on our partner's end. Impact: - We are seeing issues with completion of payments. We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Customers may use other payment methods in the meantime. - It is recommended to wait for the channel to stabilize before retrying the transaction. - If a customer encounters any failed transactions but were debited, a reversal will be processed within the next 5 business days. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 03, 2026, 09:13 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 3, 2026

DIRECT_DEBIT SIAM_COMMERCIAL_BANK Thailand Disruption

Detected by Pingoru
May 03, 2026, 09:08 AM UTC
Resolved
May 03, 2026, 09:13 AM UTC
Duration
4m
Affected: Direct Debit - Siam Commercial Bank
Timeline · 2 updates
  1. identified May 03, 2026, 09:08 AM UTC

    Dear Valued Customers, We have detected issues with DIRECT_DEBIT SIAM_COMMERCIAL_BANK payments due to disruption on our partner's end. Impact: - We are seeing issues with completion of payments. We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Customers may use other payment methods in the meantime. - It is recommended to wait for the channel to stabilize before retrying the transaction. - If a customer encounters any failed transactions but were debited, a reversal will be processed within the next 5 business days. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 03, 2026, 09:13 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 3, 2026

DIRECT_DEBIT BANK_OF_BANGKOK_LIMITED Thailand Disruption

Detected by Pingoru
May 03, 2026, 09:08 AM UTC
Resolved
May 03, 2026, 09:13 AM UTC
Duration
4m
Affected: Direct Debit - Bank of Bangkok Limited
Timeline · 2 updates
  1. identified May 03, 2026, 09:08 AM UTC

    Dear Valued Customers, We have detected issues with DIRECT_DEBIT BANK_OF_BANGKOK_LIMITED payments due to disruption on our partner's end. Impact: - We are seeing issues with completion of payments. We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Customers may use other payment methods in the meantime. - It is recommended to wait for the channel to stabilize before retrying the transaction. - If a customer encounters any failed transactions but were debited, a reversal will be processed within the next 5 business days. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 03, 2026, 09:13 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 3, 2026

DIRECT_DEBIT KASIKORNBANK Thailand Disruption

Detected by Pingoru
May 03, 2026, 09:08 AM UTC
Resolved
May 03, 2026, 09:13 AM UTC
Duration
4m
Affected: Direct Debit - Kasikornbank
Timeline · 2 updates
  1. identified May 03, 2026, 09:08 AM UTC

    Dear Valued Customers, We have detected issues with DIRECT_DEBIT KASIKORNBANK payments due to disruption on our partner's end. Impact: - We are seeing issues with completion of payments. We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Customers may use other payment methods in the meantime. - It is recommended to wait for the channel to stabilize before retrying the transaction. - If a customer encounters any failed transactions but were debited, a reversal will be processed within the next 5 business days. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 03, 2026, 09:13 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 3, 2026

EWALLET GOPAY Indonesia Disruption

Detected by Pingoru
May 03, 2026, 01:17 AM UTC
Resolved
May 03, 2026, 01:25 AM UTC
Duration
7m
Affected: E-Wallets - GoPay
Timeline · 2 updates
  1. identified May 03, 2026, 01:17 AM UTC

    Dear Valued Customers, We have detected issues with GOPAY EWALLET payments due to a disruption on our partner's end. Impact: - Intermittent timeouts on EWALLET for creation of charge requests - Merchants will be able to initiate transactions, but will receive a CHANNEL_UNAVAILABLE error with a HTTP 503 response on a percent of requests. - Over 16.70% of requests in the last 15 minutes have been affected - First triggered at: 2026-05-03 08:08:12+07:00 We are currently in the process of investigating and will keep this page updated as we learn more and restore these services. In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Retry transactions for which a 503 error is received. - Reconciliation of the status of transactions after the incident will not be required. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 03, 2026, 01:25 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 2, 2026

QR_CODE QRPH Philippines Disruption

Detected by Pingoru
May 02, 2026, 09:41 PM UTC
Resolved
May 02, 2026, 09:56 PM UTC
Duration
15m
Affected: QR Payments - QRPH
Timeline · 2 updates
  1. identified May 02, 2026, 09:41 PM UTC

    Dear Valued Customers, We have detected issues with QRPH QR_CODE payments due to a disruption on our partner's end. Impact: - Intermittent timeouts on QR_CODE for creation of charge requests - Merchants will be able to initiate transactions, but will receive a CHANNEL_UNAVAILABLE error with a HTTP 503 response on a percent of requests. - Market: ph - Over 0.132% of requests in the last 15 minutes have been affected We are currently in the process of investigating and will keep this page updated as we learn more and restore these services. In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Retry transactions for which a 503 error is received. - Reconciliation of the status of transactions after the incident will not be required. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 02, 2026, 09:56 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 2, 2026

Payouts Disruption in Indonesia

Detected by Pingoru
May 02, 2026, 09:30 PM UTC
Resolved
May 02, 2026, 09:40 PM UTC
Duration
9m
Affected: Disbursement - BNIDisbursement - Other Indonesia banks and E-WalletsRemittance Payouts
Timeline · 2 updates
  1. identified May 02, 2026, 09:30 PM UTC

    Dear valued customers, We are currently seeing delays in processing Disbursements, Remittance, Escrow to the following IDR destinations due to system issues with our partner. BNI: 5000-9999, 100000001-250000000

  2. resolved May 02, 2026, 09:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 1, 2026

DIRECT_DEBIT BPI Philippines Disruption

Detected by Pingoru
May 01, 2026, 07:59 PM UTC
Resolved
May 01, 2026, 08:11 PM UTC
Duration
11m
Affected: Direct Debit - BPI
Timeline · 2 updates
  1. identified May 01, 2026, 07:59 PM UTC

    Dear Valued Customers, We have detected issues with DIRECT_DEBIT BPI payments due to disruption on our partner's end. Impact: - We are seeing issues with completion of payments. We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Customers may use other payment methods in the meantime. - It is recommended to wait for the channel to stabilize before retrying the transaction. - If a customer encounters any failed transactions but were debited, a reversal will be processed within the next 5 business days. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved May 01, 2026, 08:11 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor May 1, 2026

Intermittent API Error

Detected by Pingoru
May 01, 2026, 02:31 AM UTC
Resolved
May 01, 2026, 01:55 AM UTC
Duration
Timeline · 1 update
  1. resolved May 01, 2026, 02:31 AM UTC

    Dear Valued Customers, We have detected intermittent disruption from our API gateway that impact a small percentage of requests. Time range: - 8:55-8:58 GMT+7 Impact: - Your requests may get 500 error code during the impacted time range. The service has recovered and you may retry your requests again. Sorry for the inconvenience caused. Sincerely, Xendit customer service

Read the full incident report →

Minor April 30, 2026

Payouts Disruption in Philippines

Detected by Pingoru
Apr 30, 2026, 02:20 PM UTC
Resolved
Apr 30, 2026, 02:40 PM UTC
Duration
19m
Affected: Disbursement - Other Philippines banks and E-Wallets
Timeline · 2 updates
  1. identified Apr 30, 2026, 02:20 PM UTC

    Dear valued customers, We are currently seeing delays in processing Payouts, Disbursements to the following PHP destinations due to system issues with our partner. PH_SEC: above 50001

  2. resolved Apr 30, 2026, 02:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 30, 2026

QR_CODE DANA Indonesia Disruption

Detected by Pingoru
Apr 30, 2026, 11:43 AM UTC
Resolved
Apr 30, 2026, 12:08 PM UTC
Duration
24m
Affected: QR Payments - DANA
Timeline · 2 updates
  1. identified Apr 30, 2026, 11:43 AM UTC

    Dear Valued Customers, We have detected issues with DANA QR_CODE payments due to a disruption on our partner's end. Impact: - Intermittent timeouts on QR_CODE for creation of charge requests - Merchants will be able to initiate transactions, but will receive a CHANNEL_UNAVAILABLE error with a HTTP 503 response on a percent of requests. - Market: Indonesia - Over 0.115% of requests in the last 15 minutes have been affected We are currently in the process of investigating and will keep this page updated as we learn more and restore these services. In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Retry transactions for which a 503 error is received. - Reconciliation of the status of transactions after the incident will not be required. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 30, 2026, 12:08 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor April 29, 2026

EWALLET TRUEMONEY Thailand Disruption

Detected by Pingoru
Apr 29, 2026, 09:10 PM UTC
Resolved
Apr 29, 2026, 09:11 PM UTC
Duration
59s
Affected: E-Wallets - TrueMoney
Timeline · 2 updates
  1. identified Apr 29, 2026, 09:10 PM UTC

    Dear Valued Customers, We have detected issues with TRUEMONEY EWALLET payments due to a disruption on our partner's end. Impact: - We are seeing issues with completion of payments on TRUEMONEY - Merchants will be able to initiate transactions successfully, but are likely to receive delayed callbacks for payment completion. - Market: Thailand - Impact: successful payment rate dropped below normal threshold We are currently in the process of investigating and will keep this page updated as we learn more and restore these services. In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Advise end users to complete payments via an alternative eWallet provider until the resolution of the issue. - Reconciliation of the status of transactions which have been initiated after the incident will be required. We will work with our eWallet provider and provide additional information in due course. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 29, 2026, 09:11 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor April 28, 2026

EWALLET PAYMAYA Philippines Disruption

Detected by Pingoru
Apr 28, 2026, 05:16 PM UTC
Resolved
Apr 28, 2026, 05:19 PM UTC
Duration
3m
Affected: E-Wallets - Paymaya
Timeline · 2 updates
  1. identified Apr 28, 2026, 05:16 PM UTC

    Dear Valued Customers, We have detected issues with PAYMAYA EWALLET payments due to a disruption on our partner's end. Impact: - Intermittent timeouts on EWALLET for creation of charge requests - Merchants will be able to initiate transactions, but will receive a CHANNEL_UNAVAILABLE error with a HTTP 503 response on a percent of requests. - Over 15.20% of requests in the last 15 minutes have been affected - First triggered at: 2026-04-29 01:13:19+08:00 We are currently in the process of investigating and will keep this page updated as we learn more and restore these services. In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Retry transactions for which a 503 error is received. - Reconciliation of the status of transactions after the incident will not be required. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 28, 2026, 05:19 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor April 28, 2026

EWALLET SHOPEEPAY Philippines Disruption

Detected by Pingoru
Apr 28, 2026, 12:59 PM UTC
Resolved
Apr 28, 2026, 01:14 PM UTC
Duration
15m
Affected: E-Wallets - ShopeePay
Timeline · 2 updates
  1. identified Apr 28, 2026, 12:59 PM UTC

    Dear Valued Customers, We have detected issues with SHOPEEPAY EWALLET payments due to a disruption on our partner's end. Impact: - We are seeing issues with completion of payments on SHOPEEPAY - Merchants will be able to initiate transactions successfully, but are likely to receive delayed callbacks for payment completion. - Impact: callback latency is high within the last 15 minutes with latency up to 53.562s - First triggered at: 2026-04-28 20:57:29+08:00 We are currently in the process of investigating and will keep this page updated as we learn more and restore these services. In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Advise end users to complete payments via an alternative eWallet provider until the resolution of the issue. - Reconciliation of the status of transactions which have been initiated after the incident will be required. We will work with our eWallet provider and provide additional information in due course. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 28, 2026, 01:14 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor April 28, 2026

EWALLET OVO Indonesia Disruption

Detected by Pingoru
Apr 28, 2026, 07:20 AM UTC
Resolved
Apr 28, 2026, 07:24 AM UTC
Duration
3m
Affected: E-Wallets - OVO
Timeline · 2 updates
  1. identified Apr 28, 2026, 07:20 AM UTC

    Dear Valued Customers, We have detected issues with OVO EWALLET payments due to a disruption on our partner's end. Impact: - Intermittent timeouts on EWALLET for creation of charge requests - Merchants will be able to initiate transactions, but will receive a CHANNEL_UNAVAILABLE error with a HTTP 503 response on a percent of requests. - Market: Indonesia - Over 0.056% of requests in the last 10 minutes have been affected We are currently in the process of investigating and will keep this page updated as we learn more and restore these services. In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Retry transactions for which a 503 error is received. - Reconciliation of the status of transactions after the incident will not be required. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 28, 2026, 07:24 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor April 27, 2026

PAYLATER KREDIVO Indonesia Disruption

Detected by Pingoru
Apr 27, 2026, 07:15 AM UTC
Resolved
Apr 27, 2026, 07:21 AM UTC
Duration
6m
Affected: PayLater - Kredivo
Timeline · 2 updates
  1. identified Apr 27, 2026, 07:15 AM UTC

    Dear Valued Customers, We have detected issues with KREDIVO PAYLATER payments due to a disruption on our partner's end. Impact: - Intermittent timeouts on PAYLATER for creation of charge requests - Merchants will be able to initiate transactions, but will receive a CHANNEL_UNAVAILABLE error with a HTTP 503 response on a percent of requests. - - We are currently in the process of investigating and will keep this page updated as we learn more and restore these services. In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Retry transactions for which a 503 error is received. - Reconciliation of the status of transactions after the incident will not be required. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 27, 2026, 07:21 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor April 24, 2026

VIRTUAL_ACCOUNT BSI Indonesia Disruption

Detected by Pingoru
Apr 24, 2026, 08:22 AM UTC
Resolved
Apr 24, 2026, 09:08 AM UTC
Duration
46m
Affected: Virtual Account - BSI
Timeline · 2 updates
  1. identified Apr 24, 2026, 08:22 AM UTC

    Dear Valued Customers, We have detected issues with VIRTUAL_ACCOUNT BSI payment due to disruption on our partner's end. Impact: - The created virtual accounts cannot be paid - The successful virtual accounts payment will take longer to process We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Advise your payers to use other payment channels Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 24, 2026, 09:08 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor April 23, 2026

CREDIT_CARDS Disruption

Detected by Pingoru
Apr 23, 2026, 09:46 PM UTC
Resolved
Apr 23, 2026, 10:06 PM UTC
Duration
19m
Affected: Credit/Debit Cards
Timeline · 2 updates
  1. identified Apr 23, 2026, 09:46 PM UTC

    Dear Valued Customers, We have detected a disruption in CREDIT_CARDS payments due to disruption on our partner. Impact: You will experience an intermittent disruption and potentially won't be able to perform 3DS authentication transactions during this period. We are inquiring about more information from our partner and will keep this page updated as we hear news from our partner. Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 23, 2026, 10:06 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor April 23, 2026

VIRTUAL_ACCOUNT BRI Indonesia Disruption

Detected by Pingoru
Apr 23, 2026, 04:28 AM UTC
Resolved
Apr 23, 2026, 05:12 AM UTC
Duration
44m
Affected: Virtual Account - BRI
Timeline · 2 updates
  1. identified Apr 23, 2026, 04:28 AM UTC

    Dear Valued Customers, We have detected issues with VIRTUAL_ACCOUNT BRI payment due to disruption on our partner's end. Impact: - The created virtual accounts cannot be paid - The successful virtual accounts payment will take longer to process We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Advise your payers to use other payment channels Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 23, 2026, 05:12 AM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Minor April 22, 2026

VIRTUAL_ACCOUNT BJB Indonesia Disruption

Detected by Pingoru
Apr 22, 2026, 01:26 PM UTC
Resolved
Apr 22, 2026, 02:33 PM UTC
Duration
1h 7m
Affected: Virtual Account - BJB
Timeline · 2 updates
  1. identified Apr 22, 2026, 01:26 PM UTC

    Dear Valued Customers, We have detected issues with VIRTUAL_ACCOUNT BJB creation due to disruption on our partner's end. Impact: - New virtual accounts cannot be created We are investigating and will keep this page updated as we hear news from our partner. In the meantime, we recommend that you take the following actions to mitigate disruption during this incident: - Advise your payers to use other payment channels Sorry for the inconvenience caused. Sincerely, Xendit customer service

  2. resolved Apr 22, 2026, 02:33 PM UTC

    Dear Customers, This incident has been resolved. Sincerely, Xendit customer service

Read the full incident report →

Looking to track Xendit downtime and outages?

Pingoru polls Xendit's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Xendit reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Xendit alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Xendit for free

5 free monitors · No credit card required