JPMorgan has issue on their side
Last updateresolvedOct 21 · 07:43 UTC
This incident has been resolved.
Reported by Solidgate on their status page.

checked Oct 23, 2026 8:58 PM UTC · Solidgate's official status page
Solidgate is up and running.
All components operational
Statusfield watches Solidgate alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
5 reports published by Solidgate in the last 30 days
When Solidgate breaks, it is typically resolved in 1h 36m — median across 4 resolved incidents over 30 days.
resolvedOct 21 · 07:43 UTC
This incident has been resolved.
Reported by Solidgate on their status page.
resolvedOct 20 · 18:32 UTC
This incident has been resolved.
Reported by Solidgate on their status page.
resolvedOct 15 · 12:14 UTC
Between 10:09 and 12:06 UTC on October 15, a small number of recurring payments using saved card tokens were declined with error code 6.03. The issue was limited to token-based recurring payments. First-time payments, whether with manually entered card details or digital wallets such as Apple Pay and Google Pay, were not affected. The issue has been fully mitigated and we are seeing no further related declines. Saved card tokens remained valid throughout, so affected payments can be safely retried. What this means for you Solidgate Subscriptions engine: affected payments will be retried automatically. No action is needed. Merchant-initiated (MIT) payments via API (your own subscription engine): please resend the payment requests that were declined with code 6.03 during this window, or we can do it on your behalf. Affected merchants will be contacted directly with details. Impact: Small number of recurring payments with saved card tokens, 10:09–11:55 UTC Action required: None for Subscriptions. MIT via API: retry declined requests, or ask us to retry them for you.
Reported by Solidgate on their status page.
resolvedOct 1 · 12:23 UTC
This incident has been resolved.
Reported by Solidgate on their status page.
resolvedSep 29 · 07:51 UTC
This incident has been resolved.
Reported by Solidgate on their status page.