Tiếng Việt
EnglishApproved
A valid recipient action under the applicable policy.
- Response evidence
- Authentication time
HOW IT WORKS
Send, receive and approve messages
Business flow from the RP to the recipient, response and evidence preservation.
SEND, RECEIVE AND APPROVE
End-to-end flow
From the RP request to recipient response and evidence preservation.
- 1
Initiate request
The RP identifies sender, recipient and content.
- 2
Resolve recipient
Match Subject ID or identity according to policy.
- 3
Create transaction
Assign authentication policy and response deadline.
- 4
Notify across channels
Email, push or another channel only creates a notification.
- 5
Open Web/App
The recipient opens Client Portal or the application.
- 6
Authenticate
Use Passkey or VNeID step-up as required.
- 7
Review content
Display sender, content and deadline.
- 8
Respond
Approve, reject or provide no response.
- 9
Record state
Trusted Delivery emits the corresponding event.
- 10
Preserve evidence
Retain records and support reconciliation.
TRUSTED DELIVERY
Do not conflate states
Notification, handover and response are distinct events.
Email, SMS and push notifications are notification channels only. Sending a notification does not by itself prove that the recipient viewed, received or approved the content.
Rejected
A valid recipient rejection.
- Optional reason
- Not a delivery failure
Expired
No valid response before the deadline.
- RP policy
- Not an implied rejection
Delivery failed
Handover conditions were not met.
- Error code
- Retry policy