Provider connections

• Disbursement provider. Configure the service that receives approved funding instructions and returns account and event references. Map actual release amounts to the lending account and retain held or uncertain outcomes for investigation. Repeated callbacks must resolve to the same underlying effect.
• Repayment source. Connect the source of confirmed incoming payments. Agree how the source identifies a receipt, verifies its amount and associates it with a loan. Retain the provider event so a repeated delivery can be investigated without allocating the same funds again.
• Insurance provider. Agree the offer and decision handoff for linked insurance applications. Keep the provider’s issuance outcome separate from internal bundled review. Attach the relevant evidence to the lending case through the permitted route.
• Document source. Agree how staff receive appraisals, statements and certificates, then attach the original files with the correct visibility. Use evidence type, provider reference and expiry information to support review. Any automated import is a connection to configure with the document owner.

Assign an owner for each provider connection and test it with representative success, failure and repeated-event cases. Use stable operation identities for funding and servicing actions. A timeout calls for investigation of the existing effect before another instruction is issued. Compare the provider account, application and actual amount with the local records during reconciliation.

Keep credentials in the approved connection setup and restrict who can change them. Decide who resolves a rejected offer, held release or unmatched receipt. Retain the original event references and failed attempts so the next operator can understand the case. Rehearse the full handoff in implementation before enabling routine use.