Key Terms & Roles
Token Sharing uses a few core terms throughout the Dashboard and API documentation.
Roles
- Donor: The AiPrise customer that has already verified the end customer and shares the permitted record.
- Recipient: The AiPrise customer that receives the shared record and imports it into its own account.
- End customer: The business or individual whose KYC or KYB information is being shared.
Term Meaning
- Connection: A one-directional relationship between two AiPrise customers that allows them to establish sharing agreements. A connection alone does not share data.
- Agreement: The set of rules that defines which customers qualify, what data can be shared, when sharing can happen and which follow-up items can be requested.
- Verification token: An immutable, point-in-time package of one approved record shared under a specific agreement and version.
- Trust level: Defines how much of the Donor's verification work the Recipient can reuse.
- Export: The Donor-side event in which a qualifying record is packaged into a token and sent to the Recipient.
- Import: The Recipient-side process that turns a token into a new profile or session in its AiPrise account.
- RFI catalog: The pre-agreed list of End Merchant RFI questions and documents that the Recipient may request after import.
- End Merchant RFI : A question or document request intended for the end merchant. These requests are defined in the agreement's RFI catalog.
- Donor RFI: A request for information sent directly to the Donor. The Donor can review the request and choose whether to respond, these are independent to the RFI catalog, any question can be asked to the Donor.
Follow-up request / RFI : A Request for Information raised by the Recipient. It may be an End Merchant RFI selected from the agreed catalog or a Donor RFI sent directly to the Donor.
Updated about 20 hours ago
Did this page help you?
