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 environment at https://oauth2-apiii.e-i.com/sandbox/cic/.

Recent and upcoming changes

• December 11^th, 2019: Breaking change - On the OAuth2 registration API, a contacts metadata field has been added as specified in RFC 7591, and has been set as mandatory. That information is needed so that CIC can comply with legal notification requirements (notifying TPPs at least 3 months in advance) for technical changes in the future.

Subjects

• 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 - What is the fallback mechanism, and how to use it?

API Specifications

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 v1

  • View v1.1 Published

    Changelog

    • GET /accounts: the name of the account entry that represents a set of card-based transactions now specifies the holder name;
    • GET /accounts/{accountResourceId}/balances: the list of balances for a set of card-based transactions now contains additional balance objects, materializing per-booking-date transaction amounts;
    • GET /accounts/{accountResourceId}/transactions: for pending card-based transactions, bookingDate is now set to the expected booking date - it was previously left unset;
    • GET /accounts/{accountResourceId}/transactions: for cash-account transactions, bookingDate is now always set to the actual booking date on the user's account;
    • GET /accounts/{accountResourceId}/transactions: for card-based transactions, unstructured remittance information may now include location information;

Publication of statistics

• View statistics

Contact us

• Need some help? Get in touch with CIC