Apigee Open Banking Connector

Seamless, Secure & Scalable API Integration

Our Apigee Open Banking Connector empowers financial entities to securely connect and integrate Open Banking APIs using a ready-to-import API proxy bundle. Built on Google Apigee’s robust API management platform, this kit simplifies the onboarding and evaluation process for AISPs and PISPs.

Prerequisites

• Access to Apigee X or Apigee Edge organization
• Required Apigee user roles and permissions

How to Integrate

1. Download & Import the Proxy Bundle
   Download and import the API proxy into your Apigee X or Edge environment
2. Create an API Product
   Create two API products in your Apigee environment:
   • AISP Product – for account access and consent APIs
   • PISP Product – for payment initiation and funds confirmation APIs
3. Register a Developer App
   Create a developer app in your Apigee instance and associate the API products created above
4. Deploy the API Proxies
   Deploy all imported proxies to your target environment (dev, prod, etc.) using the Apigee UI.
   Ensure each proxy is deployed successfully and accessible via its configured base path
   🔁 Replace the default mock target endpoint ({{target.url}}) in the proxy with your bank's actual backend endpoint
5. Generate Access Token
   POST /token/generate?grant_type=client_credentials
6. Test Open Banking APIs
   • AISP Flow
     • POST /aisp/v1/access-consent - create consent
     • POST /userauth - authenticate user
     • POST /aisp/authorize?  - authorize request 
       {query_params: client_id, scope, otp, consent_id, state, redirect_uri, response_type}
     • POST /aisp/token - token exchange
     • POST /aisp/v1/access-consent/{consent_id}/authorization - authorize consent
     • GET  /balanceinquiry - check account data
     • PUT/DELETE /aisp/v1/access-consent/{consent_id} - update/delete consent
   • PISP Flow
     • POST /pisp/v1/access-consent - create consent
     • POST /userauth - authenticate user
     • POST /pisp/authorize?  - authorize request 
       {query_params: client_id, scope, otp, consent_id, state, redirect_uri, response_type}
     • POST /pisp/token - token exchange
     • POST /pisp/v1/access-consent/{consent_id}/authorization - authorize consent
     • POST /paymentinitiation - initiate payment
     • POST /fundconfirmation - validate funds
     • PUT/DELETE /pisp/v1/access-consent/{consent_id} - update/delete consent