Origami Risk
Risk, claims, and policy administration on a single platform
ProPay integrates with Origami Risk, a policy, risk, or CRM platform. Origami Risk is a risk management and claims administration platform built for self-insured programs, TPAs, and risk pools that need policy, claims, and risk data on one system. ProPay authorizes claims against the context it holds and writes decisions back.
Origami Risk is a risk management and claims administration platform built for self-insured programs, TPAs, and risk pools that need policy, claims, and risk data on one system. ProPay reads the context Origami Risk already holds and authorizes the claim against it, writing the decision, and everything that led to it, back as the record of what happened.
What ProPay does with Origami Risk
ProPay captures claim data 24/7 through web form, chat, SMS, and voice, and validates it against the coverage Origami Risk holds, claim files, risk exposure data, and policy records, before authorizing repair versus replace, or approving inside your configured thresholds.
The context that reaches Origami Risk isn’t a call transcript, it’s a structured SMS conversation. ProPay triages the homeowner over text, with 80 to 83 percent responding, and that exchange is what populates the fields Origami Risk needs to authorize the claim correctly the first time.
From there, ProPay sources parts across suppliers, tracks the order, and validates the resulting invoice against the authorization record before payment releases, with every decision written back to Origami Risk alongside the confidence level it was made at.
How the Origami Risk connection works
Origami Risk’s platform API covers claims and risk data, which is where ProPay reads and writes.
Where Origami Risk doesn’t expose a field ProPay needs, a Forward Deployed Engineer builds the mapping during deployment rather than asking Origami Risk to change. Authorization, parts, and payment can go live against Origami Risk independently of each other.
What stays in Origami Risk
Risk exposure tracking and the underlying self-insured program structure stay inside Origami Risk.
What changes is how much of the authorization decision a person has to make by hand. ProPay applies your business rules against the context in Origami Risk and routes only the exceptions to a reviewer.
Data handling and security
The connection to Origami Risk runs on a company-specific ProPay instance, one carrier’s policy and claim data are never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.
Every authorization decision carries a confidence level and the inputs it drew from Origami Risk, and is logged. Decisions above your configured value or confidence thresholds route to a person before anything executes.
Deploying the integration
A dedicated Forward Deployed Engineer works with your team to build and maintain the Origami Risk connection, mapping the specific fields and authorization rules your program already runs on.
Frequently asked questions about ProPay and Origami Risk
Does ProPay replace Origami Risk?
No. Origami Risk remains the system of record for the underlying policy and case data; ProPay executes the authorization decision and the work that follows it.
How does ProPay connect to Origami Risk?
Origami Risk’s platform API covers claims and risk data, which is where ProPay reads and writes. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.
Are authorization decisions against Origami Risk auditable?
Yes. Every decision carries a confidence level and the specific inputs from Origami Risk it was based on, and is logged for review.
