Side by side
CoCoNet multi:bank vs FIS Open Access
Both stand on bank connectivity software. Which one you can start free with, which one lets you read the code, and what each costs once you pay.
Paid AndroidiPhoneWeb
Choose CoCoNet multi:bank if your organisation needs multi-entity banking information, varied connection methods and real-time refresh. Look elsewhere if you require published pricing before contacting the provider.
Visit CoCoNet multi:bank Paid API
FIS Open Access combines consumer permission controls with bank reporting and standardized API connections. It is mainly relevant where a customer’s bank or credit union uses FIS.
Visit FIS Open AccessThe facts
| CoCoNet multi:bank | FIS Open Access | |
|---|---|---|
| Free plan | Not published | Not published |
| Open source | Not published | Not published |
| Runs on | Android, iPhone, Web | API |
| Lowest paid plan | Not published | Not published |
| Plans published | None | None |
| Maker | Not published | Not published |
| Website | coconet.de | fisglobal.com |
| On bank connectivity software | #49 of 71 | #45 of 71 |
CoCoNet multi:bank: what it does well
- Supports multiple entities
- Real-time data refresh
- Connects through EBICS and PSD2/Open Banking
- Supports SWIFT, ERP, file and API connections
- Handles MT940, MT942 and CAMT statements
What to know first
- Paid product
- Pricing requires a request
FIS Open Access: what it does well
- Consumer-controlled sharing and revocation
- Standardized FDX API connections
- Integrations with four data networks
- Bank visibility and reporting
- Helps replace screen scraping
What to know first
- Paid service with pricing on request
- Access is tied to FIS client institutions
- API platform rather than a listed consumer app
Alternatives to CoCoNet multi:bank Alternatives to FIS Open Access The whole list