Puelo Cloud → Institution
Application intake. Risk pack (band, reason codes, flags). Document pointers. Origination lifecycle events. Idempotency per case.
Connectivity
The primary method is not a portal. It is an integration contract: Puelo Cloud delivers the file; the institution returns the verdict and, if a loan exists, the payment events.
Design
Without the return leg there is no serious marketplace: no vintage, no early warning and no real collection support.
Application intake. Risk pack (band, reason codes, flags). Document pointers. Origination lifecycle events. Idempotency per case.
Verdict: approved, declined or pending. Offered terms, if policy allows. Contract identifier. Payment, delinquency, prepayment, charge-off and recovery events.
Working standard
Versioned REST. Event webhooks. Retries with idempotency. An audit trail for every decision.
Client-credentials authentication (OAuth 2.0) and, in production, mTLS. Secrets kept out of code.
Certification environment with synthetic cases. A low-volume pilot may use a console; steady state is the API.
We do not publish endpoints or payloads on this site. The OpenAPI contract is delivered in the institution’s technical onboarding.
Payment events
Performance events return to the marketplace for three uses: origination quality, early warning and collection support defined by the institution. The borrower remains the institution’s.
On-time payment, prepayment, partial payment.
First miss, 30/60 roll, broken promise to pay.
Payoff, charge-off, recovery. Vintage input — not administration of someone else’s book.
Infrastructure
The preparation layer scales with origination and does not impose a fixed cost when traffic is idle. Implementation detail is discussed with the institution’s Architecture team, not as a marketing claim.