What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Phoenix, Arizona. After go-live, the PayPal 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.
Is this a packaged PayPal 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 PayPal changes their API after we go live?
Our SRE team monitors PayPal 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 is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The PayPal adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
Can the PayPal adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your PayPal tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
How long does the PayPal integration take to ship?
Our standard window is thirty days from signed scope to live PayPal adapter in production, plus a one-week monitored stabilization phase. For Phoenix, Arizona, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.