A Zoho Books Stripe gateway has entered a corrupted "ghost" state where the UI shows contradictory statuses (one place reports Stripe as Active but missing account details while the gateway list shows Stripe as Inactive and prompts "Set Up Now"). The gateway record in Zoho's backend needs a manual reset so you can reconnect Stripe cleanly [1].
What it means — concrete explanation tied to the Zoho API surface
The Stripe connector in Zoho Books keeps a backend gateway record that holds OAuth tokens, account metadata, and enabled payment methods. If that record becomes orphaned or inconsistent, the front-end screens can read different fields and display contradictory states: one component reads an "active" flag while another reads missing account metadata, and the UI blocks edits because the backend record is malformed. That broken gateway record prevents a fresh OAuth handshake or a normal delete/recreate flow and requires a manual backend reset by Zoho Support to remove the orphaned entry so the integration can be reestablished [1][6].
Common causes
- Interrupted or failed reconnect during OAuth flow leaves a half-created gateway row in the backend [1].
- Revoked access in the Stripe Dashboard without a clean disconnect in Zoho, leaving metadata mismatches between systems [1][6].
- Duplicate or orphaned gateway entries from past attempts, org imports, or account migrations that the UI cannot delete [1].
- UI/backend sync bug where the gateway "active" flag and the payment-method metadata diverge, producing conflicting screens [1].
How to fix it
- Try the UI steps once more: Settings → Online Payments → Payment Gateways → Credit/Debit Card → Stripe, click Edit, then Disconnect or Remove if available, and then reconnect via the Stripe OAuth flow.
- In Stripe, revoke Zoho access: log into Dashboard → Settings → Connected accounts or API Keys, remove Zoho connections, then attempt the reconnect from Zoho Books. Record timestamps and capture screenshots for each attempt [1][6].
- If the UI still shows contradictory states, gather diagnostic details: organization name, organization ID, data center (shown in Help Center banner), exact screenshots of both screens, browser console logs from the time of the action, and the list of steps you tried and timestamps.
- Open a Zoho Support ticket from Help Center > Contact Support (include "Request: backend reset of Stripe gateway record" in the subject) and attach the diagnostics. Explicitly request that Support delete or reset the Stripe gateway entry in the backend so you can run a fresh OAuth connect [1].
- Allow Support to perform the reset and then complete the standard Stripe OAuth flow in Zoho Books to reconfigure payment methods. Keep one admin session open and test with a small transaction or test mode.
When to escalate
Escalate to Zoho Support when repeated UI disconnects, Stripe revokes, and browser-session reconnects fail and the UI still shows conflicting Active/Inactive states — that indicates an orphaned backend record that only Support can remove. If customer billing or invoice payments are blocked, escalate immediately with the diagnostic package.
[1]: Stripe gateway stuck in corrupted state — manual backend reset required (https://help.zoho.com/portal/en/community/topic/stripe-gateway-stuck-in-corrupted-state-%e2%80%94-manual-backend-reset-required)
[6]: Reconciliation gets easy as Stripe goes 'Intrinsic' with Zoho Books (https://www.zoho.com/blog/books/reconciliation-stripe-integration-with-zoho-books.html)