- Detected by Pingoru
- Jun 18, 2026, 02:02 AM UTC
- Resolved
- Jun 18, 2026, 02:25 AM UTC
- Duration
- 22m
Affected: Over-The-Counter Payments - ECPay Loans
Timeline · 2 updates
-
identified Jun 18, 2026, 02:02 AM UTC
Dear Valued Customers, We have detected issues with Over-The-Counter (OTC) ECPAY_LOAN payments due to disruption on our partner's end. Impact: - The created Over-The-Counter (OTC) ECPAY_LOAN cannot be paid - The successful Over-The-Counter (OTC) payment will take longer to process - Merchants will still be able to create/update Over-The-Counter (OTC) payment codes 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
-
resolved Jun 18, 2026, 02:25 AM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 01:18 AM UTC
- Resolved
- Jun 18, 2026, 01:33 AM UTC
- Duration
- 15m
Affected: E-Wallets - ShopeePay
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 08:20 PM UTC
- Resolved
- Jun 17, 2026, 09:10 PM UTC
- Duration
- 49m
Affected: Disbursement - PaymayaDisbursement - Other Philippines banks and E-WalletsRemittance Payouts
Timeline · 3 updates
-
identified Jun 17, 2026, 08: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_PAYMAYA: 1-50000
-
identified Jun 17, 2026, 09:00 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
-
resolved Jun 17, 2026, 09:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 07:55 PM UTC
- Resolved
- Jun 17, 2026, 08:09 PM UTC
- Duration
- 13m
Affected: Direct Debit - BPI
Timeline · 2 updates
-
identified Jun 17, 2026, 07:55 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
-
resolved Jun 17, 2026, 08:09 PM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 06:42 PM UTC
- Resolved
- Jun 17, 2026, 06:45 PM UTC
- Duration
- 3m
Affected: E-Wallets - Paymaya
Timeline · 2 updates
-
identified Jun 17, 2026, 06:42 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.00% of requests in the last 15 minutes have been affected - First triggered at: 2026-06-18 02:39: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
-
resolved Jun 17, 2026, 06:45 PM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 04:12 PM UTC
- Resolved
- Jun 17, 2026, 06:02 PM UTC
- Duration
- 1h 50m
Affected: QR Payments - QRPH
Timeline · 2 updates
-
identified Jun 17, 2026, 04:12 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.122% 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
-
resolved Jun 17, 2026, 06:02 PM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 04:04 PM UTC
- Resolved
- Jun 17, 2026, 04:54 PM UTC
- Duration
- 50m
Affected: Direct Debit - MAYBANK2U
Timeline · 2 updates
-
identified Jun 17, 2026, 04:04 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
-
resolved Jun 17, 2026, 04:54 PM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 03:20 PM UTC
- Resolved
- Jun 17, 2026, 03:50 PM UTC
- Duration
- 29m
Affected: Disbursement - BCADisbursement - Other Indonesia banks and E-WalletsRemittance Payouts
Timeline · 2 updates
-
identified Jun 17, 2026, 03:20 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. BCA: 1-4999, 250000001-1000000000
-
resolved Jun 17, 2026, 03:50 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 05:13 AM UTC
- Resolved
- Jun 17, 2026, 05:13 AM UTC
- Duration
- —
Affected: Direct Debit - Unionbank
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 07:14 AM UTC
- Resolved
- Jun 16, 2026, 09:57 AM UTC
- Duration
- 2h 42m
Affected: Over-The-Counter Payments - Indomaret
Timeline · 2 updates
-
identified Jun 16, 2026, 07:14 AM UTC
Dear Valued Customers, We have detected issues with Over-The-Counter (OTC) INDOMARET payments due to disruption on our partner's end. Impact: - The created Over-The-Counter (OTC) INDOMARET cannot be paid - The successful Over-The-Counter (OTC) payment will take longer to process - Merchants will still be able to create/update Over-The-Counter (OTC) payment codes 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
-
resolved Jun 16, 2026, 09:57 AM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 07:50 PM UTC
- Resolved
- Jun 15, 2026, 08:00 PM UTC
- Duration
- 10m
Affected: TH All Destinations
Timeline · 2 updates
-
identified Jun 15, 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
-
resolved Jun 15, 2026, 08:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 06:23 PM UTC
- Resolved
- Jun 15, 2026, 06:41 PM UTC
- Duration
- 18m
Affected: E-Wallets - GoPay
Timeline · 2 updates
-
identified Jun 15, 2026, 06:23 PM 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-06-16 01:19: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
-
resolved Jun 15, 2026, 06:41 PM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 10:12 AM UTC
- Resolved
- Jun 15, 2026, 10:13 AM UTC
- Duration
- 59s
Affected: E-Wallets - LinkAja
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 09:46 AM UTC
- Resolved
- Jun 15, 2026, 10:15 AM UTC
- Duration
- 28m
Affected: E-Wallets - GCash
Timeline · 2 updates
-
identified Jun 15, 2026, 09:46 AM UTC
Dear Valued Customers, We have detected issues with GCASH 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 14.00% of requests in the last 10 minutes have been affected - First triggered at: 2026-06-15 17:43:16+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
-
resolved Jun 15, 2026, 10:15 AM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 04:46 AM UTC
- Resolved
- Jun 15, 2026, 05:09 AM UTC
- Duration
- 23m
Affected: Virtual Account - BJB
Timeline · 2 updates
-
identified Jun 15, 2026, 04:46 AM 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
-
resolved Jun 15, 2026, 05:09 AM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 14, 2026, 09:47 PM UTC
- Resolved
- Jun 15, 2026, 04:22 AM UTC
- Duration
- 6h 34m
Affected: Disbursement - BPIDirect Debit - BPIDirect Debit - BPI Online BankingDirect Debit - BPI Recurring
Timeline · 2 updates
-
investigating Jun 14, 2026, 09:47 PM UTC
Dear Valued Merchant, BPI just reported an ongoing unplanned service interruption affecting partner transactions. Restoration efforts are underway, with a tentative recovery target of 4pm PH time 14 June 2026. We'll keep this thread updated as soon as new information is available. Thank you
-
resolved Jun 15, 2026, 04:22 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 14, 2026, 08:45 PM UTC
- Resolved
- Jun 14, 2026, 08:48 PM UTC
- Duration
- 3m
Affected: E-Wallets - TrueMoney
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 10:38 AM UTC
- Resolved
- Jun 12, 2026, 10:55 AM UTC
- Duration
- 16m
Affected: E-Wallets - Touch n Go
Timeline · 2 updates
-
identified Jun 12, 2026, 10:38 AM UTC
Dear Valued Customers, We have detected issues with TOUCHNGO 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. - There is high error count on create charge for channel my_touchngo - First triggered at: 2026-06-12 18:35:25+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
-
resolved Jun 12, 2026, 10:55 AM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 04:33 AM UTC
- Resolved
- Jun 12, 2026, 04:52 AM UTC
- Duration
- 19m
Affected: Over-The-Counter Payments - 7-Eleven
Timeline · 2 updates
-
identified Jun 12, 2026, 04:33 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jun 12, 2026, 04:52 AM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 09:54 AM UTC
- Resolved
- Jun 09, 2026, 09:54 AM UTC
- Duration
- —
Affected: E-Wallets - AppotaE-Wallets - ShopeePayE-Wallets - AstrapayE-Wallets - DanaE-Wallets - VNPT WalletE-Wallets - Jenius PayE-Wallets - TrueMoneyE-Wallets - ZaloPayE-Wallets - LinkAjaPayment APIsE-Wallets - Line PayE-Wallets - NexCashE-Wallets - WeChat PayE-Wallets - OVOE-Wallets - ShopeePayE-Wallets - ShopeePayE-Wallets - GoPayE-Wallets - GoPay RecurringE-Wallets - AlipayE-Wallets - GCashE-Wallets - Touch n GoE-Wallets - GrabpayE-Wallets - ShopeePayE-Wallets - PaymayaE-Wallets - GrabpayE-Wallets - ShopeePayE-Wallets - WeChat Pay
Timeline · 1 update
-
resolved Jun 09, 2026, 09:54 AM UTC
Dear Valued Customers, We have detected issues with our E-Wallet refund through POST https://api.xendit.co/refunds from 8 June 11:38 AM GMT+7. The issue has been resolved on 9 June 04:07 PM GMT+7 Impact: - You may get 400 error code from this endpoint for E-Wallet refund In the meantime, we recommend that you take the following actions to mitigate disruptions to your end users during this incident: - Retry all the impacted transactions again Sorry for the inconvenience caused. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 08:48 AM UTC
- Resolved
- Jun 08, 2026, 08:52 AM UTC
- Duration
- 4m
Affected: Virtual Account - Mandiri
Timeline · 2 updates
-
identified Jun 08, 2026, 08:48 AM 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
-
resolved Jun 08, 2026, 08:52 AM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 02:10 AM UTC
- Resolved
- Jun 08, 2026, 02:12 AM UTC
- Duration
- 2m
Affected: PayLater - Kredivo
Timeline · 2 updates
-
identified Jun 08, 2026, 02:10 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
-
resolved Jun 08, 2026, 02:12 AM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 05:08 PM UTC
- Resolved
- Jun 05, 2026, 05:19 PM UTC
- Duration
- 11m
Affected: E-Wallets - ShopeePay
Timeline · 2 updates
-
identified Jun 05, 2026, 05:08 PM UTC
Dear Valued Customers, We have detected issues with SHOPEEPAY 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. - There is high error count on create charge for channel my_shopeepay - First triggered at: 2026-06-06 01:04:54+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
-
resolved Jun 05, 2026, 05:19 PM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 05:07 PM UTC
- Resolved
- Jun 05, 2026, 05:19 PM UTC
- Duration
- 12m
Affected: E-Wallets - ShopeePay
Timeline · 2 updates
-
identified Jun 05, 2026, 05:07 PM UTC
Dear Valued Customers, We have detected issues with SHOPEEPAY 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. - There is high error count on create charge for channel th_shopeepay - First triggered at: 2026-06-06 00:04:15+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
-
resolved Jun 05, 2026, 05:19 PM UTC
Dear Customers, This incident has been resolved. Sincerely, Xendit customer service
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 06:35 AM UTC
- Resolved
- Jun 05, 2026, 08:02 AM UTC
- Duration
- 1h 26m
Affected: QR Payments - Xendit
Timeline · 2 updates
Read the full incident report →