Is this a packaged Stripe connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
What happens if Stripe changes their API after we go live?
Our SRE team monitors Stripe change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
Does it work with our existing Stripe licenses?
Yes — the adapter rides on top of your existing Stripe subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
How long does the Stripe integration take to ship?
Our standard window is thirty days from signed scope to live Stripe adapter in production, plus a one-week monitored stabilization phase. For San Diego, California, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Can the Stripe adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Stripe tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Stripe adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.