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.
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.
Does it work with our existing Chase Payment Solutions licenses?
Yes — the adapter rides on top of your existing Chase Payment Solutions 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.
What happens if Chase Payment Solutions changes their API after we go live?
Our SRE team monitors Chase Payment Solutions 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.
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.
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.