Capture without conclusion.
Store the source URL, snapshot, observed date and proposed changed field. Do not overwrite the existing approved fact when a page or register moves.
Provider intelligence / Approved event ledger
The page changed is not the provider changed.
A NeobankDB page can be created, corrected or rebuilt without any outside product event. This directory includes only changes with an identified provider or legal entity, exact market and field, supported earlier and later states, an event or announcement date, source evidence, review state and public impact.
4 approved provider events cover 3 markets and 3 changed fields. 2 have exact effective dates; other records expose month-only or unstated precision instead of inventing a day. Latest evidence observation: 2026-07-12.
Approved events4before + after
Markets3not globalised
Changed fields3kept distinct
Exact effective dates2no guessed day
Non-negotiable distinction
Publication history is not company news.
The general NeobankDB changes ledger records when a route was completed and its source set reviewed. It does not claim that a fee changed, a market opened, an account closed or a licence moved on that date. Reusing a build timestamp as an external event date would fabricate a causal timeline.
This provider ledger makes the outside relationship explicit. Each event needs a scoped earlier state and later state, the source records supporting each side, a date with honest precision, the current publication impact and a statement of what the evidence does not prove. A crawl, press mention or model summary can propose a private candidate; none can create or approve the public event.
Admission contract
Seven questions decide whether a change enters the ledger.
Failure on any material question keeps the candidate outside the approved directory.
- 01
Who changed?
Name the provider, legal entity, partner or regulated permission. A brand-level statement cannot absorb every group company or service relationship.
- 02
Where?
Attach the market. A United States programme closure does not close the same brand’s United Kingdom or German bank, and a free-zone entity does not define a whole country.
- 03
Which field?
Availability, permission and account legal model are separate. One can change while pricing, customer eligibility, separate products and service quality remain unknown.
- 04
What was before?
Preserve the earlier scoped state with source evidence. “Unknown” is not a usable old value, and a current page alone cannot manufacture its own history.
- 05
What is after?
The later state must be supported independently or by an authoritative timeline that states both sides. Marketing emphasis is not enough for a material legal change.
- 06
When?
Keep announcement, effective and observation dates separate. If the source gives only a month, show the month. If it omits the effective date, say so.
- 07
So what?
State the current user impact and the boundary. A permission withdrawal may invalidate one entity claim without proving that every branded service vanished.
Event pipeline
A signal becomes public only after relationship review.
The pipeline preserves rejected and incomplete candidates privately; the public list contains approved relationships only.
Align subject, scope and time.
Check whether the apparent difference is a true change or merely another market, product, cohort, document purpose or historical observation.
Record the relationship.
A reviewer accepts the before and after evidence, event date precision, materiality, status, public impact and limits. Schema validity alone is insufficient.
Rebuild affected views.
Update the approved fact and related pages while retaining the earlier state, dates and source trail. A staged transition can keep two live customer cohorts.
Watch the current boundary.
Later evidence can complete a migration, change the effective date or reveal another scoped entity. It creates a candidate update, not silent replacement.
Approved provider-event filters
Trace the field that actually changed.
4 of 4 provider change eventsPage publication dates are never used as provider event dates.
- Effectiveexact day
United States / market accounts closed
Monzo United States account programme
completedmarket availabilityMonzo closed every account in its former United States programme on 8 June 2026 and no longer accepts new incoming deposits for those accounts.
Before Before closure
Monzo Inc. operated a United States account programme with Sutton Bank.Historical United States partner-bank programme only; not Monzo Bank Limited in the UK
- Observed
- 2026-07-12
- Source IDs
- SRC-MONZO-US-CLOSURE
- Monzo Help: Monzo US account closure supportAuthority 2/10 · observed 2026-07-12
After After closure
All United States accounts closed on 8 June 2026; new incoming deposits and transfers are rejected and returned.Current United States programme availability and post-closure payment handling
- Observed
- 2026-07-12
- Source IDs
- SRC-MONZO-US-CLOSURE
- Monzo Help: Monzo US account closure supportAuthority 2/10 · observed 2026-07-12
Current impact
Exclude the former programme from current United States account options and route former customers to closure support for statements, tax forms, checks or suspicious activity.
Not proven by this event
The closure record does not describe Monzo Bank Limited's United Kingdom accounts, predict a United States relaunch or establish service quality before closure.
Read dates, evidence state and related pages
- Announcement date
- Not separately stated
- Effective date
- 2026-06-08
- Last reviewed
- 2026-07-13
- Evidence confidence
- high
- Effectivemonth only
United Kingdom / bank licence transition
Revolut United Kingdom account model
staged in progressaccount legal modelRevolut Bank UK Ltd became a fully licensed UK bank in March 2026, but the account-model change remains staged for some existing e-money customers.
Before Earlier account model
United Kingdom customers held e-money accounts using safeguarding rather than bank-deposit protection.Revolut UK account model before bank-account migration; separate products excluded
- Observed
- 2026-07-12
- Source IDs
- SRC-REVOLUT-UK-BANK-TRANSITION
- Revolut: Is Revolut a fully licensed bank in the UK?Authority 3/10 · observed 2026-07-12
After Bank licence and staged migration
Revolut Bank UK Ltd became fully licensed in March 2026; new customers receive bank accounts while some existing e-money accounts remain in transition.United Kingdom bank-account cohort only; customer migration and product eligibility control
- Observed
- 2026-07-12
- Source IDs
- SRC-REVOLUT-UK-BANK-TRANSITION
- Revolut: Is Revolut a fully licensed bank in the UK?Authority 3/10 · observed 2026-07-12
Current impact
Use the authenticated account and current terms to decide whether eligible funds are bank deposits with FSCS treatment or transitional e-money using safeguarding.
Not proven by this event
The licence does not convert every legacy account or separate crypto, investment and other group product into a protected bank deposit.
Read dates, evidence state and related pages
- Announcement date
- Not separately stated
- Effective date
- 2026-03
- Last reviewed
- 2026-07-13
- Evidence confidence
- high
- Effectiveexact day
United Arab Emirates / permission withdrawn
Wise Nuqud Ltd ADGM permission
completed current effectregulatory permissionThe ADGM public register records the named Wise Nuqud Ltd permission as withdrawn on 26 September 2023.
Before Before withdrawal
The FSRA register carried a permission record for Wise Nuqud Ltd.Named ADGM legal entity and its recorded permission only
- Observed
- 2026-07-12
- Source IDs
- SRC-ADGM-WISE-NUQUD
- Abu Dhabi Global Market Financial Services Regulatory Authority: Wise Nuqud Ltd public register entryAuthority 1/10 · observed 2026-07-12
After After withdrawal
The Wise Nuqud Ltd permission status is withdrawn from 26 September 2023.Named ADGM legal entity only; not every Wise group entity or UAE product
- Observed
- 2026-07-12
- Source IDs
- SRC-ADGM-WISE-NUQUD
- Abu Dhabi Global Market Financial Services Regulatory Authority: Wise Nuqud Ltd public register entryAuthority 1/10 · observed 2026-07-12
Current impact
Do not cite Wise Nuqud Ltd's withdrawn permission as current authority for UAE onboarding, sending or holding products.
Not proven by this event
The withdrawal does not by itself prove that every Wise service is unavailable in the UAE or identify a current alternative contracting entity.
Read dates, evidence state and related pages
- Announcement date
- Not separately stated
- Effective date
- 2023-09-26
- Last reviewed
- 2026-07-13
- Evidence confidence
- high
- Announcednot stated
United States / market exit announced
N26 United States operations
completed current effectmarket availabilityN26 announced its United States market exit on 18 November 2021; current first-party guidance confirms that the former account programme is closed.
Before Before the exit
N26 Inc. operated a United States partner-bank account programme.Historical United States account programme only; not N26 Bank SE in Germany
- Observed
- 2026-07-12
- Source IDs
- SRC-N26-US-EXIT-ANNOUNCEMENT · SRC-N26-US-CLOSURE
- N26: N26 announcement on leaving the United StatesAuthority 3/10 · observed 2026-07-12
- N26: N26 United States account closure updateAuthority 2/10 · observed 2026-07-12
After After the exit
N26 ceased United States operations and the current closure page says every former account is closed.Present United States availability and former-customer support state
- Observed
- 2026-07-12
- Source IDs
- SRC-N26-US-EXIT-ANNOUNCEMENT · SRC-N26-US-CLOSURE
- N26: N26 announcement on leaving the United StatesAuthority 3/10 · observed 2026-07-12
- N26: N26 United States account closure updateAuthority 2/10 · observed 2026-07-12
Current impact
Exclude N26 from current United States account availability. Former customers must use the closure-support route for historic records or remaining issues.
Not proven by this event
The approved sources do not state an exact final closure date, a future United States return date, customer totals or service-quality outcomes.
Read dates, evidence state and related pages
- Announcement date
- 2021-11-18
- Effective date
- Not stated in approved evidence
- Last reviewed
- 2026-07-13
- Evidence confidence
- high
Deliberate exclusions
Interesting signals stay out when the before-and-after chain is incomplete.
Exclusion prevents a sparse current source from turning into invented history.
Fee schedules
A current effective date is not an old price.
Several approved schedules state when current terms became effective. Without a reviewed prior schedule for the same plan and market, they support the current value only. The directory does not infer that every listed price changed on the effective date.
Partner migrations
A process page is not a universal migration event.
Mercury describes how partner-bank switching can open new accounts and change routing details, but the exact customer cohort and controlling provider remain account-specific. That mechanism stays outside this event set until scoped old and new relationships agree.
Conflicting pages
Disagreement is not proof of movement.
Airwallex pricing pages and Wise UAE availability pages currently disagree. They remain in the conflict ledger; selecting an order for those pages would fabricate a change and a winner.
Phased service relationships
Direction and cohort must be evidenced.
Cash App identifies two possible carrying brokers during a phased migration. The public agreement does not establish one universal before and after for every customer, so the statement or confirmation remains controlling.
Date semantics
Four dates can describe one change.
Date labels are not interchangeable. The UI never pads a month with a fictional first day or turns a research observation into the provider’s effective date.
When the subject publicly communicated an intended or completed change. An announcement can precede the effective state and does not prove implementation by itself.
When the licence, closure, term or product state took effect. Exact day and month-only precision remain visibly different.
When NeobankDB reviewed the source. It supports freshness and auditability but is not evidence that the outside event occurred that day.
When the before-and-after relationship was approved or rechecked. It records the editorial decision, not a new provider event.
Current-use rules
An event changes only the field and scope its evidence supports.
Every card below is intentionally narrower than a brand-wide verdict.
Remove a closed programme from current availability.
Keep former-customer support, statements, tax forms, checks and dispute paths visible. Do not describe another market’s live entity as closed or promise a return.
Stop citing the withdrawn entity permission.
The event can invalidate current authority for the named entity. It does not establish a replacement contract or universal brand availability without new evidence.
Preserve customer cohorts while migration is staged.
New bank accounts and older e-money accounts can require different protection language. Authenticated account terms decide the current customer relationship.
Reject current product and incoming-payment claims.
A completed closure changes present availability. Historical partner-bank and protection evidence stays history and does not create a live account option.
User boundary
A change record is evidence context, not individual advice.
The directory does not decide whether a user’s specific account migrated, which bank holds a balance, whether funds qualify for protection, whether a transfer will be returned or how a complaint should be resolved. Customer statements, agreements, authenticated notices and regulator records can control the individual position.
A historical event also does not measure provider quality. Closures, licences and permission states do not become scores, rankings or predictions. If a record is incomplete or wrong, submit the exact claim, market, source URL and observation date through the correction workflow; the submission remains pending until reviewed.
Follow the audit trail
Separate delivery, evidence, conflict and event.
Use the general changes ledger for NeobankDB page history, the source directory for evidence metadata, the conflict ledger for unresolved disagreement and the methodology for approval rules. No single directory answers every question.