Evidence governance / Active public ledger
Two official pages can describe the same provider, market and field differently. NeobankDB does not average the values, select the more attractive one or let the most recently crawled page win automatically. This ledger preserves each scoped claim, its source, observation date and public consequence until evidence supports a reviewed resolution.
5 active conflict records span 4 markets and 5 material fields. 4 are high materiality. Latest source observation: 2026-07-13. Latest review:2026-07-13.
Publication red line
A conflict is not permission to calculate an average price, choose a larger protection limit, merge several legal entities into one relationship or describe availability as “probably supported.” Those transformations create a third claim that appears in none of the sources. The current decision must instead say what can be published, what must be held and what live document controls an individual customer’s position.
Source authority also does not erase disagreement. A regulator register can be authoritative about a named entity’s permission while remaining unable to establish the exact customer product, plan fee or contracting relationship. A provider agreement may control a specific customer while a product page describes a broader acquisition offer. Both records remain visible when their scopes cannot be reconciled safely.
Qualification test
Reviewers test subject, market, product, customer class, effective period and source purpose before assigning the conflicting state.
Brand names are not legal entities, and provider groups can operate several regulated companies, programme managers, custodians and partner banks. A page about one subsidiary does not conflict with another subsidiary merely because both use the same brand. The exact company, product, plan and contractual role must overlap first.
Fees, licences, protection, availability and routes are commonly market-specific. A US plan price cannot resolve a UK plan, and an EEA entity cannot be substituted for a UAE contracting party. The ledger stores an ISO market on every record and does not promote a local disagreement into a global provider statement.
A reviewed newer fee schedule can supersede an older one without leaving an active conflict. But “newer” alone is not enough: an undated marketing page may remain live beside a dated agreement, and a store rating is only a snapshot. Effective dates, observation dates and document versions decide whether the difference is history or disagreement.
A help article, public offer, legal agreement, regulator record and authenticated account screen can each serve a different purpose. Reviewers identify the claim each source can actually support. A document is not discarded because it cannot answer every question, and it is not stretched beyond its stated audience or role.
Conflict workflow
Detection starts review; it never publishes a candidate fact directly.
Retain the source URL, snapshot, observed date and extracted candidate. Automated systems may flag a mismatch, but the flag stays private until validation confirms that each record is well formed and linked to a real source.
Match provider, legal entity, product, plan, market, customer class, direction and period. Separate different scopes before calling them contradictory. Unknown scope remains a gap; it is not filled from a neighboring market.
Assess source authority and relevance independently. A high-authority source can still be incomplete for the exact field. Marketing prominence and affiliate value never increase evidence authority.
Assign materiality, public summary, resolution state and publication effect. The decision says whether to hold a positive claim, publish the scoped disagreement, defer to customer documents or omit a score or ranking.
Show both values with source IDs and dates when the conflict is safe and useful to expose. Keep private reviewer notes, contact details and unpublished candidate records outside the public view.
A new agreement, fee schedule, register entry, authenticated flow or dated store snapshot can reopen review. Resolution requires an approved evidence relationship; a fresh crawl or model suggestion cannot close the record.
Active conflict filters
United States / plan pricing
Two current first-party Airwallex pages present materially different Grow plan prices in the United States.
Why this remains a conflict: The dedicated pricing page uses a per-active-user price plus a team-size platform fee, while the current business-account page presents a USD 99 monthly figure. Those are not interchangeable totals without the included-user and platform-fee terms.
Dedicated US pricing page
USD 12 per active user per month plus a platform fee based on team sizePublic United States plans and pricing presentation
US business-account page
Grow presented at USD 99 per monthCurrent United States business-account product presentation
Current publication decision
Do not publish one uncontested Grow total or rank Airwallex on that amount. Show the conflict and require the live account quote.
hold positive claimEvidence required to resolve
A current controlling fee schedule or authenticated quote that identifies billing cadence, included active users, platform fee, team-size treatment and effective date.
User boundary: A public list price is not a guaranteed customer quote. Confirm the complete live price before subscribing and keep transaction, FX, card and payment-acceptance fees separate.
United States / banking provider scope
Mercury's legal and disclosure summaries name Choice and Column, while its current business-account page also names Evolve.
Why this remains a conflict: The pages may describe different onboarding cohorts, migrations or product relationships, but the public scope is not explicit enough to assign every customer account to one provider list.
Legal and business disclosure summaries
Choice Financial Group and Column N.A. provide cited business banking servicesCurrent general legal and business banking disclosure
Business-account page and migration guidance
Business FAQ also names Evolve Bank & Trust; partner migration can change the live account bankCurrent product FAQ plus customer-specific migration context
Current publication decision
Publish the partner-list conflict and make the customer's statement and governing agreement control the exact live core bank and routing details.
customer document controlsEvidence required to resolve
A current provider disclosure that scopes Evolve, Choice and Column by customer cohort, product, onboarding or migration state, plus the controlling customer document.
User boundary: A named banking provider, card issuer or programme bank has a specific role. Do not assume every bank listed holds every Mercury balance or provides every product.
France / service legal entity
Two current French N26 pages name different Bitpanda legal entities for N26 Crypto.
Why this remains a conflict: The product page names Bitpanda Asset Management GmbH while the support page names Austrian Bitpanda GmbH. Both were observed on the same date, and the counterparty can affect execution, custody, complaints and controlling terms.
French N26 Crypto product page
Bitpanda Asset Management GmbHProvider named in the public French crypto product and pricing presentation
French N26 Crypto support page
Austrian Bitpanda GmbHDigital-asset service provider named in current French operational guidance
Current publication decision
Keep the exact N26 Crypto counterparty conflicting and require the live French contract before assigning pricing, custody, complaint or legal-entity responsibility.
customer document controlsEvidence required to resolve
The live French N26 Crypto agreement or aligned first-party disclosure naming the full contracting and service-provider entities, addresses, roles, regulator and effective version.
User boundary: N26 Bank SE deposit protection does not extend to crypto assets or resolve the Bitpanda service entity. Review the live order and contract before funding.
United Arab Emirates / market availability
Current Wise UAE pages disagree on whether customers can send from the United Arab Emirates, while the cited ADGM permission is withdrawn.
Why this remains a conflict: Verification and availability pages describe sending from AED or sending worldwide, but the current send-money page says Wise is not ready to let customers send from the UAE and offers a waiting list. The withdrawn Wise Nuqud Ltd permission cannot resolve the current contracting entity.
UAE verification guidance
Describes Emirates ID and UAE residence verification for customers sending from AEDWise UAE verification flow
UAE availability page
Advertises sending money worldwide from supported currenciesWise public UAE availability presentation
UAE send-money page
Says sending from the UAE is not ready and offers a waiting listWise UAE send-money acquisition flow
ADGM public register
Wise Nuqud Ltd permission shown as withdrawn on 26 September 2023Named ADGM entity only; not a universal Wise UAE status
Current publication decision
Keep Wise research-only for positive UAE sending availability and do not name Wise Nuqud Ltd as the current contracting entity.
hold positive claimEvidence required to resolve
Aligned current first-party availability, contracting-entity terms and applicable live regulator record for the exact UAE customer and product flow.
User boundary: Do not rely on a marketing or verification page alone to assume onboarding or sending is live. The authenticated product flow and current contract must agree.
United Kingdom / rating snapshot
Monzo's product page prints an older Google Play rating that differs from the live store snapshot observed later.
Why this remains a conflict: The values refer to different observation dates and publishing surfaces. They demonstrate snapshot drift rather than proving that either value measures reliability or that one source should replace the other without its date.
Monzo personal-account page
Google Play 4.8 as of 27 April 2026Dated marketing snapshot printed on Monzo's product page
Google Play listing
4.2 from about 178,000 reviews at observationLive Google Play listing observed 12 July 2026
Current publication decision
Preserve both dated snapshots, do not blend them and publish no reliability, support-quality or overall review score from either rating.
omit score or rankEvidence required to resolve
A new dated store observation can supersede the live snapshot for freshness, but it cannot turn an app-store rating into independently tested reliability.
User boundary: Store ratings, review counts, downloads and marketing snapshots change and do not establish account safety, service quality, dispute outcomes or product eligibility.
Material field effects
The consequence follows the field and user risk, not the size of the visual difference.
Plan pricing
A monthly number may exclude active-user, platform, transaction, foreign-exchange, card or acceptance fees. When first-party pages show incompatible plan structures, the public page must not rank the provider on either number. It should describe both presentations, name the missing fee components and require a complete live quote.
Market availability
Verification guidance can exist for a flow that is paused, restricted or offered only to selected users. A waitlist can coexist with broad marketing copy. Positive availability stays research-only until the live flow, applicable terms and current legal entity agree for the exact customer and product.
Provider or service entity
Partner banks and service entities can vary by cohort, migration, product or task. A list of institutions is not proof that every institution holds every balance or performs every service. Where public scope remains unclear, the account statement, agreement and live order disclosure control the exact relationship.
Rating snapshot
Store ratings and review counts move continuously. A marketing page may preserve an older snapshot while the store shows another value. Neither establishes account safety, eligibility, support quality or dispute outcomes. The ledger keeps each dated observation and does not blend it into a provider ranking.
Resolution standard
A record can be resolved by aligned current evidence, a controlling document or a reviewed supersession—not by removing the inconvenient source.
Current primary sources identify the same subject, value, market, role and effective period. The reviewer records the new source set and the date alignment was confirmed.
Evidence shows that the claims apply to different plans, customer cohorts, legal entities, products, markets or periods. Each fact can then publish only inside its proven scope.
Public pages may continue to differ, but an authenticated statement, order or agreement establishes the current relationship for that customer. Public copy must retain that limit.
The old source remains in history with its observation or effective period. A reviewer links the replacement and approves which value is active; recency alone does not create that link.
User boundary
The records are not legal, financial, tax or individual eligibility advice. They do not predict whether a provider will accept an application, execute a transfer, restore access, reimburse a loss, protect a particular balance or resolve a complaint. Live agreements, statements, authenticated product screens and applicable regulator records can control a user’s actual position.
If you find evidence that resolves or changes a record, submit the exact page path, market, claim, proposed correction, source URLs and source observation date through the corrections workflow. A submission creates a pending review record; it does not edit a public page or approve a fact automatically.
Continue the audit trail
The evidence-status guide explains the state vocabulary. The source directory exposes reviewed source metadata. The editorial policy defines publication controls, and the changes ledger records approved public history. Each view answers a different question; none substitutes for the exact conflict record.