API archive entry · source-reported
OpenFinTech.io
# Introduction OpenFinTech.io is an open database that comprises of standardized primary data for FinTech industry. It contains such information as geolocation data (countries, cities, regions), organizations, currencies (national, digital, virtual, crypto), banks, digital exchangers, payment providers (PSP), payment methods, etc. It is created for communication of cross-integrated micro-services on "one language". This is achieved through standardization of entity identifiers that are used to exchange information among different services. ### UML UML Domain Model diagram you can find here. ### Persistence Entities are updated not more than 1 time per day. ### Terms and Conditions This *OpenFinTech.io* is made available under the Open Database License. Any rights in individual contents of the database are licensed under the Database Contents License. ### Contacts For any questions, please email - info@openfintech.io Or you can contact us at Gitter Powered by Paymaxi # Get Started If you use POSTMAN or similar program which can operate with swagger`s files - just download our spec and import it. Also you can try live API demo. ## Overview The OpenFinTech API is organized around REST
Plan the first integration safely
The access fields below come from the connected directory. Their likely implementation impact is explained without assuming provider-specific behavior.
Authentication
OAuth is reported. Confirm flows, scopes, consent, token lifetime, and refresh rules.
Transport
HTTPS is not confirmed. Do not send credentials or production data until secure transport is verified.
Browser access
CORS is unknown. Treat direct browser access as unconfirmed and test before choosing a client-only architecture.
First-request sequence
- Identify the current base URL, version, and endpoint for the use case.
- Confirm how credentials are issued and where they may be stored.
- Test success, invalid input, throttling, unavailable data, and timeouts.
- Record response fields, pagination, caching, and error shapes.
- Add monitoring, retries with backoff, and an appropriate fallback.
Questions to resolve before production
Pricing and quotas
Confirm current plans, free-tier limits, overages, and request ceilings.
Endpoint coverage
Check that the operations and response fields match the intended workload.
Reliability
Look for uptime history, a status page, support routes, and service commitments.
Data and privacy
Review retention, licensing, regional processing, and compliance requirements.
Versioning
Confirm the active version, change policy, deprecation window, and migration guidance.
Developer experience
Validate SDKs, examples, error formats, pagination, and test environments.
Source reference
This page separates source-reported facts from questions that need live provider verification.