PSD2 API Developer Portal
PSD2 API Developer Portal
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
Stay up-to-date with our updates feed:
- Last update: 2021-03-15T00:00:00 Updates Feed
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:
-
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;
-
View v2.0 Published
Changelog
- In the
PaymentRequestResource
schema, the field that describes the payment request status is now correctly namedpaymentInformationStatus
; - In the
CreditTransferTransaction
schema, the fieldstransactionStatus
andstatusReasonInformation
are now available; - Payment cancellation workflows are now initiated with status
CANC
and 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
Contact us
- Need some help? Get in touch with CIC