Jira
Issue tracking for engineering and integration workstreams
ProPay integrates with Jira for tracking the integration build itself, not claims, not claims data. Jira is issue tracking used by engineering teams, including the work of building and maintaining a ProPay integration. It's a coordination layer around ProPay's integration and exceptions, not a claims channel.
Jira is issue tracking used by engineering teams, including the work of building and maintaining a ProPay integration. This isn’t where claim data lives, Jira is where your team coordinates around ProPay: tracking the integration build itself, not claims.
What ProPay does with Jira
Your Forward Deployed Engineer can track the specific connector work, field mappings, edge cases, go-live milestones for each module, as tickets in your team’s existing Jira project, so your engineers see the integration build the same way they see any other engineering work.
Nothing about claim data, parts sourcing, or payment execution routes through Jira. It’s purely operational, the coordination layer around the integration and around exceptions that need a person’s attention, not a channel for claim records themselves.
How the Jira connection works
Integration work is tracked in a Jira project your team provides access to during deployment.
This is set up once, early in deployment, alongside the rest of the Jira configuration your team already maintains, it isn’t a separate ongoing integration to manage.
What stays in Jira
Jira continues to run exactly as it does for every other team and project already inside it. ProPay adds one more source of notifications or tracked work, using the structure your team has already built.
Data handling and security
Anything ProPay posts into Jira, an escalation, a deployment update, is a notification about activity happening on your company-specific ProPay instance, not a copy of underlying claim or customer data. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.
The claim recommendations behind any escalation posted to Jira carry their own confidence level and audit trail inside ProPay, independent of whatever your team tracks in Jira.
Setting this up
A dedicated Forward Deployed Engineer sets up the Jira connection early in deployment, working with whoever on your team owns that workspace.
Frequently asked questions about ProPay and Jira
Does claim data flow into Jira?
No. Jira is used for operational coordination, escalations, deployment tracking, documentation, not claim, parts, or payment data.
How does ProPay connect to Jira?
Integration work is tracked in a Jira project your team provides access to during deployment.
Is Jira required to use ProPay?
No. Jira is an optional coordination layer some clients use during deployment and ongoing operation; it isn’t required for ProPay’s core claims functionality.
