What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Scranton, Pennsylvania. After go-live, the Adyen adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
Will this break our existing reports?
No. The adapter writes through a versioned schema layer with full lineage. Existing reports, BI extracts and Excel pivot-tables keep working unchanged while new fields and new objects are added behind the scenes for the Adyen surface.
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.
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.
What happens if Adyen changes their API after we go live?
Our SRE team monitors Adyen 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.
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 Scranton, Pennsylvania, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.