During a routine database configuration change, we lost connection to the Payment Methods storage table. This prevented the use of payment methods in transactions and the creation of new payment methods.
During a routine database change to decommission extra nodes, a corruption occurred with our internal reference data. This corruption caused the database query optimizer to error when trying to process SQL queries on the payment methods storage, which resulted in the inability to access that storage table and led to errors from the application layer when trying to read, update, or create payment methods.
Payment methods successfully created during this period have had their fingerprints regenerated. Please contact Spreedly Support if you need the updated fingerprint values to utilize within your business processes and we will be happy to provide them.
Spreedly is also working with our database service provider on a more detailed root cause analysis. Moving forward, Spreedly will be proactively engaging with our database provider when performing these types of configuration changes.
-The Spreedly Team