From 859234bc664c2106adedf78b5a75901cd776febe Mon Sep 17 00:00:00 2001 From: Henk Kodde Date: Thu, 21 Nov 2019 15:08:25 +0200 Subject: [PATCH 1/6] - Removed the suppression of ToC pages on gh-pages. - Removed the document ToC to eliminate duplication. --- documents/platform-operating-guideline.md | 65 --------------------- documents/scheme-business-rules.md | 37 ------------ documents/scheme-key-choices.md | 35 ----------- documents/scheme-participation-agreement.md | 11 ---- documents/scheme-uniform-glossary.md | 3 - 5 files changed, 151 deletions(-) diff --git a/documents/platform-operating-guideline.md b/documents/platform-operating-guideline.md index 5a65547..d855fbb 100644 --- a/documents/platform-operating-guideline.md +++ b/documents/platform-operating-guideline.md @@ -1,6 +1,3 @@ ---- -showToc: false ---- # Platform Operating Guideline Template - Version: 2.0 @@ -39,68 +36,6 @@ This document is a template for such a Platform Operating Guideline. Many provis The Business Rules template that is part of this project can be used independent of a scheme's choice of platform. This Platform Operating Guideline is more specific to the use of Mojaloop as a platform. -## **Table of Contents -- Platform Operating Guideline Template** - -[1 - About This Document](#1-About-This-Document) - -[1.1 - Scheme Services](#1.1-Scheme-Services) - -[1.2 - Open API Specification](#1.2-Open-API-Specification) - -[1.3 - Scheme Use Cases](#1.3-Scheme-Use-Cases) - -[1.4 - Scheme Supported Identifiers](#1.4-Scheme-Supported-Identifiers) - -[2 - The Account Lookup Service](#2-The-Account-Lookup-Service) - -[2.1 - Description of the Account Lookup Service](#2.1-Description-of-the-Account-Lookup-Service) - -[2.2 - Party Request](#2.2-Party-Request) - -[2.3 - Parties Query](#2.3-Parties-Query) - -[2.4 - Parties Query Response](#2.4-Parties-Query-Response) - -[3 - The Quote Service](#3-The-Quote-Service) - -[3.1 - Description of the Quote Service](#3.1-Description-of-the-Quote-Service) - -[3.2 - Quote Request](#3.2-Quote-Request) - -[3.3 - Quote Response](#3.3-Quote-Response) - -[4 - The Transfer Service](#4-The-Transfer-Service) - -[4.1 - Description of the Transfer Service](#4.1-Description-of-the-Transfer-Service) - -[4.2 - Transfer Request](#4.2-Transfer-Request) - -[4.3 - Request to Pay](#4.3-Request-to-Pay) - -[5 - The Settlement Service](#5-The-Settlement-Service) - -[5.1 - Transfer Settlement](#5.1-Transfer-Settlement) - -[5.2 - Fee Settlement: Processing Fees](#5.2-Fee-Settlement:-Processing-Fees) - -[5.3 - Fee Settlement: Interchange Fees](#5.3-Fee-Settlement:-Interchange-Fees) - -[6 - The Scheme Management Service](#6-The-Scheme-Management-Service) - -[6.1 - Description of the Scheme Management Service](#6.1-Description-of-the-Scheme-Management-Service) - -[6.2 - The Registration Process](#6.2-The-Registration-Process) - -[6.3 - DFSP Customer Service](#6.3-DFSP-Customer-Service) - -[6.4 - Scheme System Management](#6.4-Scheme-System-Management) - -[7 - The Fraud Management Service](#7-The-Fraud-Management-Service) - -[8 - Appendix: Scheme Supported Use Cases and System Parameters](#8-Appendix:-Scheme-Supported-Use-Cases-and-System-Parameters) - -[9 - Appendix: Merchant Category Codes](#9-Appendix:-Merchant-Category-Codes) - ## 1. About This Document These Platform Operating Guidelines specify operational and technical requirements for DFSPs and for the Scheme. From time to time the Scheme will issue additional Operational Bulletins, which will describe additional operational features of the Scheme and specify additional requirements of DFSPs. diff --git a/documents/scheme-business-rules.md b/documents/scheme-business-rules.md index 2e66771..4ec5f9b 100644 --- a/documents/scheme-business-rules.md +++ b/documents/scheme-business-rules.md @@ -1,6 +1,3 @@ ---- -showToc: false ---- # Scheme Business Rules Template - Version: 4.0 @@ -39,40 +36,6 @@ Before Business Rules are written, Schemes need to make major business decisions Scheme Business Rules Template -## **Table of Contents** - -[1 - About These Scheme Business Rules](#1.-about-these-scheme-business-rules) - -[2 - Scheme Goals](#2.-scheme-goals) - -[3 - Participation in Scheme](#3.-participation-in-scheme) - -[4 - Scheme Business Rules](#4.-scheme-business-rules) - -[5 - Responsibilities and Obligations of the Scheme](#5.-responsibilities-and-obligations-of-the-scheme) - -[6 - Participant Responsibilities and Obligations of Participants](#6.-participant-responsibilities-and-obligations-of-participants) - -[7 - Liability - Allocation of Responsibilities](#7.-liability---allocation-of-responsibilities) - -[8 - Security, Risk Management, and Data Confidentiality](#8.-security-risk-management-and-data-confidentiality) - -[9 - Scheme Platform and Services](#9.-scheme-platform-and-services) - -[10 - Exception Management](#10.-exception-management) - -[11 - Appendix: Associated Documents](#11.-appendix:-associated-documents) - -[12 - Appendix: Onboarding and Exit Processes](#12.-appendix:-onboarding-and-exit-processes) - -[13 - Appendix: Scheme Services](#13.-appendix:-scheme-services) - -[14 - Appendix: Scheme Supported Use Cases](#14.-appendix:-scheme-supported-use-cases) - -[15 - Appendix: Scheme Fee Schedule](#15.-appendix:-scheme-fee-schedule) - -[16 - Appendix: Risk Management, Security, Privacy, and Service Standards](#16.-appendix:-risk-management-security-privacy-and-service-standards) - ## **A Guide to This Document** Section Headings and bulleted entries underneath section headings are actual proposed wording, or suggested sections for a rules document. Text in italics are comments which can be used when a scheme drafts the actual language of a rules document. diff --git a/documents/scheme-key-choices.md b/documents/scheme-key-choices.md index 6065eb4..0f0cd44 100644 --- a/documents/scheme-key-choices.md +++ b/documents/scheme-key-choices.md @@ -1,6 +1,3 @@ ---- -showToc: false ---- # Scheme Key Choices - Version: 5.0 @@ -39,38 +36,6 @@ Schemes implementing Mojaloop will need to make a number of business choices abo Although this document is written as a contribution to the Mojaloop community, the issues described here are pertinent to any Level One aligned payments system, regardless of the technical implementation chosen. -## **Choices Described in this Document** - -[1 - Choice: Ownership of Scheme](#1.-choice:-ownership-of-scheme) - -[2 - Choice: Participation in the Scheme](#2.-choice:-participation-in-the-scheme) - -[3 - Choice: Relationship of Scheme to Platform](#3.-choice:-relationship-of-scheme-to-platform) - -[4 - Choice: Scope of Scheme Rules and Scheme Rules Authority](#4.-choice:-scope-of-scheme-rules-and-scheme-rules-authority) - -[5 - Choice: Use Cases](#5.-choice:-use-cases) - -[6 - Choice: QR Codes](#6.-choice:-qr-codes) - -[7 - Choice: Payments Addressing](#7.-choice:-payments-addressing) - -[8 - Choice: Interparticipant Settlement](#8.-choice:-interparticipant-settlement) - -[9 - Choice: Tiered Access](#9.-choice:-tiered-access) - -[10 - Choice: Scheme Fees and End User Pricing](#10.-choice:-scheme-fees-and-end-user-pricing) - -[11 - Choice: Brand Management](#11.-choice:-brand-management) - -[12 - Choice: Scheme Connections to Other Schemes](#12.-choice:-scheme-connections-to-other-schemes) - -[13 - Choice: Scheme Use by Other FSP's](#13.-choice:-scheme-use-by-other-fsp's) - -[14 - Choice: Scheme Risk Management Standards](#14.-choice:-scheme-risk-management-standards) - -[15 - Choice: Exception Management](#15.-choice:-exception-management) - ## 1. Choice: Ownership of Scheme The Scheme is the entity that writes the rules for the payment system. As such, the scheme controls multiple aspects of the delivery of scheme services, including how the technical and operational platform will be delivered to participating DFSPs. Common models in for Scheme ownership in the payments industry include: diff --git a/documents/scheme-participation-agreement.md b/documents/scheme-participation-agreement.md index d14bf29..3f6760c 100644 --- a/documents/scheme-participation-agreement.md +++ b/documents/scheme-participation-agreement.md @@ -1,6 +1,3 @@ ---- -showToc: false ---- # Scheme Participation Agreement Template - Version: 3.0 @@ -29,14 +26,6 @@ The following documents are part of the project: - Uniform Glossary -# Table Of Content - -[1 - Participation Application and Agreement](#1-participation-application-and-agreement) - -[1.1 - Applicable Law](#1.1-applicable-law) - -[1.2 - Signature Block: Applicant and Scheme](#1.2-signature-block:-applicant-and-scheme) - # 1. Participation Application and Agreement __ diff --git a/documents/scheme-uniform-glossary.md b/documents/scheme-uniform-glossary.md index ccb3369..0c4aec0 100644 --- a/documents/scheme-uniform-glossary.md +++ b/documents/scheme-uniform-glossary.md @@ -1,6 +1,3 @@ ---- -showToc: false ---- # Uniform Glossary Template - Version: 1.0 From fcbace38b7916e063a06cc7921cf254f7062bead Mon Sep 17 00:00:00 2001 From: Henk Kodde Date: Thu, 21 Nov 2019 15:43:20 +0200 Subject: [PATCH 2/6] - Update release to v8.5.2 - Update circleCI to use { .Revision } instead instead of { checksum "package.json" } (recommended by Miguel - https://github.com/mojaloop/documentation/pull/135) - Restored ToC in documents - do not want to alter the current document content. --- .circleci/config.yml | 8 +-- documents/platform-operating-guideline.md | 62 +++++++++++++++++++++ documents/scheme-business-rules.md | 34 +++++++++++ documents/scheme-key-choices.md | 32 +++++++++++ documents/scheme-participation-agreement.md | 8 +++ package-lock.json | 2 +- package.json | 2 +- 7 files changed, 142 insertions(+), 6 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index dc2f575..9154e0e 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -96,7 +96,7 @@ jobs: name: Delete build dependencies command: apk del build-dependencies - save_cache: - key: dependency-cache-{{ checksum "package.json" }} + key: dependency-cache-{{ .Revision }} paths: - node_modules @@ -123,13 +123,13 @@ jobs: curl -L https://sourceforge.net/projects/plantuml/files/plantuml.${PLANTUML_VERSION}.jar/download -o plantuml.jar - restore_cache: keys: - - dependency-cache-{{ checksum "package.json" }} + - dependency-cache-{{ .Revision }} - run: name: Build Gitbooks command: | npm run gitbook:build - save_cache: - key: build-cache-{{ checksum "package.json" }} + key: build-cache-{{ .Revision }} paths: - _book @@ -154,7 +154,7 @@ jobs: echo 'export GIT_CI_EMAIL=$GIT_CI_EMAIL' >> $BASH_ENV - restore_cache: keys: - - build-cache-{{ checksum "package.json" }} + - build-cache-{{ .Revision }} - run: <<: *defaults_git_identity_setup - run: diff --git a/documents/platform-operating-guideline.md b/documents/platform-operating-guideline.md index d855fbb..48f7d26 100644 --- a/documents/platform-operating-guideline.md +++ b/documents/platform-operating-guideline.md @@ -36,6 +36,68 @@ This document is a template for such a Platform Operating Guideline. Many provis The Business Rules template that is part of this project can be used independent of a scheme's choice of platform. This Platform Operating Guideline is more specific to the use of Mojaloop as a platform. +## **Table of Contents -- Platform Operating Guideline Template** + +[1 - About This Document](#1-About-This-Document) + +[1.1 - Scheme Services](#1.1-Scheme-Services) + +[1.2 - Open API Specification](#1.2-Open-API-Specification) + +[1.3 - Scheme Use Cases](#1.3-Scheme-Use-Cases) + +[1.4 - Scheme Supported Identifiers](#1.4-Scheme-Supported-Identifiers) + +[2 - The Account Lookup Service](#2-The-Account-Lookup-Service) + +[2.1 - Description of the Account Lookup Service](#2.1-Description-of-the-Account-Lookup-Service) + +[2.2 - Party Request](#2.2-Party-Request) + +[2.3 - Parties Query](#2.3-Parties-Query) + +[2.4 - Parties Query Response](#2.4-Parties-Query-Response) + +[3 - The Quote Service](#3-The-Quote-Service) + +[3.1 - Description of the Quote Service](#3.1-Description-of-the-Quote-Service) + +[3.2 - Quote Request](#3.2-Quote-Request) + +[3.3 - Quote Response](#3.3-Quote-Response) + +[4 - The Transfer Service](#4-The-Transfer-Service) + +[4.1 - Description of the Transfer Service](#4.1-Description-of-the-Transfer-Service) + +[4.2 - Transfer Request](#4.2-Transfer-Request) + +[4.3 - Request to Pay](#4.3-Request-to-Pay) + +[5 - The Settlement Service](#5-The-Settlement-Service) + +[5.1 - Transfer Settlement](#5.1-Transfer-Settlement) + +[5.2 - Fee Settlement: Processing Fees](#5.2-Fee-Settlement:-Processing-Fees) + +[5.3 - Fee Settlement: Interchange Fees](#5.3-Fee-Settlement:-Interchange-Fees) + +[6 - The Scheme Management Service](#6-The-Scheme-Management-Service) + +[6.1 - Description of the Scheme Management Service](#6.1-Description-of-the-Scheme-Management-Service) + +[6.2 - The Registration Process](#6.2-The-Registration-Process) + +[6.3 - DFSP Customer Service](#6.3-DFSP-Customer-Service) + +[6.4 - Scheme System Management](#6.4-Scheme-System-Management) + +[7 - The Fraud Management Service](#7-The-Fraud-Management-Service) + +[8 - Appendix: Scheme Supported Use Cases and System Parameters](#8-Appendix:-Scheme-Supported-Use-Cases-and-System-Parameters) + +[9 - Appendix: Merchant Category Codes](#9-Appendix:-Merchant-Category-Codes) + ## 1. About This Document These Platform Operating Guidelines specify operational and technical requirements for DFSPs and for the Scheme. From time to time the Scheme will issue additional Operational Bulletins, which will describe additional operational features of the Scheme and specify additional requirements of DFSPs. diff --git a/documents/scheme-business-rules.md b/documents/scheme-business-rules.md index 4ec5f9b..012c428 100644 --- a/documents/scheme-business-rules.md +++ b/documents/scheme-business-rules.md @@ -36,6 +36,40 @@ Before Business Rules are written, Schemes need to make major business decisions Scheme Business Rules Template +## **Table of Contents** + +[1 - About These Scheme Business Rules](#1.-about-these-scheme-business-rules) + +[2 - Scheme Goals](#2.-scheme-goals) + +[3 - Participation in Scheme](#3.-participation-in-scheme) + +[4 - Scheme Business Rules](#4.-scheme-business-rules) + +[5 - Responsibilities and Obligations of the Scheme](#5.-responsibilities-and-obligations-of-the-scheme) + +[6 - Participant Responsibilities and Obligations of Participants](#6.-participant-responsibilities-and-obligations-of-participants) + +[7 - Liability - Allocation of Responsibilities](#7.-liability---allocation-of-responsibilities) + +[8 - Security, Risk Management, and Data Confidentiality](#8.-security-risk-management-and-data-confidentiality) + +[9 - Scheme Platform and Services](#9.-scheme-platform-and-services) + +[10 - Exception Management](#10.-exception-management) + +[11 - Appendix: Associated Documents](#11.-appendix:-associated-documents) + +[12 - Appendix: Onboarding and Exit Processes](#12.-appendix:-onboarding-and-exit-processes) + +[13 - Appendix: Scheme Services](#13.-appendix:-scheme-services) + +[14 - Appendix: Scheme Supported Use Cases](#14.-appendix:-scheme-supported-use-cases) + +[15 - Appendix: Scheme Fee Schedule](#15.-appendix:-scheme-fee-schedule) + +[16 - Appendix: Risk Management, Security, Privacy, and Service Standards](#16.-appendix:-risk-management-security-privacy-and-service-standards) + ## **A Guide to This Document** Section Headings and bulleted entries underneath section headings are actual proposed wording, or suggested sections for a rules document. Text in italics are comments which can be used when a scheme drafts the actual language of a rules document. diff --git a/documents/scheme-key-choices.md b/documents/scheme-key-choices.md index 0f0cd44..7b1abdc 100644 --- a/documents/scheme-key-choices.md +++ b/documents/scheme-key-choices.md @@ -36,6 +36,38 @@ Schemes implementing Mojaloop will need to make a number of business choices abo Although this document is written as a contribution to the Mojaloop community, the issues described here are pertinent to any Level One aligned payments system, regardless of the technical implementation chosen. +## **Choices Described in this Document** + +[1 - Choice: Ownership of Scheme](#1.-choice:-ownership-of-scheme) + +[2 - Choice: Participation in the Scheme](#2.-choice:-participation-in-the-scheme) + +[3 - Choice: Relationship of Scheme to Platform](#3.-choice:-relationship-of-scheme-to-platform) + +[4 - Choice: Scope of Scheme Rules and Scheme Rules Authority](#4.-choice:-scope-of-scheme-rules-and-scheme-rules-authority) + +[5 - Choice: Use Cases](#5.-choice:-use-cases) + +[6 - Choice: QR Codes](#6.-choice:-qr-codes) + +[7 - Choice: Payments Addressing](#7.-choice:-payments-addressing) + +[8 - Choice: Interparticipant Settlement](#8.-choice:-interparticipant-settlement) + +[9 - Choice: Tiered Access](#9.-choice:-tiered-access) + +[10 - Choice: Scheme Fees and End User Pricing](#10.-choice:-scheme-fees-and-end-user-pricing) + +[11 - Choice: Brand Management](#11.-choice:-brand-management) + +[12 - Choice: Scheme Connections to Other Schemes](#12.-choice:-scheme-connections-to-other-schemes) + +[13 - Choice: Scheme Use by Other FSP's](#13.-choice:-scheme-use-by-other-fsp's) + +[14 - Choice: Scheme Risk Management Standards](#14.-choice:-scheme-risk-management-standards) + +[15 - Choice: Exception Management](#15.-choice:-exception-management) + ## 1. Choice: Ownership of Scheme The Scheme is the entity that writes the rules for the payment system. As such, the scheme controls multiple aspects of the delivery of scheme services, including how the technical and operational platform will be delivered to participating DFSPs. Common models in for Scheme ownership in the payments industry include: diff --git a/documents/scheme-participation-agreement.md b/documents/scheme-participation-agreement.md index 3f6760c..de9a7e9 100644 --- a/documents/scheme-participation-agreement.md +++ b/documents/scheme-participation-agreement.md @@ -26,6 +26,14 @@ The following documents are part of the project: - Uniform Glossary +# Table Of Content + +[1 - Participation Application and Agreement](#1-participation-application-and-agreement) + +[1.1 - Applicable Law](#1.1-applicable-law) + +[1.2 - Signature Block: Applicant and Scheme](#1.2-signature-block:-applicant-and-scheme) + # 1. Participation Application and Agreement __ diff --git a/package-lock.json b/package-lock.json index ce14a6b..52d8c13 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,6 +1,6 @@ { "name": "mojaloop-business-docs", - "version": "8.5.1", + "version": "8.5.2", "lockfileVersion": 1, "requires": true, "dependencies": { diff --git a/package.json b/package.json index f79ded0..636f5f7 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "mojaloop-business-docs", - "version": "8.5.1", + "version": "8.5.2", "description": "Mojaloop Business Documentation GitBook Project", "dependencies": { "express": "4.17.1", From 23c2efe00c034fdb00a8694af981cfbcbb44c13c Mon Sep 17 00:00:00 2001 From: Henk Kodde Date: Thu, 21 Nov 2019 17:47:03 +0200 Subject: [PATCH 3/6] Corrected the internal document ToC navigation for gh-pages. --- documents/platform-operating-guideline.md | 64 ++++++++++----------- documents/scheme-business-rules.md | 34 +++++------ documents/scheme-key-choices.md | 32 +++++------ documents/scheme-participation-agreement.md | 4 +- package-lock.json | 2 +- package.json | 2 +- 6 files changed, 69 insertions(+), 69 deletions(-) diff --git a/documents/platform-operating-guideline.md b/documents/platform-operating-guideline.md index 48f7d26..52c1ad1 100644 --- a/documents/platform-operating-guideline.md +++ b/documents/platform-operating-guideline.md @@ -38,65 +38,65 @@ The Business Rules template that is part of this project can be used independent ## **Table of Contents -- Platform Operating Guideline Template** -[1 - About This Document](#1-About-This-Document) +[1 - About This Document](#1-about-this-document) -[1.1 - Scheme Services](#1.1-Scheme-Services) +[1.1 - Scheme Services](#11-scheme-services) -[1.2 - Open API Specification](#1.2-Open-API-Specification) +[1.2 - Open API Specification](#12-open-api-specification) -[1.3 - Scheme Use Cases](#1.3-Scheme-Use-Cases) +[1.3 - Scheme Use Cases](#13-scheme-use-cases) -[1.4 - Scheme Supported Identifiers](#1.4-Scheme-Supported-Identifiers) +[1.4 - Scheme Supported Identifiers](#14-scheme-supported-identifiers) -[2 - The Account Lookup Service](#2-The-Account-Lookup-Service) +[2 - The Account Lookup Service](#2-the-account-lookup-service) -[2.1 - Description of the Account Lookup Service](#2.1-Description-of-the-Account-Lookup-Service) +[2.1 - Description of the Account Lookup Service](#21-description-of-the-account-lookup-service) -[2.2 - Party Request](#2.2-Party-Request) +[2.2 - Party Request](#22-party-request) -[2.3 - Parties Query](#2.3-Parties-Query) +[2.3 - Parties Query](#23-parties-query) -[2.4 - Parties Query Response](#2.4-Parties-Query-Response) +[2.4 - Parties Query Response](#24-parties-query-response) -[3 - The Quote Service](#3-The-Quote-Service) +[3 - The Quote Service](#3-the-quote-service) -[3.1 - Description of the Quote Service](#3.1-Description-of-the-Quote-Service) +[3.1 - Description of the Quote Service](#31-description-of-the-quote-service) -[3.2 - Quote Request](#3.2-Quote-Request) +[3.2 - Quote Request](#32-quote-request) -[3.3 - Quote Response](#3.3-Quote-Response) +[3.3 - Quote Response](#33-quote-response) -[4 - The Transfer Service](#4-The-Transfer-Service) +[4 - The Transfer Service](#4-the-transfer-service) -[4.1 - Description of the Transfer Service](#4.1-Description-of-the-Transfer-Service) +[4.1 - Description of the Transfer Service](#41-description-of-the-transfer-service) -[4.2 - Transfer Request](#4.2-Transfer-Request) +[4.2 - Transfer Request](#42-transfer-request) -[4.3 - Request to Pay](#4.3-Request-to-Pay) +[4.3 - Request to Pay](#43-request-to-pay) -[5 - The Settlement Service](#5-The-Settlement-Service) +[5 - The Settlement Service](#5-the-settlement-service) -[5.1 - Transfer Settlement](#5.1-Transfer-Settlement) +[5.1 - Transfer Settlement](#51-transfer-settlement) -[5.2 - Fee Settlement: Processing Fees](#5.2-Fee-Settlement:-Processing-Fees) +[5.2 - Fee Settlement: Processing Fees](#52-fee-settlement:-processing-fees) -[5.3 - Fee Settlement: Interchange Fees](#5.3-Fee-Settlement:-Interchange-Fees) +[5.3 - Fee Settlement: Interchange Fees](#53-fee-settlement:-interchange-fees) -[6 - The Scheme Management Service](#6-The-Scheme-Management-Service) +[6 - The Scheme Management Service](#6-the-scheme-management-service) -[6.1 - Description of the Scheme Management Service](#6.1-Description-of-the-Scheme-Management-Service) +[6.1 - Description of the Scheme Management Service](#61-description-of-the-scheme-management-service) -[6.2 - The Registration Process](#6.2-The-Registration-Process) +[6.2 - The Registration Process](#62-the-registration-process) -[6.3 - DFSP Customer Service](#6.3-DFSP-Customer-Service) +[6.3 - DFSP Customer Service](#63-dfsp-customer-service) -[6.4 - Scheme System Management](#6.4-Scheme-System-Management) +[6.4 - Scheme System Management](#64-scheme-system-management) -[7 - The Fraud Management Service](#7-The-Fraud-Management-Service) +[7 - The Fraud Management Service](#7-the-fraud-management-service) -[8 - Appendix: Scheme Supported Use Cases and System Parameters](#8-Appendix:-Scheme-Supported-Use-Cases-and-System-Parameters) +[8 - Appendix: Scheme Supported Use Cases and System Parameters](#8-appendix:-scheme-supported-use-cases-and-system-parameters) -[9 - Appendix: Merchant Category Codes](#9-Appendix:-Merchant-Category-Codes) +[9 - Appendix: Merchant Category Codes](#9-appendix:-merchant-category-codes) ## 1. About This Document @@ -227,7 +227,7 @@ The Scheme may wish to provide some mechanism for porting a Scheme ID from one D The following sections describe each service and the obligations and responsibilities of stakeholders. Each service consists of processes: most of the processes are linked to specific API calls specified in the "Open API Specification" section of this document. -## 2.The Account Lookup Service +## 2. The Account Lookup Service ### 2.1 Description of the Account Lookup Service @@ -517,7 +517,7 @@ following sections:_ 7. _Real-time Transaction Interception Options_ -8. Appendix: Scheme Supported Use Cases and System Parameters +## 8. Appendix: Scheme Supported Use Cases and System Parameters _
    This is the same table as appears in the Business Rules document, but it has added the systemic codes necessary for the Platform to recognize a transaction as belonging to a given use case or secondary use case. A scheme would only define Secondary Use Cases if it wanted to write rules and/or specify fees that are unique to that Secondary Use Case
_ diff --git a/documents/scheme-business-rules.md b/documents/scheme-business-rules.md index 012c428..d6a508f 100644 --- a/documents/scheme-business-rules.md +++ b/documents/scheme-business-rules.md @@ -38,37 +38,37 @@ Scheme Business Rules Template ## **Table of Contents** -[1 - About These Scheme Business Rules](#1.-about-these-scheme-business-rules) +[1 - About These Scheme Business Rules](#1-about-these-scheme-business-rules) -[2 - Scheme Goals](#2.-scheme-goals) +[2 - Scheme Goals](#2-scheme-goals) -[3 - Participation in Scheme](#3.-participation-in-scheme) +[3 - Participation in Scheme](#3-participation-in-scheme) -[4 - Scheme Business Rules](#4.-scheme-business-rules) +[4 - Scheme Business Rules](#4-scheme-business-rules) -[5 - Responsibilities and Obligations of the Scheme](#5.-responsibilities-and-obligations-of-the-scheme) +[5 - Responsibilities and Obligations of the Scheme](#5-responsibilities-and-obligations-of-the-scheme) -[6 - Participant Responsibilities and Obligations of Participants](#6.-participant-responsibilities-and-obligations-of-participants) +[6 - Participant Responsibilities and Obligations of Participants](#6-participant-responsibilities-and-obligations-of-participants) -[7 - Liability - Allocation of Responsibilities](#7.-liability---allocation-of-responsibilities) +[7 - Liability - Allocation of Responsibilities](#7-liability---allocation-of-responsibilities) -[8 - Security, Risk Management, and Data Confidentiality](#8.-security-risk-management-and-data-confidentiality) +[8 - Security, Risk Management, and Data Confidentiality](#8-security-risk-management-and-data-confidentiality) -[9 - Scheme Platform and Services](#9.-scheme-platform-and-services) +[9 - Scheme Platform and Services](#9-scheme-platform-and-services) -[10 - Exception Management](#10.-exception-management) +[10 - Exception Management](#10-exception-management) -[11 - Appendix: Associated Documents](#11.-appendix:-associated-documents) +[11 - Appendix: Associated Documents](#11-appendix-associated-documents) -[12 - Appendix: Onboarding and Exit Processes](#12.-appendix:-onboarding-and-exit-processes) +[12 - Appendix: Onboarding and Exit Processes](#12-appendix-onboarding-and-exit-processes) -[13 - Appendix: Scheme Services](#13.-appendix:-scheme-services) +[13 - Appendix: Scheme Services](#13-appendix-scheme-services) -[14 - Appendix: Scheme Supported Use Cases](#14.-appendix:-scheme-supported-use-cases) +[14 - Appendix: Scheme Supported Use Cases](#14-appendix-scheme-supported-use-cases) -[15 - Appendix: Scheme Fee Schedule](#15.-appendix:-scheme-fee-schedule) +[15 - Appendix: Scheme Fee Schedule](#15-appendix-scheme-fee-schedule) -[16 - Appendix: Risk Management, Security, Privacy, and Service Standards](#16.-appendix:-risk-management-security-privacy-and-service-standards) +[16 - Appendix: Risk Management, Security, Privacy, and Service Standards](#16-appendix-risk-management-security-privacy-and-service-standards) ## **A Guide to This Document** @@ -307,7 +307,7 @@ Section Headings and bulleted entries underneath section headings are actual pro - The Payee Participant must affirm, upon submission of each Transfer Response with a Transaction State "Committed", that the Transfer is being credited to an account that is AML-compliant and is executed in accordance with any account volume limitations, or any other regulation that apply in the territories in which they operate, and that the Payee has been provided all disclosure and has provided all consents necessary to conduct the Transfer in accordance with the Rules and under Applicable Law. - ## 7. Liability - Allocation of Responsibilities +## 7. Liability - Allocation of Responsibilities - Each Participant is responsible for errors made by them, and for fraud committed by its employees or contractors, in accordance with Applicable Law. diff --git a/documents/scheme-key-choices.md b/documents/scheme-key-choices.md index 7b1abdc..99df4ca 100644 --- a/documents/scheme-key-choices.md +++ b/documents/scheme-key-choices.md @@ -38,35 +38,35 @@ Although this document is written as a contribution to the Mojaloop community, t ## **Choices Described in this Document** -[1 - Choice: Ownership of Scheme](#1.-choice:-ownership-of-scheme) +[1 - Choice: Ownership of Scheme](#1-choice-ownership-of-scheme) -[2 - Choice: Participation in the Scheme](#2.-choice:-participation-in-the-scheme) +[2 - Choice: Participation in the Scheme](#2-choice-participation-in-the-scheme) -[3 - Choice: Relationship of Scheme to Platform](#3.-choice:-relationship-of-scheme-to-platform) +[3 - Choice: Relationship of Scheme to Platform](#3-choice-relationship-of-scheme-to-platform) -[4 - Choice: Scope of Scheme Rules and Scheme Rules Authority](#4.-choice:-scope-of-scheme-rules-and-scheme-rules-authority) +[4 - Choice: Scope of Scheme Rules and Scheme Rules Authority](#4-choice-scope-of-scheme-rules-and-scheme-rules-authority) -[5 - Choice: Use Cases](#5.-choice:-use-cases) +[5 - Choice: Use Cases](#5-choice-use-cases) -[6 - Choice: QR Codes](#6.-choice:-qr-codes) +[6 - Choice: QR Codes](#6-choice-qr-codes) -[7 - Choice: Payments Addressing](#7.-choice:-payments-addressing) +[7 - Choice: Payments Addressing](#7-choice-payments-addressing) -[8 - Choice: Interparticipant Settlement](#8.-choice:-interparticipant-settlement) +[8 - Choice: Interparticipant Settlement](#8-choice-interparticipant-settlement) -[9 - Choice: Tiered Access](#9.-choice:-tiered-access) +[9 - Choice: Tiered Access](#9-choice-tiered-access) -[10 - Choice: Scheme Fees and End User Pricing](#10.-choice:-scheme-fees-and-end-user-pricing) +[10 - Choice: Scheme Fees and End User Pricing](#10-choice-scheme-fees-and-end-user-pricing) -[11 - Choice: Brand Management](#11.-choice:-brand-management) +[11 - Choice: Brand Management](#11-choice-brand-management) -[12 - Choice: Scheme Connections to Other Schemes](#12.-choice:-scheme-connections-to-other-schemes) +[12 - Choice: Scheme Connections to Other Schemes](#12-choice-scheme-connections-to-other-schemes) -[13 - Choice: Scheme Use by Other FSP's](#13.-choice:-scheme-use-by-other-fsp's) +[13 - Choice: Scheme Use by Other FSP's](#13-choice-scheme-use-by-other-fsps) -[14 - Choice: Scheme Risk Management Standards](#14.-choice:-scheme-risk-management-standards) +[14 - Choice: Scheme Risk Management Standards](#14-choice-scheme-risk-management-standards) -[15 - Choice: Exception Management](#15.-choice:-exception-management) +[15 - Choice: Exception Management](#15-choice-exception-management) ## 1. Choice: Ownership of Scheme @@ -342,7 +342,7 @@ Mojaloop as a technology is designed to allow system-to-system connectivity. Sch The relevant L1P principles here are low cost and "openness". The Mojaloop code in particular has the potential to turn cross-border transactions from ones that are governed by complex relationships (as in the case of traditional correspondent banking) into ones which are competed for in an open, interconnected marketplace. Schemes will need to evaluate the merits of this (arguably promoting lower costs) with the risks of dominance by major institutions. Scheme-to-scheme business arrangements may have a beneficial "level the playing field" characteristics. Hybrid relationships are also possible. This is an evolving area of the payment industry, and one where considerable variety of arrangements are both possible and likely. -## 13 Choice: Scheme Use by Other FSP's +## 13. Choice: Scheme Use by Other FSP's A successful L1P aligned scheme will be used by many enterprises -- merchants, billers, government agencies, etc. as well as individual people. There will also be a wide range of other FSPs (Financial Services providers) which are not DFSP's: in other words, which do not hold customer transaction accounts. This includes payments services providers: aggregators, merchant services providers, various DFSP processors, etc., all of which may want to connect to and use the scheme. diff --git a/documents/scheme-participation-agreement.md b/documents/scheme-participation-agreement.md index de9a7e9..c4250e6 100644 --- a/documents/scheme-participation-agreement.md +++ b/documents/scheme-participation-agreement.md @@ -30,9 +30,9 @@ The following documents are part of the project: [1 - Participation Application and Agreement](#1-participation-application-and-agreement) -[1.1 - Applicable Law](#1.1-applicable-law) +[1.1 - Applicable Law](#11-applicable-law) -[1.2 - Signature Block: Applicant and Scheme](#1.2-signature-block:-applicant-and-scheme) +[1.2 - Signature Block: Applicant and Scheme](#12-signature-block-applicant-and-scheme) # 1. Participation Application and Agreement diff --git a/package-lock.json b/package-lock.json index 52d8c13..f1eb9c1 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,6 +1,6 @@ { "name": "mojaloop-business-docs", - "version": "8.5.2", + "version": "8.5.3", "lockfileVersion": 1, "requires": true, "dependencies": { diff --git a/package.json b/package.json index 636f5f7..5792c85 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "mojaloop-business-docs", - "version": "8.5.2", + "version": "8.5.3", "description": "Mojaloop Business Documentation GitBook Project", "dependencies": { "express": "4.17.1", From 423858598bb24f6c841a190cf44ffcc800075201 Mon Sep 17 00:00:00 2001 From: Henk Kodde Date: Fri, 13 Dec 2019 17:49:45 +0200 Subject: [PATCH 4/6] - generated pdf documents from markdown documents using Pandoc toolset. - update markdown documents not to use