Financing, connected to the project.
Keep the customer and proposal in Ridge Arc Network while the financing partner handles the hosted application and financier workflow. Return verified progress to the team managing the job.
The exchange
| Operation | Direction | Purpose |
|---|---|---|
| Create customer | Ridge Arc → partner | Submit approved initial customer fields and retain the partner’s customer identifier. |
| Update proposal | Ridge Arc → partner | Synchronize equipment, system configuration and authorized proposal pricing. |
| Hosted application | Homeowner → provider | Complete the application in a provider-hosted pop-up or approved embed, or through a link sent directly to the homeowner. |
| Application progress | Partner → Ridge Arc | Return status and permitted decision information, correlated to the customer, application and proposal. |
| Document signing | Ridge Arc → partner; status returns | Trigger the existing signing process and track its document version and execution outcome. |
| Welcome call | Partner → Ridge Arc | Return the welcome-call URL for display and the call’s completion state. |
| Installation evidence | Ridge Arc → partner | Send installation updates, required fields, photos and supporting documents using the agreed upload protocol. |
| Quality review and funding | Partner → Ridge Arc | Return review outcomes, correction requirements and distinct funding milestones. |
These are integration responsibilities. Partner-specific endpoint paths, schemas, authentication and event names are agreed during onboarding; use the OpenAPI document for published Ridge Arc endpoints.
Customer data and credit data
Customer names, contact details and service addresses are personal data. Agree the exact create-customer fields, purpose, consent and retention responsibilities before exchanging them. The production design keeps SSNs, dates of birth, income documents and other sensitive credit-application inputs in the provider-hosted application.
Do not include sensitive application inputs in Ridge Arc API payloads, callback URLs, logs or installation photos. The provider agreement must identify which system receives and retains them. Internal equipment costs, margin, compensation and unrelated customer records are outside the financing exchange.
Products, rates and selection
Each financier approves the product information and disclosures shown to homeowners. Establish whether the integration can retrieve and select products, which fields it may display, how long offers remain valid, and when pricing is illustrative versus a personalized offer.
- Confirm eligible trades, states, dealers and financed amounts.
- Agree permitted APR, payment, term, promotion, dealer-fee and risk-based pricing displays with the financier.
- Define selection through the API or the provider-hosted flow, including how the selected product identifier returns to Ridge Arc.
- Revalidate affected financing and signing steps when proposal scope or price changes.
Receiving partner updates
Ridge Arc’s receiver design covers application and offer changes, signing, welcome-call links and outcomes, project progress, QC corrections and funding. The provider’s event contract determines whether one signed receiver or several endpoints are required.
Agree an event identifier, tenant/account binding, external record identifiers, occurrence time, version or sequence, status and allowed data fields. Specify signature verification, secret rotation, retries, duplicate handling, ordering and a read API for reconciliation. A browser redirect is not proof of approval, signing or payment.
Agree before activation
- API documentation, sandbox credentials and a named technical owner.
- Final product catalogue, approved presentation and product-selection mechanism.
- Customer and proposal field mapping, identifiers and revision behavior.
- Signing templates, welcome-call URL lifetime and completion events.
- Installation evidence requirements, QC states and funding conditions.
- Security, data retention, support and end-to-end acceptance criteria.
Production target: https://ridgearc.network/api. Staging / sandbox: https://staging.ridgearc.network/api. See the complete production workflow.