Account and Transaction API Specification - UK vs Classic Platforms - Notifications
If you need a Finance API that's easy to integrate, go with Classic Platforms - Notifications.
Account and Transaction API Specification - UK
## Functionality at a glance The NBG "UK OPB - Account and Transaction v3.1.5" API follows the [UK Open Banking Specification v3.1.5](https://openbankinguk.github.io/read-write-api-site3/v3...
Classic Platforms - Notifications
This API is used for the classic integration. If you are just starting your implementation, refer to our [new integration guide](https://docs.adyen.com/marketplaces-and-platforms) instead. The Not...
Account and Transaction API Specification - UK
- Simple API key authentication
- HTTPS supported
- Currently flagged as inactive
Classic Platforms - Notifications
- Simple API key authentication
- HTTPS supported
| Feature | Account and Transaction API Specification - UK | Classic Platforms - Notifications |
|---|---|---|
| Authentication | apiKey | apiKey |
| HTTPS | Yes | Yes |
| CORS | Unknown | Unknown |
When to use which?
Both Account and Transaction API Specification - UK and Classic Platforms - Notifications offer similar capabilities as Finance APIs. Review their documentation to find the best fit for your specific use case.