| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...
The R&R contain the established rules and also a description of the Roles and activities that parties involved in the Product can carry out. In that context, Currence issues Licence and Certificate Agreements/wiki/spaces/SPEEL/pages/50561125.
Currence helps safeguard the efficiency, quality (including reliability and image) and the integrity of its Product. Currence carries out the following tasks:
...
Currence has no direct relationship with a Merchant. The Acquirer or DISP is responsible for onboarding a Merchant, in accordance with the requirements as stated in the R&R annex '/wiki/spaces/SPEEL/pages/68747408' and 'Guidelines and Use of Product Logos/wiki/spaces/SPEEL/pages/68747465' as well as the /wiki/spaces/SPEEL/pages/33731039.
...
A platform as a Merchant within the iDIN Scheme is a party platform that provides a service or software to its business customers (hereinafter sub_Merchants). The User can deliver its iDIN data via the platform to the sub_Merchants of the platform (Merchant). These sub_Merchants will make use of the platform's iDIN service and can offer iDIN as a Product to the User.A platform as , in which the providing of ID services is not its core business but a limited ancillary service as part of the full range of services.
The below mentioned examples can be considered as a iDIN (platform) Merchant (not exhaustive):
software administration packages taking out loans / mortgages / insurances to their business customers;
payroll administration software packages;
software packages for the administration of nurseries and comparable industries.
These sub_Merchants must be related to the same industry, or make use of the same software package for a service, which is offered by the iDIN (platform) Merchant.
An iDIN (platform) Merchant has the advantage that all its subits sub_Merchants do not have to enter into a separate iDIN contract with a DISP or Acquirer, but they , but an iDIN (platform) Merchant can enter into a single contract with the platform (Merchant) its Acquirer or DISP for all services offered by the platform.
Examples of platforms (not exhaustive):
taking out loans / mortgages / insurances;
payroll administration software packages;
software packages for the administration of nurseries.
NB An Acquirer or DISP must report a platform to Currence.
The environment of the sub_Merchant can be reached after iDIN verification via the platform (Merchant). by theiDIN (platform) Merchant.
The sub_Merchant chooses to join use the services the iDIN (platform) Merchant, which allows Users to access the online environment of sub_Merchant. The sub_The iDIN (platform) Merchant hereby determines the purposes and means for the processing of Personal Data, whereby the sub_Merchant chooses to process the personal data of their Users via the verification system of the iDIN (platform) Merchant and iDIN for verification purposes.
...
The platform as an iDIN Merchant only fulfills the role of intermediary (with access to iDIN) (platform = processor);
...
The environment of the sub_Merchant can be reached after iDIN verification via the iDIN (platform) Merchant.
NB An Acquirer or DISP must report an iDIN (platform) Merchant to Currence.
4.3 Earnings model
The earnings model is based on the mutual contractual relationships between the parties involved in the Scheme, see Figure 3. Acquirers and Issuers (with a Licence Agreement) and DISPs (Certificate Holder) offer the Product to the market commercially. They can charge their User or Merchant a fee for this, the interpretation of which is at the Institutions' discretion. The Institutions must draw up a mutual agreement on a Fee, if applicable. Currence charges its Licencees and Certificate Holders a fee.
...
For both the Issuing and Acquiring Domain, the Licencees must comply with the relevant laws and regulations that apply to them, and with the rules and guidelines prescribed by the regulators in the country where the organisation is based.
5.1.1 Licence and Certificate structure
Institutions wishing to join one of the Schemes must conclude a Licence or Certificate Agreement with Currence:
...
General Notes (this document)
This gives an outline description of the Schemes, with the Roles and Products associated with them.Agreements
Licence Agreement/wiki/spaces/SPEEL/pages/50561125: The agreement concluded by a Licencee with Currence after successfully completing the Certification Procedure for the Scheme or Schemes in which it wishes to take part. The Fees annex also applies here;
Certificate Agreement/wiki/spaces/SPEEL/pages/50561125: The agreement concluded by a Certificate Holder with Currence after successfully completing the Certification Procedure for the Scheme or Schemes in which it wishes to take part. The Fees annex also applies here;Accreditation Agreement: The agreement concluded by an Accredited Party with Currence after successfully completing the accreditation procedure for the Product iDEAL or eMandates.General Regulations
/wiki/spaces/SPEEL/pages/66093148: description and applicability of the General Regulations;
/wiki/spaces/SPEEL/pages/66093191: definition of terms in the Online R&R that start with a capital letter;
/wiki/spaces/SPEEL/pages/66093222: duties and powers of the members of the Council of Licencees;
/wiki/spaces/SPEEL/pages/65831020: description of how parties may communicate in relation to the Schemes;
/wiki/spaces/SPEEL/pages/66093279: description of how Currence implements changes to the R&R;
/wiki/spaces/SPEEL/pages/66093292: description of when Currence may impose a penalty on a Licencee or Certificate Holder. /wiki/spaces/SPEEL/pages/66093292 also applies here;
/wiki/spaces/SPEEL/pages/66093320: description of how and when a Bilateral Fee is applicable.Acceptance Regulations and Certification Procedure
Acceptance Regulations: description of the procedure established by Currence that is used to assess whether an Applicant may be accepted to the Scheme concerned in order to be able to fulfil the Role it has applied for;
/wiki/spaces/SPEEL/pages/65994808: description of the procedure established by Currence that is used to assess whether an Applicant meets the conditions set out in the R&R on the basis of a /wiki/spaces/SPEEL/pages/59277442 (CSA) it has itself carried out.R&R Provisions
/wiki/spaces/SPEEL/pages/65929472: set of provisions that a Licencee who is certified for this Role is obliged to comply with. For iDIN there are additional requirements for the Framework iDIN and Data Quality iDIN;
/wiki/spaces/SPEEL/pages/67633182: set of provisions that a Certificate Holder who is certified for this Role is obliged to comply with;
/wiki/spaces/SPEEL/pages/67567687: set of provisions that a Licencee who is certified for this Role is obliged to comply with;
/wiki/spaces/SPEEL/pages/67600565: set of provisions that a Certificate Holder who is certified for this Role is obliged to comply with;
/wiki/spaces/SPEEL/pages/67764352: set of provisions that a Certificate Holder who is certified for this Role is obliged to comply with; This Role applies only to iDIN;
/wiki/spaces/SPEEL/pages/68026369: set of provisions for, among other things, identifying Users to whom an Issuer Licencee is obliged to comply to. These requirements apply only to the iDIN Scheme.
/wiki/spaces/SPEEL/pages/68780088: set of provisions for the dataset which is used within the iDIN Scheme to whom an Issuer Licencee is obliged to comply to. These requirements apply only to the iDIN Scheme.
/wiki/spaces/SPEEL/pages/68780096: set of provisions regarding to the privacy of the data within iDIN, which all licensed and certified iDIN parties are obliged to comply to. These requirements apply only to the iDIN Scheme.
/wiki/spaces/SPEEL/pages/567476279: set of provisions for DISP's who want to offer the iDIN Product variant 'iDIN Signature'.
R&R Annexes
/wiki/spaces/SPEEL/pages/33731039
The Technical Standards consist of the following components:
For iDIN:
iDx Documentation SuiteiDx 001 Cover document: an overview of the various documents that form the Technical Standard;
iDx_010 Protocol: vsetting down the technical aspects of the Technical Standards with regard to messages for the relevant Product front-end implementation, to which the parties involved in the Scheme must adhere based on their Roles of Issuer and Acquirer;
iDx_025 Messages between Acquirer and Issuer: an overview of the iDx messages exchanged between the Validation Service Provider and the Routing Service Provider;
iDx_035 Messages between Merchant and Acquirer: an overview of the iDx messages exchanged between Merchants and Routing Service Providers;
Implementation Guidelines
A document that describes guidelines concerning the implementation and content of the messages for Issuers and Acquirers.
Software libraries
A piece of programming language/software to simplify the technical implementations of Merchants
Merchant Implementatie Gids (MIG):
A derivative of the Technical Standard. The MIG gives an overview of the guidelines and recommendations that are relevant for the implementation of the Product concerned by Merchants, CPSPs or DISPs. A Licencee can incorporate relevant Technical Standard matters as information in its own publication of the MIG. The MIG is issued by the Acquirer to the Merchant or DISP.
...