Pull RHF Go borrower, loan and document data into your CRM, LOS or data lake
RHF Go is the borrower and loan-officer companion app published by Reliant Home Funding, Inc., a Long Island, New York mortgage lender founded in 2010 that operates in roughly half of U.S. states. The package ID com.simplenexus.loans.client.s__56089 shows it is built on the SimpleNexus borrower platform — now part of the nCino Mortgage Suite after nCino's 2022 acquisition. That heritage matters: it means the on-device behaviour follows a documented pattern of loan applications, calculator runs, contact cards and a secure document vault that maps cleanly to OpenFinance-style endpoints.
What we deliver for RHF Go
Every engagement is scoped around the lender's data-residency rules and the borrower's consent. The default drop ships an OpenAPI 3.1 specification, a Python or Node.js reference client, a Postman collection, and a written protocol report explaining how the on-device flows map to the underlying nCino Mortgage API and Reliant Home Funding back-end. Loan officers can plug the output straight into their CRM, while engineering teams keep the specification as the contract for downstream services.
Deliverables checklist
- OpenAPI 3.1 specification covering auth, loan status, calculator, vault and webhook surfaces
- Protocol analysis report (token rotation, request signing, header chain, certificate pinning)
- Runnable source code for borrower login plus two read endpoints in Python and Node.js
- Automated integration tests, fixture data and a Postman collection
- Compliance pack: GLBA / FTC Safeguards mapping, CFPB Regulation X/Z notes, TRID disclosure timing
- Optional hosted gateway with per-call billing for teams that prefer not to operate the bridge themselves
Engagement models
Two ways to work with us, both finished only when you are happy with the result. The first is a flat source-code drop starting at USD 300: we send the runnable API code plus documentation, and you settle the invoice once the build runs against your sandbox. The second is a metered pay-per-call contract: we host the integration, you authenticate against our gateway, and you pay only for the calls your stack consumes — useful for teams running short proofs of concept or seasonal pipeline spikes during the spring buying window.
Data available for integration
Below is the inventory of fields and surfaces our protocol analysis has confirmed inside RHF Go. Every row corresponds to a real screen in the app — affordability calculator, refinance-savings calculator, document upload screen, loan officer contact sheet — and shows the granularity at which it can be exposed through an OpenFinance-style endpoint.
| Data type | In-app source | Granularity | Typical use |
|---|---|---|---|
| Borrower profile | Account / sign-in screen | Per user, includes loan officer pairing | CRM lead enrichment, KYC pre-fill |
| Loan application status | "My loan" milestone view | Per loan, with milestone timestamps | Pipeline reporting, partner-portal mirroring |
| Mortgage calculator scenarios | Affordability, refinance and rent-vs-buy tools | Per run, including assumptions | Lead-scoring, marketing follow-up triggers |
| Document vault metadata | "Scan and upload" screen | Per file: type, size, hash, status | Audit trails, FTC Safeguards evidence |
| Document vault binaries | Phone camera scan flow | Per file, encrypted payload | Long-term archival, eDiscovery, AI parsing |
| Loan officer and agent contacts | "My team" contact card | Per loan, vCard-compatible | CRM sync, partner referral tracking |
| Industry news feed | In-app news module | Per article, headline + URL | Content republishing, engagement metrics |
Typical integration scenarios
RHF Go sits at the borrower edge of a mortgage pipeline. The most valuable integrations are the ones that pull what the borrower sees on their phone and reconcile it with what the loan officer sees in the loan-origination system. Below are the patterns we ship most often.
1. CRM lead enrichment
Whenever a borrower runs the affordability calculator or scans a pay stub, the integration emits a webhook into Salesforce or HubSpot with the loan officer ID and the calculator inputs. Loan officers see warm leads ranked by intent — a borrower who scanned three documents in one evening is treated very differently from one who only opened the news feed. This maps directly onto the OpenFinance "consented event" pattern: the borrower's consent record is attached to every payload.
2. LOS pipeline mirror
The loan status milestones surfaced inside RHF Go are mirrored into Encompass, MeridianLink Mortgage or a custom warehouse. Operations teams stop logging into two systems and reporting becomes a single SQL query. The integration is idempotent, uses cursor-based paging, and supports per-loan deltas so an overnight rebuild costs only a few cents per loan.
3. Document-vault to long-term archive
Scanned documents are duplicated to an S3 or Azure Blob bucket with versioning, object-lock and a manifest that mirrors the in-app filename. The archive becomes evidence for GLBA exams and is consumable by AI parsers that extract income, assets and identity fields. The OpenFinance angle is that the archive can be queried by an authorized aggregator under the same consent that authorized the initial upload.
4. Mortgage marketplace comparison
When a borrower is shopping multiple lenders, an authorized aggregator queries the calculator-output API to compare the RHF Go scenarios with what Rocket Mortgage or SoFi presents. The borrower sees a unified comparison and the lender sees how their pricing ranks. This is the same pattern Mastercard's Open Finance Lending offering applies to payroll and bank-account data.
5. Compliance and audit feed
Every read, write and consent event is emitted to a SIEM with the borrower ID hashed and the loan officer ID intact. Examiners can replay any session, prove that TRID disclosures were delivered inside the regulatory window, and see which fields were exported off-platform. The pipeline is a simple Kinesis or Kafka topic with a retention policy that aligns to CFPB record-keeping rules.
Technical implementation
The reference stack uses bearer tokens minted against the SimpleNexus / nCino Mortgage authorization server, with refresh tokens rotated every fifteen minutes. The same patterns work whether you are consuming the public nCino Mortgage API or a documented borrower-side surface authorized by the lender.
Borrower login — OAuth-style token request
POST /api/v1/rhf-go/auth/token
Content-Type: application/json
{
"client_id": "rhf_go_partner_xxx",
"grant_type": "password",
"username": "borrower@example.com",
"password": "<consent-bound credential>",
"scope": "loan.read documents.read calculator.read"
}
200 OK
{
"access_token": "eyJhbGci...",
"refresh_token": "rt_8f3...",
"token_type": "Bearer",
"expires_in": 900,
"loan_officer_id": "lo_28411"
}
Loan status read
GET /api/v1/rhf-go/loans/{loan_id}/status
Authorization: Bearer <ACCESS_TOKEN>
200 OK
{
"loan_id": "L-2026-0931",
"product": "FHA-30",
"milestone": "underwriting",
"milestone_at": "2026-05-04T18:11:09Z",
"next_action": "Submit updated bank statement",
"officer": { "id": "lo_28411", "name": "J. Carter" },
"agent": { "id": "ag_8821", "name": "M. Lopez" }
}
Document-vault webhook
POST https://your-system/webhooks/rhf-go
X-Signature: sha256=4f6b...
Content-Type: application/json
{
"event": "document.uploaded",
"loan_id": "L-2026-0931",
"document": {
"id": "doc_5a91c",
"type": "pay_stub",
"size_bytes": 482113,
"sha256": "9c0f...",
"uploaded_at": "2026-05-09T13:42:01Z"
},
"consent_id": "cns_abc123"
}
# Verify with HMAC-SHA256 on the raw body
# Reject if signature mismatches or consent_id is revoked.
Compliance & privacy
Mortgage data sits under several overlapping U.S. regimes, and an integration that ignores any of them will fail an examination. We design every RHF Go pipeline against the Consumer Financial Protection Bureau (CFPB) mortgage-resources framework, which includes Regulation X (RESPA) and Regulation Z (Truth in Lending). On the data-protection side the binding rules are the Gramm-Leach-Bliley Act and the FTC Safeguards Rule. HMDA reporting obligations are handled separately at the LOS, but the integration preserves the fields the lender needs to file.
Controls we ship by default
- TLS 1.3 between every hop, AES-256 at rest, certificate pinning on the mobile-side analyzer
- Append-only audit log of upload, download, view and delete events with user and timestamp
- Role-based access: borrower, loan officer, processor, examiner
- Consent records stored alongside every payload, revocable in one call
- Data-minimization checklist mapped to GLBA, FTC Safeguards Rule, CFPB Regulation X / Z and TRID
What we will not do
We do not bypass the app's account security, we do not scrape data without the borrower's written consent, and we do not offer to silently read loan documents on a borrower's behalf. The deliverables are documentation, OpenAPI specifications and source for the lawful pipeline; we walk away from any engagement that would breach the lender's terms of service or the borrower's privacy expectations.
Data flow / architecture
A typical RHF Go pipeline has four nodes. The mobile Client App initiates the borrower session and emits events. An Ingestion Gateway (FastAPI or NestJS) terminates TLS, validates the bearer token against the nCino Mortgage authorization server, and writes a normalized envelope. Storage is split between a relational database for indexed metadata (loans, milestones, calculator runs) and an object store for the document binaries with object-lock and versioning. From there a Distribution Layer exposes consumer-facing surfaces: a REST/GraphQL API for the lender's CRM, a Kafka topic for the data warehouse, and a webhook fan-out for downstream LOS or partner systems. The whole pipeline is idempotent and replayable, so a failed downstream consumer never loses an event.
Market positioning & user profile
RHF Go is a B2B2C borrower app — Reliant Home Funding ships it to its own customers and prospects rather than to a generic audience. Reliant operates in roughly twenty-five U.S. states with an East Coast concentration, offers FHA, VA, conventional, ARM, renovation and reverse-mortgage products, and approves loans typically in 30 to 45 days. The dominant user is a homebuyer or refinancer in the Northeast working with a named loan officer; secondary users are real-estate agents who use the app to track client progress. Both Android and iOS builds are maintained, and the SimpleNexus / nCino heritage means the app is part of a mortgage-tech ecosystem that already powers hundreds of independent lenders nationwide. Mobile-first matters: industry surveys now show that the majority of U.S. mortgage applications start on a phone, and lenders with a usable borrower app capture meaningfully more pipeline than those without.
Screenshots
Snapshots of the in-app surfaces we map to API endpoints. Click any thumbnail to open a larger view.
Similar apps & the broader mortgage integration landscape
RHF Go is one of many borrower-facing surfaces in the U.S. mortgage stack. Teams that integrate RHF Go usually already work with one or more of the platforms below, and unified data exports across them are the most common ask we receive. Each entry is part of the wider ecosystem rather than a competitor to evaluate.
About OpenFinance Lab
We are an independent technical studio specializing in mobile-app interface integration and authorized API delivery for fintech, mortgage and digital-banking clients. Our team has shipped protocol analysis and API source code for U.S., European and APAC lenders for over a decade. For mortgage clients specifically we maintain reference implementations against the nCino Mortgage API, Encompass, MeridianLink and Floify so a new RHF Go drop can reuse field mappings rather than start from zero.
- Mortgage, payments, digital banking and cross-border clearing
- Enterprise API gateways, security reviews, SOC2-ready logging
- Custom Python, Node.js and Go SDKs with test harnesses
- Full pipeline: protocol analysis → build → validation → compliance pack
- Source code delivery from $300 — runnable code plus documentation, paid after you sign off
- Pay-per-call hosted gateway — no upfront cost, ideal for short proofs of concept
Contact
For a quote on an RHF Go integration, or to scope another mortgage app, send us the target package and the data you need:
Engagement workflow
- Scope confirmation — which RHF Go surfaces you need (loan status, vault, calculator, contacts) and the destination system
- Protocol analysis and OpenAPI design (2–5 business days)
- Build and internal validation against a sandbox loan (3–8 business days)
- Documentation, test fixtures and compliance pack (1–2 business days)
- First delivery typically lands in 5–15 business days; lender approvals can extend
FAQ
What do you need from me to start an RHF Go integration?
How long does an RHF Go API delivery take?
Is reverse engineering of a mortgage app legal?
How do you handle GLBA, CFPB and TRID requirements?
📱 Original app overview (appendix)
RHF Go - Reliant Home Funding is the official mobile companion app for Reliant Home Funding, Inc., a Long Island, New York mortgage lender founded in 2010. The app's stated goal is to make the home-loan process simpler for three audiences: prospective homebuyers, current homeowners considering refinancing, and real-estate agents who want faster turnaround for their clients.
- Compare lending scenarios across multiple loan programs (FHA, VA, conventional, ARM, renovation, reverse) to identify the best fit
- Calculate the savings or cost of a refinance against the borrower's current mortgage
- Run an affordability analysis based on current income and monthly expenses
- Scan and upload documents directly from the phone to expedite the loan-approval process
- Quickly access and share the contact details of the assigned Reliant loan officer and real-estate agent
- Stay current on industry news that may affect the borrower's loan
Reliant's published guidance reminds borrowers that the in-app calculators give a useful indication of what homeownership might mean for them, but a customized solution still requires a conversation with their loan officer. The app earns strong reviews on the major lender directories — Reliant scores well on customer experience and affordability in 2026 third-party reviews — and is shipped on both Android and iOS. The package ID com.simplenexus.loans.client.s__56089 reveals that the build is generated on the SimpleNexus platform (now part of nCino Mortgage Suite following nCino's 2022 acquisition), which is the same lineage shared by hundreds of other independent-lender borrower apps in the U.S.