Is Rebill down?

Since 20:00 UTC today, we have been observing degraded performance in card payment processing for transactions in Mexico. Some transactions may be declined or take longer than usual to complete. The cause has been identified and our team is actively working to restore full service as soon as possible. A further update will be provided as soon as additional information is available. If you require assistance, please contact us at [email protected].

The issue affecting card payment processing in Mexico has been resolved and transactions are processing normally. We are monitoring the service closely to confirm stable performance before closing this incident. Any transaction declined during the affected window can be retried successfully. If you require assistance, please contact us at [email protected].

Card payment processing in Mexico has remained stable since the fix was applied. This incident is now resolved. We apologize for the inconvenience. If you require assistance, please contact us at [email protected].

STATUS Resolved DURATION Aug 29, 10:21 – 15:11 UTC UPDATE · Resolved · Aug 29, 17:30 UTC This incident has been resolved. Pix payments in Brazil are operating normally. Between 10:21 and 15:11 UTC, payment requests sent to the Pix processing service were not being completed, which prevented charges from being created. Affected attempts returned a generic decline message. No amount was charged and no funds were withheld from end customers. Card payments were not affected at any point, and payments in other countries operated normally throughout. Customers who could not complete a payment during that window can retry with no issues. If you have questions about a specific transaction, contact us at [email protected].

Identified – June 26, 2026, 08:08 UTC We have identified an issue affecting outbound webhook delivery to merchant endpoints, starting at approximately 08:08 UTC today. Events are being generated and queued correctly, but the delivery worker is experiencing periods of reduced throughput, causing notifications to arrive with delays. Payment and subscription processing are operating normally on our side. The impact is limited to the timing of webhook notifications. Our engineering team is actively investigating and we will post the next update as soon as we have more information. We apologize for the inconvenience, and if you need assistance, please reach out to us at [email protected].

Resolved – June 26, 2026, 20:11 UTC Outbound webhook delivery has been fully restored as of 20:11 UTC. All events queued during the affected window (08:08 UTC to 20:11 UTC) have been successfully delivered to merchant endpoints. Payment and subscription processing were not affected at any point. The impact was limited to the timing of webhook notifications, which arrived with delays ranging from a few minutes up to several hours for some events. We apologize for the inconvenience this may have caused. If you notice any missing notification on your end, please reach out to us at [email protected] and we will trace it individually.

Identified – June 18, 2026, 14:35 UTC We identified an issue affecting outbound webhook delivery to merchant endpoints, starting at approximately 10:40 UTC today. During this window, payment events (payment.created and payment.updated) have been processing normally, but the corresponding webhook notifications have not been dispatched to merchant URLs. Payments themselves are unaffected — checkout, authorization, capture and settlement continue to operate normally. The impact is limited to the delivery of webhook notifications. In the meantime, the status of any payment can be retrieved directly through the Dashboard or the GET /v3/payments/{id} API. Our engineering team has identified the root cause and is working on restoring the service. We will post the next update as soon as it is back online. We apologize for the inconvenience, and if you need assistance, please reach out to us at [email protected].

Resolved – June 18, 2026, 15:30 UTC The issue affecting outbound webhook delivery has been resolved. Our engineering team applied a fix at 15:25 UTC, and all webhook notifications generated during the incident window (10:40 UTC to 15:25 UTC) were automatically re-dispatched to merchant endpoints between 15:26 UTC and 15:28 UTC. From that point onward, webhook delivery has resumed normal operation. Payment processing was not affected at any point during the incident. We apologize for the inconvenience, and if you need assistance, please reach out to us at [email protected].