Stripe
Payments infrastructure for card and bank transfers
ProPay integrates with Stripe to execute validated contractor and supplier payments. Stripe is payments infrastructure for card and bank transfers, used by some operators to move money directly rather than through a full ERP payment run. ProPay writes payment instructions in only after an invoice passes authorization.
Stripe is payments infrastructure for card and bank transfers, used by some operators to move money directly rather than through a full ERP payment run. For ProPay, Stripe is downstream of a decision already made, the rail ProPay can use to execute contractor and supplier payments directly. Nothing reaches Stripe until ProPay has validated the invoice against the authorization record that approved the work.
What ProPay sends to Stripe
ProPay validates contractor and supplier invoices against the authorization decision that approved the repair or parts order, the same decision that carried a confidence level and a documented reason at the time it was made. Only invoices that pass that check reach Stripe.
Every payment instruction ProPay sends to Stripe traces back to a specific claim: a validated invoice, an authorization decision made at a known confidence level, and, where a homeowner was involved, the SMS conversation that confirmed the work was done.
That’s what Stripe receives: a payment instruction with the underlying claim, invoice, and authorization already reconciled, not a raw invoice needing separate review.
How the Stripe connection works
ProPay initiates payments through Stripe’s API once an invoice has been validated against the authorization record, so a payment only executes after that check has passed.
A Forward Deployed Engineer maps ProPay’s payment records to Stripe’s chart of accounts and approval structure during deployment, so what lands in Stripe fits how your finance team already reconciles spend.
What stays in Stripe
Stripe continues to own the actual disbursement, reconciliation, and financial reporting exactly as it does today. ProPay supplies validated payment instructions; Stripe remains the system of record for the money itself.
Data handling and security
Payment data written into Stripe comes from a company-specific ProPay instance, one client’s financial data is never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.
Every payment ProPay sends to Stripe is logged alongside the authorization decision and confidence level behind it, so any payment landing in Stripe is traceable back to the claim that generated it.
Deploying the integration
A dedicated Forward Deployed Engineer sets up the Stripe connection to match your chart of accounts and payment approval structure before any live payments flow through it.
Frequently asked questions about ProPay and Stripe
Does ProPay execute payments directly, or does Stripe still control disbursement?
Stripe remains the system of record for actual disbursement and reconciliation; ProPay supplies validated payment instructions once its own authorization check has passed.
How does ProPay connect to Stripe?
ProPay initiates payments through Stripe’s API once an invoice has been validated against the authorization record, so a payment only executes after that check has passed.
Can a payment reach Stripe without authorization?
No. Every invoice is validated against the authorization record before it’s written to Stripe, recommendations outside configured thresholds route to a person first.
