Is this a packaged Adyen 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.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Adyen adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
How long does the Adyen integration take to ship?
Our standard window is thirty days from signed scope to live Adyen adapter in production, plus a one-week monitored stabilization phase. For Schenectady, New York, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Can the Adyen adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Adyen tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
Does it work with our existing Adyen licenses?
Yes — the adapter rides on top of your existing Adyen 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.
Do we own the integration code at the end?
Yes. The Connectify Adyen adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.