Home inspection software with payment processing that stays clear

Home inspection software with payment processing should make the money side of a job easier to understand, not turn your inspection company into a payment experiment. The job starts with a service, a property, a fee, and an agreement. After the walk, the report is generated from structured findings and selected photos. Payment processing should connect those steps without confusing the client invoice with the software subscription. Inspecta Home 360 is home inspection software. It is not an inspector, it does not make findings, and it does not replace your judgment. Inspecta Home does not inspect houses, and Inspecta Home takes no cut of your client payments.

Use Stripe or PayPal for the client-facing payment path under Firm Billing. The processor handles the sensitive card interaction. Your workspace should retain the invoice, the inspection, the amount, the provider reference, and the resulting paid or unpaid state. That gives the office a useful record without asking the inspection application to become a card vault. Never store raw card numbers. Never paste payment credentials into notes or job chat. Never log them while troubleshooting.

One job should carry one amount

Payment problems often begin before the client ever opens the pay link. If the booking says $425, the estimate says $450, and the invoice says $400, a payment processor cannot repair the trust problem. Define the service, square-footage rules, travel, age, add-ons, discounts, and tax treatment in one fee model. Put the resulting amount on the inspection record before the appointment. An invoice should reflect the job rather than a number someone remembers after the walk.

That model can still support judgment. A commercial property may need a quoted fee. A reinspection may use a different service. A builder may prepay. Record the reason and amount on the job when the price changes. A clear adjustment is better than a private message that leaves the invoice wrong. The client portal should show what the buyer is paying for and what remains due.

The Invoices and payments Help article should be the short operational path: create or confirm the invoice, send the pay link through the portal, wait for the processor, and reconcile the job. Do not create a second invoice merely because the first webhook is delayed. Check the provider reference and the event history first.

Stripe and PayPal are providers, not your source of judgment

Stripe and PayPal can move money and report events. They do not decide whether an inspection was complete, whether an agreement was properly accepted, or whether a report should include a particular observation. Those are domain decisions. The application should isolate provider-specific details behind a billing boundary so the inspection record remains understandable if your firm changes providers.

Payment state should come from an authenticated, authoritative event. A client may send a screenshot. An agent may say the buyer paid. A browser may return to a success page. None of those is enough to mark an invoice paid. Verify the provider event, match it to the intended invoice and amount, and process it idempotently. A retry must not create a duplicate charge, duplicate invoice, or second report release.

Webhooks need the same care as any other trusted boundary. Verify signatures, reject malformed payloads, retain a safe event reference, and make duplicate delivery harmless. Log useful identifiers such as organization, inspection, invoice, provider, and event type. Do not log secrets or full payment credentials. If the event cannot be reconciled, keep the invoice visibly unpaid and give office staff a recovery path.

Keep the agreement and payment gates together

Some firms release a report only after the agreement is signed and the invoice is paid. That is a workflow choice, not a trick. A job-level gate should check both conditions. Payment without an executed agreement leaves the contract step incomplete. A signed agreement without payment leaves the fee at risk. The Hold the report until they sign and pay Help article explains how to configure the hold and communicate it in the portal.

The portal should tell the client what is waiting: sign the agreement, pay the invoice, or complete both. Silence creates more friction than a clear gate. If the client has a question about a line item, the office can correct the invoice on the job rather than sending an attachment from a private mailbox. When the authoritative payment event arrives and the agreement is signed, the release can be automatic or can wait for your firm’s final review.

Turning the gate off for a prepaid job should also be recorded on the job. A builder wire, a recurring commercial account, or a check already reconciled may justify a different path. Keep the invoice and payment note anyway. Historical records matter when an office employee, owner, or client asks what happened months later.

Standards and payment are separate responsibilities

The InterNACHI Standards of Practice are relevant to inspection scope and reporting, not to card storage. A payment screen must not encourage an inspector to skip a limitation, soften a finding, or release a report before the firm’s policy allows it. The ASHI public resources likewise provide professional context rather than a payment specification.

Keep the report model independent from the billing provider. The canonical record is the inspection data: sections, findings, recommendations, media, limitations, agreement, and delivery state. Stripe or PayPal can update the invoice state. They should not rewrite a finding or turn an AI draft into a confirmed finding. Inspecta Copilot may help draft a narrative, but the inspector remains responsible for reviewing and accepting the final language.

Two kinds of billing should be impossible to confuse

Account Billing is what your firm pays Inspecta Home for access to the software. Firm Billing is where your clients pay your firm for inspection services. Account Billing has plans, seats, a trial, and a subscription payment method. Firm Billing has invoices, client pay links, Stripe or PayPal events, and inspection revenue. A clear navigation label prevents an office manager from looking for a client payment in the wrong screen.

Inspecta Home 360 keeps Account Billing simple: Solo is $119, Team is $169, and Scale is $229. Inspecta Copilot is included, extra seats are $25, and each plan starts with a 7-day trial. There is no per-job fee. Client payments are not revenue share; Inspecta Home takes no cut. You pay for seats, and you keep what your clients pay for the inspection.

That distinction also makes support conversations faster. “The client paid” belongs to Firm Billing. “Our card was declined for the subscription” belongs to Account Billing. “The report is still closed” belongs to the job’s agreement and payment gate. A good workspace names the object, the owner, and the next action instead of putting every financial concern under one generic billing label.

Review before you release

Payment processing should reduce uncertainty at the end of the walk. Before release, verify the inspection identity, the recipient permissions, the agreement state, the invoice amount, and the provider event. Confirm that the report version is the one you reviewed. If a webhook is delayed, tell the client that the payment is processing and keep the report closed rather than guessing.

Train office staff on the same runbook. They should be able to see a paid invoice without asking the inspector to forward a receipt. Inspectors should not be expected to collect cards from a ladder or manually change a paid flag in the field. Owners should be able to audit provider events, adjustments, refunds, and report delivery from the job.

The right payment workflow is deliberately unexciting. Create the job, price it consistently, send the agreement and invoice, let Stripe or PayPal process the client payment, verify the event, and release the report according to policy. Keep raw cards out of the application. Keep provider details at the integration boundary. Keep the inspection record authoritative.

For a complete discussion of the two billing screens, read Stripe, PayPal, and the two kinds of billing. For the delivery gate, read hold the PDF until they sign and pay. Home inspection software with payment processing works when the payment workflow supports your business without pretending to be the inspector, the standard, or the source of truth.