Connect Noelse accounts, IBAN transactions and TPE settlements to your stack
Noelse is a French payment institution (Afone Paiement, ACPR-approved) offering personal and pro accounts, French IBANs, instant SEPA transfers, sub-accounts and Eftpos terminals. We deliver protocol analysis and OpenBanking-style APIs so accounting tools, ERPs and analytics platforms can read and write that data under user consent.
Market positioning & user profile
Noelse, operated by the Afone group through its Afone Paiement subsidiary, was launched in late 2020 as a French challenger account targeting two segments at once: individuals who want a simple smartphone-first account with a French IBAN, and professionals — freelancers, craftsmen, traders and small entrepreneurs — who need a pro account, a business card, sub-accounts and acquiring through Noelse Eftpos terminals. The platform is recognized in the European digital-banking landscape, with an average user rating around 4.0/5 on neobank directories. Most usage is concentrated in mainland France and operates on Android and iOS, regulated by the French ACPR as a payment institution.
What we deliver
Deliverables checklist
- OpenAPI 3.1 specification covering login, accounts, transactions, transfers, TPE settlements
- Protocol & auth flow report (token rotation, device binding, two-factor patterns)
- Runnable Python and Node.js source for IBAN sync and statement APIs
- Webhook receiver template for instant transfer and TPE telecollection events
- Automated test suite, Postman collection and PSD2-aligned consent guidance
Recent change worth noting
In 2024 Noelse partnered with Algoan to layer Open Banking decisioning on top of customer accounts and roll out a €100 advance product. Around the same period the company expanded its acquiring stack with Ingenico Eftpos terminals, signalling a clear move toward integrated B2B settlement data — exactly the data slice most ERPs and reconciliation platforms want to ingest.
Data available for integration
The table below summarizes the structured data Noelse holds and the typical downstream uses we wire up for clients. Coverage assumes user-authorized access and is based on the visible product surface plus published roadmap items.
| Data type | Source (screen / feature) | Granularity | Typical use |
|---|---|---|---|
| Account & IBAN profile | Onboarding + Accounts screen | Per account, per sub-account | KYC sync, payout setup, bank-link verification |
| Live balance & available funds | Home dashboard | Per account, refreshed on event | Cash-flow dashboards, treasury automation |
| Transaction history | Unlimited history view | Per transaction, with annotation | Accounting reconciliation, expense reports |
| Card lifecycle | Digital card / physical card screens | Per card event (issued, frozen, lost) | Risk control, employee card programs |
| Transfer & beneficiary list | Transfer flow | Per transfer, per beneficiary | Payroll, supplier payments, scheduled treasury |
| Sub-accounts (projects/savings) | Sub-account manager | Per bucket, with goals | Budgeting apps, multi-shop separation |
| TPE / Eftpos settlement | Pro dashboard, dedicated TPE sub-account | Per terminal, per telecollection batch | POS reconciliation, shop performance, accounting |
| Spending notifications | Mobile push channel | Per event, near real-time | Fraud alerts, budget triggers, automation hooks |
Typical integration scenarios
1. Multi-shop TPE reconciliation for a retailer
A small retail chain with three Noelse Eftpos terminals needs daily settlement matched against POS receipts. We bind each terminal to its shop, pull telecollection batches from the dedicated TPE sub-account, and emit a normalized settlement_id → shop_id → gross/net/fees stream into the client's accounting tool. This maps to the OpenFinance acquiring data category.
2. Freelancer accounting auto-sync
A freelancer wants their Noelse pro IBAN feeding directly into their bookkeeping tool. We expose an authorized statement endpoint with categorization tags from the user's annotations, then push monthly closes into the accounting backend. This is a textbook PSD2 AISP scenario.
3. Treasury & instant SEPA from an ERP
A small B2B SaaS triggers supplier payouts from its ERP. We wrap Noelse's instant transfer flow behind a POST /transfers endpoint with idempotency keys, beneficiary cache and PISP-style consent, then return webhook callbacks on settlement. This compresses payment latency from minutes to seconds.
4. Personal finance aggregation
A French PFM app wants to aggregate Noelse alongside other banks. We deliver a Noelse connector that mirrors the announced account-aggregation roadmap, normalizes balances and transactions to the AISP schema, and refreshes every 4 hours with on-demand pull on user open.
5. Compliance & audit export
An accountant needs a year of clean transaction data per client for tax filings. We deliver a signed batch export job — paginated transaction pulls, sub-account roll-up, PDF statement bundle, and a hash manifest for audit. Output stays inside the client's tenant and matches GDPR retention requirements.
Technical implementation
API example: bind account & fetch IBAN
POST /api/v1/noelse/auth/bind
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>
{
"user_ref": "client_42",
"consent_scope": ["accounts","transactions"],
"device_id": "ios-9f2…",
"tfa_channel": "sms"
}
Response 200:
{
"account_id": "acc_8a91…",
"iban": "FR76 3000 …",
"type": "individual",
"currency": "EUR",
"consent_expires_at": "2026-08-03T00:00:00Z"
}
API example: statement export with paging
POST /api/v1/noelse/statement
Authorization: Bearer <ACCESS_TOKEN>
{
"account_id": "acc_8a91…",
"from_date": "2026-04-01",
"to_date": "2026-04-30",
"include_subaccounts": true,
"page": 1, "page_size": 200
}
Response 200:
{
"items": [{
"tx_id": "tx_b13…",
"ts": "2026-04-12T09:18:33+02:00",
"amount": -42.50, "currency": "EUR",
"counterparty": "SNCF",
"category": "travel",
"annotation": "Client visit"
}],
"next_page": 2
}
API example: TPE settlement webhook
POST /your-app/webhooks/noelse/tpe
X-Noelse-Signature: t=…,v1=…
{
"event": "tpe.telecollection.settled",
"settlement_id": "stl_5c…",
"terminal_id": "tpe_PARIS_03",
"shop_id": "shop_paris_03",
"gross": 1284.10,
"fees": 18.66,
"net": 1265.44,
"currency": "EUR",
"value_date": "2026-04-29"
}
Compliance & privacy
Noelse is a French payment institution approved by the Autorité de Contrôle Prudentiel et de Résolution (ACPR) and falls under the EU PSD2 framework. Our connectors only operate under explicit user authorization and follow AISP/PISP-style consent journeys. We log every consent grant and revoke, store tokens in encrypted vaults, and apply GDPR data-minimization to every export pipeline.
Data flow / architecture
The default pipeline is intentionally simple and auditable:
- Client App / ERP initiates a consent and a query.
- Noelse connector handles auth refresh, paging, and rate limiting.
- Normalization layer maps raw payloads to the AISP / settlement schema.
- Storage + downstream pushes to the client's data warehouse, accounting tool, or live API.
Screenshots
Click any thumbnail to view the full-size screenshot. Source: official Google Play listing.
Similar apps & integration landscape
Teams that integrate Noelse usually also need to read or write data in adjacent French and European fintech apps. We commonly deliver bridges between Noelse and the apps below; each one holds a specific data slice that fits naturally into a unified OpenFinance pipeline.
Qonto
European pro account widely used by SMEs and freelancers — IBAN, card transactions and accounting integrations are the usual sync targets.
Shine
Société Générale's neobank for micro-entrepreneurs; pairs naturally with Noelse for invoicing and social-charge data alignment.
Blank
Crédit Agricole's neobank for the self-employed; transaction and VAT-provision data often gets joined with Noelse statements.
Revolut Business
Multi-currency business account with strong transaction APIs; teams unify FX-side flows with Noelse's domestic French IBAN side.
N26 Business
Pan-European mobile-first account; commonly aggregated alongside Noelse for cross-border freelancers.
PropulsebyCA
Crédit Agricole's digital offering for very small businesses; a frequent companion account for Noelse Pro users seeking financing.
Hero (Heropay)
French B2B account with deferred payment features; often joined with Noelse settlement data for cash-flow planning.
Indy
French accounting app that consumes bank feeds; pairs with Noelse via AISP-style transaction exports for automated bookkeeping.
Anytime
Belgian/French neobank for SMEs and associations; complementary IBAN coverage when consolidating multi-account treasuries.
Memo Bank
French bank for SMEs; shares the regulated-payments space and is typically reconciled with Noelse for combined cash positions.
About us
OpenFinance Lab is an independent studio focused on fintech protocol analysis and OpenData/OpenBanking integrations. Our engineers come from European payment institutions, neobanks and acquiring platforms, and we ship end-to-end APIs under PSD2, ACPR and GDPR constraints.
- Payments, digital banking, acquiring and cross-border clearing experience
- Consent-first design with audit logs, NDAs and data-residency options
- Custom Python / Node.js / Go SDKs and webhook receivers
- Full pipeline: protocol analysis → build → validation → compliance review
- Source code delivery from $300 — runnable API source plus full docs; pay after delivery upon satisfaction
- Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost
Contact
For quotes or to submit your target app and requirements, open our contact page:
Engagement workflow
- Scope confirmation: integration scenarios and API surface (IBAN sync, statements, transfers, TPE).
- Protocol analysis and API design (2–5 business days, complexity-dependent).
- Build and internal validation against a sandbox or supervised live account (3–8 business days).
- Docs, samples, Postman collection and test cases (1–2 business days).
- Typical first delivery: 5–15 business days; ACPR-related approvals may extend timelines.
FAQ
What information do I need to provide to start a Noelse integration?
Is Noelse data access compliant with French and EU law?
How long does a typical Noelse delivery take?
Can you also handle TPE / Eftpos settlement data?
📱 Original app overview (appendix)
Noelse is the online account for individuals and professionals from Afone Paiement. Registration is quick, with no commitment, and the app aims to give users back control over their money — budgeting, mobile payments, and instant transfers from a single mobile interface.
- Open an account in minutes directly from the application
- Manage accounts easily through a smart interface
- Activate a digital card and order a physical card
- Make instant transfers and use a French IBAN
- Customise services for a tailored experience
- Organise projects or savings with sub-accounts
- Unlimited transaction history with tallying and annotations
- Instant spending notifications, beneficiary management, customer service
For freelancers, craftsmen, traders and entrepreneurs, Noelse offers an all-in-one solution including a pro account, business card and sub-accounts plus free EFT, real-time transaction monitoring, one-off, recurring, scheduled or instantaneous transfers, and integration with Noelse Eftpos terminals — including a dedicated TPE sub-account and per-shop allocation, with live telecollection and automatic terminal updates.
Roadmap items announced by Noelse include account aggregation, payment initiation, deposit account, instant transfer and accounting assistance. For more information visit noelse.com/faq or contact support@noelse.com.