How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Chase Payment Solutions 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 Chase Payment Solutions integration take to ship?
Our standard window is thirty days from signed scope to live Chase Payment Solutions adapter in production, plus a one-week monitored stabilization phase. For Champaign, Illinois, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Do we own the integration code at the end?
Yes. The Connectify Chase Payment Solutions 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.
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 Chase Payment Solutions surface.
Can the Chase Payment Solutions adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Chase Payment Solutions tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Champaign, Illinois. After go-live, the Chase Payment Solutions 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.