Mifos Docs
  • Open Banking API via WS02 API Gateway
  • WSO2
    • Configure EC2 instance for WSO2 APIGateway
      • WSO2 APIGateway install from docker-compose
      • Default urls
    • Setup OpenBanking API's
      • How to import swagger file to API store
      • Account and Transaction API Specification - v3.1.2
      • Payment Initiation API Specification - v3.1.2
    • WSO2 authentication endpoint demo application
      • Config, setup, build, deploy application
      • web.xml
      • oauth2_authz.jsp and oauth2_consent.jsp
      • uk.org.openbanking.v3_1_2 package
      • hu.dpc package
    • Signup and subscribe APIs as TPP/FPP
    • How to add new bank user
  • OpenBanking Adapter
    • Setting up the adapter
  • ACEFintech TPP demo application
    • Configure EC2 instance
    • Config, setup, build, deploy application
  • LionFintech FPP demo application
    • Configure EC2 instance
    • Config, setup, build, deploy application
  • How to
    • Add bank user to demo application
    • Configure Azure instance
      • Installing docker & docker-compose
      • Installing JDK
      • Installing git client
      • Install unzip
      • Install tools to compile WebApp
      • Compile Server Apps
      • Compile WebApp
    • Configure Amazon EC2 instance
      • Installing JDK
      • Installing docker & docker-compose
      • nginx config for ACEFintech and/or LionFintech
  • Payment Hub EE
    • Business Overview
      • Vision
      • Benefits of Payment Hub EE
      • Target Users of Payment Hub EE
      • Using Payment Hub EE
    • Technical Overview
      • Deployment models
        • DevOps Tooling for Deployment
      • Microservices orchestration - Zeebe
      • Installation instructions
        • Post Deployment Steps
        • Sample Pipeline
          • Secrets to be Configured in Contexts
        • Default cookbook chart for GOV use case
        • Requirements
          • System Requirements
          • Azure Requirements
        • Custom Installations
          • Customizing the Deployment Configurations
        • Configuration Instructions
          • Deploy BPMNs with multiple DFSP-IDs
          • How to setup the Registering Institution ID with Budget Account
          • How to setup the Program ID
          • How to setup the Tenants
          • How to setup the DFSP-IDs
          • Flow Configurations
          • Updating DNS
          • Known issue and fix
      • Uninstallation Instructions
      • An introductory Zeebe project (Getting started)
      • An introductory Zeebe project (How it works)
      • Lab environment
      • Accessing Lab Environment
      • Example
      • Secondary Identifier Storage and Registration
      • Data Architecture
      • Data Dictionary
      • Payment Hub APIs
      • Source Code repositories
      • Audit Trail
      • Tuning and performance
      • Payment Process Overview
      • Development Environment
      • Bulk Disbursement Integration
    • Release Notes
      • v1.7.0
      • v1.7.2
      • v1.8.0
      • v1.8.1
      • v1.9.0
      • v1.10.0
      • v1.11.0
      • v1.11.1
      • v1.12.0
      • v1.13.0
  • Mifos - Mojaloop
    • Mifos Wallet Solution
Powered by GitBook
On this page

Was this helpful?

  1. WSO2
  2. Setup OpenBanking API's

Payment Initiation API Specification - v3.1.2

Scope: payments Swagger definition: https://raw.githubusercontent.com/OpenBankingUK/read-write-api-specs/v3.1.2/dist/payment-initiation-swagger.yaml OpenBanking documentation: https://openbanking.atlassian.net/wiki/spaces/DZ/pages/1077805296/Account+and+Transaction+API+Specification+-+v3.1.2

Implement section

Field

Value

Endpoint production

Manage section Resources group

Add accounts scope

Field

Value

Scope Key

payments

Scope Name

payments

Role

Internal/everyone

Description

(empty)

Setup API calls

After you add scope "payments", you must set "payments" scope to all API entry. You must modify "Caller type" to "Application" the following API entries:

  • /domestic-payment-consents

  • /domestic-payment-consents/{ConsentId}

  • /domestic-payments/{DomesticPaymentId}

You must modify "Caller type" to "Application User" the following API entries:

  • /domestic-payment-consents/{ConsentId}/funds-confirmation

The remain API entries still "Application & Application User".

PreviousAccount and Transaction API Specification - v3.1.2NextWSO2 authentication endpoint demo application

Last updated 5 years ago

Was this helpful?

http://lion.mlabs.dpc.hu/apischema/ob/