Home
/
Status
/
Service
Global payments orchestration platform for connecting payment services worldwide.
Source
auto
Category
Payments
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 27m ago
22
Components
0
Active incidents
0
Maintenance
16.67%
90d uptime
Asynchronous transactions with degraded performance
Jun 17, 2:55 PM
Normalized official status-page data for incidents, maintenance, components, and history.
16.67%
Known uptime
6 known history days
22
Components tracked
0 outage, 0 degraded
51
Incidents indexed
0 active right now
28
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Core Transactional API
Operational
3DS Global
Operational
Advanced Vault
Operational
Alternative Payment Methods (APMs)
Operational
BIN MetaData
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
2
outage days
3
maintenance days
84
unknown days
Latest outages and degradations detected from the official status page.
After a period of monitoring, we have confirmed that the issue has been resolved and systems are operating normally. If you continue to experience any issues, please reach out to Support.
This incident has been resolved.
This incident has been resolved.
### Mar 18th 2026 — _Decryption Errors on API endpoints_ ### Summary Between 5:40 PM and 5:43 PM UTC on March 16, 2026, we experienced a brief issue during a key rotation that caused a small subset of API requests to fail due to decryption errors. These errors occurred within our system before any external processing took place. The issue was quickly identified, and traffic was immediately redirected to a stable environment, restoring normal service. ### What Happened At 5:36 PM UTC, we routed traffic to a newly deployed cluster of our encryption service running with the latest security keys. Shortly after, we observed decryption errors affecting a small subset of records, which resulted in some requests returning 500 error responses. We promptly redirected traffic back to the existing cluster, restoring normal operation. Further investigation determined that these records were still associated with a key in the process of rotation, and we updated them as a follow-up action to prevent the issue from recurring. ### Next Steps We have enhanced our process to ensure that a key’s usage is fully verified before it is removed from the encryption service. -The Spreedly Team
The storage issue affecting the Dodgeball production instance has been fully resolved. Capacity has been restored and systems are operating normally. We are no longer observing elevated error rates for customers using Dodgeball. Thank you for your patience while we worked to resolve this issue.
After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We are completing our investigation concerning the causes of the incident and any residual impact. We apologize for any inconvenience or disruption.
### February 10, 2026 — Credits Referencing Capture Transactions Failing ### High Level Summary Between approximately 1:56 PM UTC and 4:15 PM UTC on February 5, 2026, credit transactions where the reference transaction was a capture failed with the error "The specified `reference_token` corresponds to a transaction which cannot be used as a reference." ### What Happened At approximately 1:56 PM UTC on February 5, 2026, Spreedly rolled out a change to support credits on the CyberSource Rest gateway. This included a change in the way we validated reference transaction types used in credits. Specifically, there was an unintended side-effect which caused captures to no longer be treated as a valid reference type for credits on gateways other than CyberSource Rest. Once this was discovered, the code was reverted at 4:01PM UTC. By 4:15 PM UTC, credit requests against captures were fully functional. ### Next Steps * Any credit attempts that failed with this error are safe to retry * We are making improvements to our code review processes and regression test suite to ensure we catch similar errors before they make it into production * We have identified a gap in our observability surrounding validation errors that we will be prioritizing -The Spreedly Team
This incident has been resolved.
We’ve implemented a fix and stabilized the Dodgeball component that was experiencing a partial outage. After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We apologize for any inconvenience or disruption.
### February 3rd, 2026 — 3DS2 Global Transactions Pending Between 5:40 pm UTC and 7:24 PM UTC on January 27, 2026 the latest version of the Spreedly iFrame \(`iframe-v1`\) was configured to use version 1.180 which contained a bug related to the handling of device fingerprinting for `Sca::Authentications` in an end user's browser. As a result there was an elevated number of `Sca::Authentications` stuck in a pending flow with a `required_action` of `device_fingerprint`. These transactions were held in a pending state and never completed. Our team identified the issue and updated the version of iFrame \(`iframe-v1`\) to utilize `1.179`. ### What Happened At 5:40 pm UTC on January 27th, 2026 a new version of iFrame was released \(1.180\) and updated the version to be used in the `iframe-v1.min.js` asset to point to `1.180`. This change was meant to improve the error handling for the loading of 3rd party critical SDKs however it caused the SDK to enter a permanently error-ed state when attempting to perform device fingerprinting due to a race condition with loading the SDKs. At 7:20 pm UTC on January 27th, 2026 the change was rolled back and by 7:24 pm UTC, 2026 the `iframe-v1.min.js` asset globally was pointing to version `1.179`. ### Next Steps We have identified a gap in our observability and alerting within the iFrame service related to the managing of 3DS lifecycle flows that we will be prioritizing. -The Spreedly Team
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Spreedly status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
http://status.spreedly.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 22 of 22 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Advanced Vault Spreedlys Advanced Vault is the evolution of our vault and lifecycle services to a managed vault that combines core vaulting, lifecycle functionality, and data enrichment of payment methods with rules and best practices. | Operational | Group | Not recorded |
Supporting Services Spreedlys customer-facing tools and resources. | Operational | Group | Not recorded |
BIN MetaData BIN Metadata is a feature provided by Spreedly that allows merchants to access detailed information about a card's Bank Identification Number (BIN), which consists of the first six or more digits of a debit or credit card. | Operational | Component | Not recorded |
Core Transactional API | Operational | Component | 6/17/2026 |
app.spreedly.com Spreedlys internal customer interface that provides access to feature and functionality controls. | Operational | Component | Not recorded |
Core Secondary API Spreedlys non-transactional API (Store, List, Show, etc.) | Operational | Component | Not recorded |
Fingerprinting Fingerprinting assigns a randomly generated identifier to cards that share the same number (PAN), making it easy to identify when multiple payment methods represent the same underlying card. | Operational | Component | Not recorded |
3DS Global Spreedlys 3DS2 Global solution allows users to integrate with a single 3DS2 Server and bring their authentication parameters to any gateway that accepts third-party 3DS fields. | Operational | Component | Not recorded |
Lifecycle Management (Account Updater) Lifecycle Management (Account Updater) allows you to always keep your customers’ card details up-to-date. | Operational | Component | Not recorded |
Spreedly.com Spreedly website: spreedly.com | Operational | Component | Not recorded |
Alternative Payment Methods (APMs) APM - Spreedly supports Alternative Payment Methods outside of a credit card, ACH, or cash. | Operational | Component | Not recorded |
Docs.spreedly.com Spreedly developer-facing documentation and how-to. | Operational | Component | Not recorded |
Lifecycle Management (Account Updater) Callbacks As an alternative to viewing results in the Spreedly dashboard, callbacks are provided that will push Lifecycle Management (Account Updater) results to a destination of your choosing. | Operational | Component | Not recorded |
Composer Composer is Spreedly’s Low Code/No Code workflow builder that allows our customers to simplify implementation, orchestration and payment outcomes. | Operational | Component | Not recorded |
Network Tokenization Network Tokenization converts stored credit card data to secure network tokens, merchants get the benefits of higher security, better customer experience, and increased authorization success rates | Operational | Component | Not recorded |
Express Spreedlys fastest and simplest payment form that incurs the least amount of PCI scope and complete payment method tokenization. | Operational | Component | Not recorded |
Checkout Checkout is our next-generation, SDK-based payment solution. Designed to succeed our legacy iFrame implementation, it offers a more flexible and robust integration experience for modern payment workflows. | Operational | Component | Not recorded |
iFrame Spreedlys payment form is utilized to collect the credit card number and CVV for tokenization. | Operational | Component | Not recorded |
Payment Method Distribution (PMD) Spreedlys Payment Method Distribution (PMD) allows you to transact against another service’s API while still controlling your customer’s card data by vaulting with Spreedly. | Operational | Component | Not recorded |
Recover Recover enables our customers to automatically retry declined transactions on a backup gateway in the case of an outage or soft decline. This improves the chance that a transaction is ultimately successful and builds system resilience. | Operational | Component | Not recorded |
Spreedly Payment Fraud Prevention Spreedlys fraud solution is fully embedded in the orchestration workflow, empowering merchants with easy access to both fraud prevention and transaction optimization tools all within a single API call for payments. | Operational | Component | Not recorded |
Dodgeball | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Spreedly is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
