OnPoint Warranty
Warranty platform plus managed administration for appliance and electronics programs
ProPay integrates with OnPoint Warranty, a warranty administration platform. OnPoint is a hybrid warranty platform: software plus managed administration, using its ServiceAvenger system to dispatch technicians and process claim payments for appliance and electronics protection programs. ProPay executes the claim on top of it, OnPoint Warranty stays the system of record.
OnPoint is a hybrid warranty platform: software plus managed administration, using its ServiceAvenger system to dispatch technicians and process claim payments for appliance and electronics protection programs. ProPay integrates with OnPoint Warranty so that the claim itself, intake, triage, authorization, parts, and payment, is executed on top of it, rather than replacing it.
What ProPay does with OnPoint Warranty
ProPay reads coverage and claim context from OnPoint Warranty, dispatch assignments, servicer payment records, and claim status, and writes the resulting claim progress back as the work happens. At first notice of loss, ProPay captures claim data 24/7 through web form, chat, SMS, and voice, and validates that coverage against what OnPoint Warranty holds before dispatch.
ProPay’s homeowner triage runs over SMS, capturing model and serial numbers, photos, and symptom detail directly from the homeowner’s phone, with 80 to 83 percent of homeowners responding after a claim is opened. That conversation, not a call center script, is what feeds the record in OnPoint Warranty.
Where a truck roll is warranted, ProPay applies your configured business rules, repair versus replace, auto-approval inside a threshold, then sources parts across suppliers, tracks the order through delivery and return, and validates the resulting invoice against the authorization record before payment releases. Every step writes back to OnPoint Warranty as the record of what happened.
How the OnPoint Warranty connection works
ServiceAvenger handles dispatch and payment execution, and ProPay connects to it as an event and file-exchange partner rather than a pure API integration, matching how OnPoint’s managed-service model actually operates.
Where OnPoint Warranty doesn’t expose a field ProPay needs, a Forward Deployed Engineer builds the mapping during deployment rather than asking OnPoint Warranty to change. Modules go live independently, FNOL, triage, authorization, parts, and payment can each be switched on against OnPoint Warranty one at a time.
What stays in OnPoint Warranty
OnPoint’s managed administration relationship with the carrier, and its own servicer network in ServiceAvenger, are unaffected.
What changes is how much of the routine claim work a person has to do by hand inside OnPoint Warranty. ProPay handles the repetitive execution and routes exceptions to a human, so your team spends its time on the claims that actually need judgment.
Data handling and security
Each ProPay client, including the connection to OnPoint Warranty, runs on a company-specific instance, one carrier’s claim data and contract terms are never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.
Every recommendation ProPay makes against OnPoint Warranty’s data carries a confidence level and the inputs behind it, and is logged. Recommendations above your configured thresholds route to a person rather than executing automatically.
Deploying the integration
A dedicated Forward Deployed Engineer works alongside your team to build and maintain the OnPoint Warranty connection, mapping fields and handling the edge cases specific to how your program is configured inside OnPoint Warranty today.
Frequently asked questions about ProPay and OnPoint Warranty
Does ProPay replace OnPoint Warranty?
No. OnPoint’s managed administration and servicer network through ServiceAvenger continue to operate; ProPay adds automated triage and parts sourcing upstream of dispatch.
How does ProPay connect to OnPoint Warranty?
ServiceAvenger handles dispatch and payment execution, and ProPay connects to it as an event and file-exchange partner rather than a pure API integration, matching how OnPoint’s managed-service model actually operates. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.
What does OnPoint Warranty still control after ProPay is connected?
OnPoint’s managed administration relationship with the carrier, and its own servicer network in ServiceAvenger, are unaffected.
