All systems operational
Rails (Stripe, Yapily) and Certivus are third-party providers; their status is mirrored here for transparency. Saldivo holds no funds, so a rail incident never puts your money at risk — only its movement.
How Saldivo reports availability
This page separates Saldivo-owned services from third-party rails so customers can see where an incident is happening. API, checkout, dashboard and webhook availability are measured from Saldivo systems. Stripe Connect, Yapily and Certivus signals are mirrored because they affect the payment journey, but funds remain with the regulated provider and the merchant account. A rail incident may delay a payment or a confirmation event; it does not place client money on Saldivo's balance sheet because Saldivo never holds funds.
Recent history
A Yapily upstream slowdown delayed bank-payment confirmations by up to 90 seconds for 22 minutes. No payments failed; all confirmed once the provider recovered. Resolved 14:32.
Dashboard read-only for 8 minutes during a database upgrade. The API and checkout were unaffected. Completed as planned.
No other incidents in the last 90 days.