Learn FINORA the way it is really used.

Language

The Academy is written first in neutral Spanish. These entry pages and the satellite-systems integration guide are available in English; the other lessons open in Spanish, with a notice at the top, until their translation is published.

Choose your system

Each system has its own home page and its own sidebar; the selector in the header moves you from one to another.

Bank

FINORA CoreThe core banking system: customers, accounts, accounting and loans, with an open API for the bank's satellite systems.

FINORA Emisión (CMS)Issuing and management of debit, prepaid and credit cards: products and BIN, authorizations, limits, clearing and credit-card billing.

FINORA SucursalThe bank branch: account opening, teller, cash, vault, cash count and remittances.

Payments

Aurora SwitchThe ISO 8583 switch: it authorizes and routes card transactions as issuer, acquirer or hub, with an HSM.

Aurora OfficeThe switch console: interconnections, nodes, ports, routing and four-eyes publication.

Commerce

FINORA MerchantAcquiring: merchant onboarding, terminals (TMS), payment orchestration, batch, clearing, settlement and reconciliation.

FINORA Caja and FINORA PagoThe point-of-sale register for Windows and Android, and the local payment agent for third-party registers and ERPs.

FINORA CheckoutHosted payment page and SDK to take payments online, with signed webhooks.

Enterprise and platform

FINORA ERPThe company ERP: finance, accounting, payroll, sales, purchasing, inventory and transport.

FINORA PlatformInstallation by environment and country, the cell-based cloud, module licensing, BPMN orchestration and FINORA Pulse.

Start here

1. Choose your system from the list above. If you use several of them (for example, a bank that runs the core and also the switch), each one has its own home page and its own sidebar.
2. Follow your role path. It is the shortest way to learn: lessons are listed in the order in which they are best done, and each one is a concrete task.
3. Check the status of each page before relying on it. Every technical page states how far its claims have been checked: Documented (written from the design or the code), Implemented (exists in the code) or Verified (tested against a running system, with evidence and date).

Inside each system, pages come in four types: tutorials to learn by doing, how-to guides to solve a task, reference to look up the exact value and concepts to understand the reasons behind the design. Statuses, page types and access levels are explained in How to read the Academy.

Search (Ctrl/Cmd + K) covers every system at once.

Honest status

The systems described here are deployed and operate in FINORA’s demonstration environment, against a simulated bank. A Implemented badge means exactly that: deployed and operating in that environment, never «in use by banks». The Academy does not claim that any system operates with real banks, complies with PCI DSS or holds a card-brand certification.

Conventions

• The reference language is neutral Spanish. Technical terms stay in English when they have no common translation (switch, clearing, webhook).
• No example carries real customer or card data: card numbers, accounts and amounts are test values.
• Card-brand rules (Mastercard, Visa) are explained in our own words, citing the manual and page; their manuals are not reproduced.
• A Por verificar (to be verified) notice marks something not yet confirmed against a live FINORA server. Treat it as a lead, not as a fact.