Norma 43 bank reconciliation with payment proofs and Redsys card payments
A component to take card payments through the Redsys virtual POS or bank transfers, and to confirm transfers automatically against the Norma 43 statement, with the customer's payment proofs at hand for unclear cases.
Taking payment by bank transfer is cheap, but confirming every incoming payment by hand is slow. This Norma 43 bank reconciliation module matches pending transfers against the statement from any Spanish bank and confirms the ones that fit on its own. For unclear cases, the customer can upload a payment proof. It also takes card payments through the Redsys virtual POS (the card payment gateway your bank provides): both routes end with the payment confirmed and the service activated.
Who it is for
Teams building business management software for companies in Spain, service businesses that take payment by transfer and by card, and card payment integrators.
Built for Spain: Norma 43 is the Spanish bank statement format and Redsys is the Spanish card payment processor.
What Norma 43 bank reconciliation solves
- Checking the bank every day. Transfers that match the statement are confirmed automatically.
- Payments confirmed by mistake. Automatic confirmation only happens when both the reference and the amount match.
- Two payment methods, two processes. Card and transfer end at the same point.
What it does
- Reads the Norma 43 statement (AEB/CSB43) from any Spanish bank: account, transactions, descriptions, currency and totals.
- Matches each incoming credit with the pending transfers by reference and, if the amount matches, confirms the payment and activates the service.
- Sets unclear cases aside for review: a reference with a different amount, several matches, credits with no reference and files already imported.
- Collects the payment proofs the customer uploads from the website or the app, checks that each file is the type it claims to be and deletes them when the retention period ends.
- Takes card payments through the Redsys virtual POS, verifying the bank's notification.
- Generates a SEPA credit transfer QR code (EPC069-12) that fills in the IBAN, amount and reference in the customer's banking app.
Benefits
- Manual payment review shrinks to a handful of cases.
- You can offer bank transfer as a payment method without multiplying the admin work.
- The SEPA QR code avoids typing errors.
Industry context
General industry data with its public source. These are not results of this product.
- In the second half of 2025, 1.637 billion credit transfers were made in Spain, 6.9% more than a year earlier, accounting for 87.9% of the value of non-cash payments. Source: Bank of Spain (Banco de España), "Estadísticas sobre pagos en España (segundo semestre de 2025)" (payment statistics for Spain, second half of 2025), 2026.
What you get with each license
Price upon request, depending on license type and scope. Integration support and maintenance are contracted separately.
- The module code, ready to add to your business management software.
- Integration examples and documentation.
- A warranty against defects for the agreed period.
- Everything above, with the right to adapt it to your data model and maintain it inside your product.
- The right to integrate the asset into a commercial product of your own, identified in the contract.
- The right to distribute it to your customers as part of that product, without requesting authorization for each installation and with no limit on end customers, unless otherwise agreed.
- It does not include reselling or sublicensing the asset on its own.
- It is not exclusive, unless otherwise agreed.
- Maintenance, support and adaptations are contracted separately.
Technical specifications
Language and runtime: TypeScript 5.9 on Node.js. Minimum supported version: Node.js 20.9 (declared in the project configuration and by Next.js 16).
Frameworks: Next.js 16.4 for the API routes. Data access with Prisma 5.22.
Database: PostgreSQL.
Operating systems: A server with Node.js.
Interface languages: Spanish.
Required infrastructure:
- PostgreSQL.
- Redsys, your bank's virtual POS, for card payments (requires the buyer's own account).
Private deployment: It can run on its own in your infrastructure: the Norma 43 statement is downloaded from online banking and loaded into the application. Only card payments need a connection to Redsys.
Main libraries:
| Library | Version | License |
|---|---|---|
| next | 16.4.2 | MIT |
| @prisma/client | 5.22.0 | Apache-2.0 |
| unpdf | 1.9.1 | MIT |
| qrcode | 1.5.4 | MIT |
Dependencies with specific license terms:
- @img/sharp-libvips-* 1.3 (libvips binaries, an optional dependency of Next.js): LGPL-3.0-or-later; @img/sharp-win32-* and @img/sharp-wasm32 0.35: Apache-2.0 AND LGPL-3.0-or-later.
Compatibility and integrations: Norma 43 statements (AEB/CSB43), Redsys virtual POS (test and live environments) and SEPA credit transfer QR code (EPC069-12).
Redistribution terms
The asset's own code can be integrated into the licensee's commercial products under the embeddable module license, the source code license and the OEM license, on the terms of the contract. The libvips binaries that Next.js installs as an optional dependency (LGPL-3.0-or-later) have specific terms; see the list under Technical specifications.
Installation requirements
A Node.js application with PostgreSQL. For card payments, your bank's Redsys virtual POS and its merchant credentials.
Frequently asked questions
Does it work with any bank?
Yes, any Spanish bank: Norma 43 is the standard statement format of Spanish banking.
What happens with unclear cases?
They go to a review list so someone can assign them by hand.
Does it need a third-party payment gateway?
No. Redsys is the virtual POS provided by the merchant's own bank, and the statement is downloaded from online banking.
Is maintenance included?
No. Maintenance (updates and bug fixes) and integration support are contracted separately.
Request
Request information on M-BAN-01
Fill in the form with the asset reference and the license type you're considering. I reply in writing. If you need to review code, tick the NDA box and we'll sign one before anything is shared.