Skip to main content

Devlog: 2026-03-17 — LOS Integration Discovery

What Happened​

During discussion about the full WTPO workflow, identified that the LOS integration point (pushing purchased loans into Encompass) belongs in PSSaaS, not in PSX or the Desktop App.

Key Discovery​

When a trade is confirmed on PSX, loans need to enter Encompass (WTPO's LOS) for:

  • Document custody and compliance
  • Servicing setup
  • Investor reporting and regulatory audit
  • Accounting (payables to seller, receivables from buyer)

Why PSSaaS Owns This Integration​

  • PSSaaS Pipeline already receives the trade webhook — it has the loan data
  • The Pipeline spec already calls for bidirectional LOS integration
  • Different principals may use different LOSs — PSSaaS abstracts this per tenant
  • PSX should not know or care which LOS each principal uses

Integration Architecture (Planned)​

PSX: trade confirmed
  → PSSaaS Pipeline: receives webhook
    → PSSaaS LOS Integration: pushes loans to Encompass via REST API
    → Stores Encompass loan GUID for cross-reference
    → Later: receives settlement/delivery confirmations back from Encompass

Planned Capability​

A future spec — "LOS Integration (Encompass)" — under the Pipeline module. Will cover:

  • Encompass Partner Connect (EPC) REST API integration
  • Loan data mapping from PSSaaS Pipeline format to Encompass loan format
  • Cross-reference storage (PSSaaS pipeline_loan_id ↔ Encompass loan GUID)
  • Bidirectional sync (push loans in, receive status updates back)
  • Tenant-configurable LOS selection (Encompass for WTPO, other LOSs for other principals)

Not a current priority — WTPO is still setting up their PSX workflow. This becomes relevant when trades start executing.