In the scope of the European Payment Services Directive 2015/2366 (also known as PSD2), CIC provides API access to qualified Third Party Payment Service Providers for the following purposes:
- Account and Transaction Information for Account Information Service Providers (AISPs)
- Checking of Funds Coverage for Card-Based Payment Instrument Issuers (CBPIIs)
- Payment Initiation for Payment Initiation Service Providers (PISPs)
These APIs are available at
https://oauth2-apiii.e-i.com/cic/, with a sandbox
Recent and upcoming changes
Stay up-to-date with our updates feed:
- Last update: 2021-12-28T00:00:00 Updates Feed
- Registration for API Access - Who can access the APIs, under what criteria?
- OAuth 2 and Strong Customer Authentication Workflows - How, when, and under which conditions will Strong Customer Authentication be processed?
- OAuth 2 Endpoints - How is OAuth 2 implemented?
- Open Banking API Endpoints - How to call the endpoints, what do they return?
- Fallback Mechanism - As published by ACPR in September 2021, CIC has been exempted from the fallback mechanism. Therefore, the fallback mechanism will be shut down on January 19, 2022.
If you want to dive directly into the APIs, they are documented as OpenAPI Specification (Swagger) files:
- View OAuth 2 Endpoints Specification
- Open Banking API Endpoints Specification:
View v2.0 Published
- In the
PaymentRequestResourceschema, the field that describes the payment request status is now correctly named
- In the
CreditTransferTransactionschema, the fields
statusReasonInformationare now available;
- Payment cancellation workflows are now initiated with status
CANCand do not require SCA;
- The API endpoints now conform to STET Specification v1.4.2;
- The REDIRECT workflow for payment confirmation now conforms to OAuth2 authorization code flow;
- In the
API specifications updates and deprecation announcements are also in our updates feed.
Publication of statistics
- Need some help? Get in touch with CIC