Closing eSign through the NATIVE engine — envelopes actually send now

FeatureSecurityService
Ya
11 Julai 2026, 15:59 UTC
Mwandishi
Kamo
Ahadi ya
9ea5d68

Recording a disclosure e-sign envelope was v1 metadata-only. Now, when the tenant's ESIGN vendor rail resolves to KAMO_NATIVE (per-market integrations config — never hardcoded), the envelope is SENT via ESigService's non-metered platform endpoint (contextType=DISCLOSURE, contextId=envelope id): signers = the loan's URLA borrowers with an email (primary carries memberId), invites go out immediately, and the disclosure row is patched **************** Every non-sendable case stays an honest metadata row with the reason surfaced to the steward in the response (ESIGN_NOT_CONFIGURED / EXTERNAL_VENDOR_PENDING / NO_TEMPLATE / NO_SIGNERS_WITH_EMAIL / NATIVE_SEND_FAILED) — never a fake SENT.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei