NeobankDB is an independent database, comparison, review and transaction-intelligence platform. It is not a bank, lender, broker, exchange, wallet or adviser and does not hold customer funds.
Attribution register / Verified 13 July 2026
A real empty state beats a fictional expert.
NeobankDB currently publishes one verified contributor profile: the NeobankDB organisation credit used where a page explicitly names the organisation as author or publisher. There are no approved named-person profiles and no approved named fact-checker profiles. That absence is published plainly rather than filled with generated names, biographies, credentials, portraits or assignments.
This index is an identity and attribution register, not a staff directory or claim about team size. A contributor count does not measure editorial quality, evidence completeness or review independence. Organisation authorship does not imply that a named individual performed every research, review or publication function.
Public profiles1runtime validated
Organisations1verified first-party record
Verified people0no substitute identities
Named fact-checkers0workflow role not claimed
Identity red line
No person is created to make a page look trustworthy.
A name, portrait and polished biography can create confidence even when none belongs to a real contributor. NeobankDB does not generate those signals. A named profile requires a verified identity, a precise public role, evidence for each credential claim, a scoped page assignment, relevant disclosures and a recorded review date. Missing proof produces no profile, not a plausible placeholder.
The same rule applies to fact-checking. A page may pass evidence validation, source ranking, conflict analysis, tests and approval without claiming a named fact-checker. “Reviewed” is a workflow decision; “fact-checked by Jane Doe” is a separate identity and assignment claim. NeobankDB publishes the second only when that exact record exists.
Verified public profiles
Filter the attribution record.
1 of 1 public profilesZero-count filters are intentional evidence states, not missing UI.
Challenge an attribution or published claim
What the current byline means
Organisation authorship is a boundary, not a hidden person.
It identifies the publication accountable for the public record while declining to invent individual attribution.
NeobankDB owns the published correction trail.
Where a page names NeobankDB as author or publisher, the organisation is accountable for the public evidence display, the rendered explanation, the dated revision and the route through which a correction can be challenged. The credit states which publication issued the page. It aligns with structured data that identifies NeobankDB as an Organization and with the methodology and editorial policy that govern approval.
Organisation attribution also keeps the product boundary visible: NeobankDB is an independent database, comparison, review and transaction-intelligence platform. It is not a bank, lender, broker, exchange, wallet or adviser. Authorship does not create a financial product, customer relationship, account balance or promise of an individual outcome.
No unnamed credential is smuggled into the byline.
The organisation credit does not imply that a licensed lawyer, accountant, financial adviser, compliance officer, former banker or named subject-matter expert wrote or checked the page. It does not claim a particular headcount, editorial board, independent review committee or separation of duties. Those would be new facts requiring their own evidence.
It also does not convert the publication’s research into personalised financial, legal or tax advice. The evidence can explain a provider’s legal structure, market availability, fees, protection model or route conditions. The reader must still evaluate personal eligibility and obtain appropriate professional advice where needed.
Role separation
Author, publisher, reviewer and fact-checker are not synonyms.
Each label answers a different question and needs a separate public or private assignment record.
Who is credited for the editorial work?
A public author can be an organisation or a verified person. The record must name the credited subject and scope the assignment. Current NeobankDB pages use the organisation credit where stated. The index does not infer that every source collector or developer is an author.
Which organisation releases the page?
The publisher is responsible for the public version, metadata, structured data and correction channel. Publisher status does not itself prove that a separate individual reviewed every field, nor does it grant expertise outside the evidence shown on the page.
Was the candidate approved?
Review checks schema, subject, market, source authority, relevance, dates, conflicts and high-risk meaning. A recorded approval is required for publication, but the public page does not name a reviewer unless a verified identity and assignment are deliberately approved for display.
Is a named person credited for claim verification?
A named fact-checker credit requires a real person profile plus an exact assignment. The current count is zero. NeobankDB does not promote the general reviewer function into a named fact-checker badge merely because a page passed validation.
Identity evidence contract
A future named profile must prove more than a display name.
The contract below prevents a contributor page from becoming an unsupported résumé or trust decoration.
The person and the assignment must both be real.
A verified person profile needs stable public identity evidence, a display name the person is entitled to use, an exact contributor role and a review date. NeobankDB must also record whether the person is an author, publisher or named fact-checker for a particular page. General participation does not justify a specific byline, and a byline on one page does not automatically extend to every article in the database.
Retired or withdrawn profiles must preserve prior assignment history where necessary while stopping new attribution. A name change, role change or departure creates a new review event. It does not justify erasing who was publicly credited at the time or continuing to imply an active relationship after it ends.
Each credential claim needs its own evidence.
Degrees, licences, professional memberships, certifications, former employers and years of experience are material identity claims. A profile cannot inherit them from someone with a similar name, a social bio, a generated résumé or the organisation itself. Each claim needs an issuer or controlling record, a public evidence URL, an observation date and a verified state before it appears.
Even a real credential has scope. A legal qualification in one jurisdiction does not turn every product review into legal advice. A finance degree does not prove current regulator expertise. An employer title does not establish independent testing. Copy must explain only what the evidence supports and avoid prestige shorthand that enlarges the claim.
No generated or borrowed headshot.
A profile image is a separate identity and rights record. NeobankDB publishes no portrait unless the asset belongs to the verified contributor, is authorised for the intended use and is linked to the correct person. A generated face, stock portrait or image copied from an unrelated profile would misrepresent identity even if the written name were accurate.
The current organisation record therefore uses a graphic monogram and explicitly records that no approved profile-image URL exists. The monogram is presentation, not evidence of a person or logo ownership claim. Missing photography never blocks an otherwise verified text profile, but it must not be concealed with a fictional likeness.
Conflicts attach to the contributor and assignment.
A relevant employment, investment, advisory, commercial or close personal relationship can affect how readers interpret an assignment. A verified contributor profile must expose relevant disclosures at the appropriate level and keep commercial data separate from the evidence graph. Affiliate compensation cannot change facts, scores, rankings, route verdicts, correction outcomes or conclusions.
Public contact should use a scoped editorial route rather than private financial data. A reader can challenge a byline, credential or assignment through the correction policy with public evidence. NeobankDB does not request passwords, account access, card data, identity documents, private keys or full transaction histories to verify authorship.
Assignment and page history
A contributor profile and a page assignment remain separate records.
This prevents a verified identity from becoming a universal byline or retrospective fact-checker claim.
Attribution follows the exact public page.
A contributor record establishes who the contributor is and which roles may be displayed. An assignment record establishes which page, version and role actually applies. Publishing an author profile does not add that person to every review, comparison, country hub or transaction guide. Publishing a single fact-checker credit does not imply that the person verified later revisions or unrelated markets.
Dates matter. A page should record published and modified dates when its content type requires them, and an assignment should be valid for the version it covers. If a material revision changes the entity, protection, fee, route or scoring analysis, the prior credit cannot automatically prove that the new version received the same individual review.
A trusted name never replaces the source ledger.
A contributor’s experience can inform research questions and editorial judgement, but a named expert cannot approve an unsupported financial fact by reputation alone. Every material claim still needs subject, market, value, source, observed date, verification state and confidence. High-risk legal entity, licence, protection, closure, availability, fee and route claims still require the publication review gate.
If evidence is stale, conflicting or unavailable, the page must preserve that state even when a credentialed person prefers a cleaner answer. Reader trust should follow the visible evidence trail, not a badge. Corrections reopen the claim and assignment history without allowing a contributor name to suppress controlling regulator or legal records.
Why the zero-state is public
Zero verified people is information, not an embarrassment.
It tells the reader exactly which trust signal is absent and which evidence remains available instead.
Sources, dates, states and corrections do the work.
Readers can inspect the approved source directory, market-scoped regulators, protection schemes, payment-rail glossary, evidence-status guide, editorial policy, correction intake and page change ledger. Reviews expose source history and preserve unknown, conditional, stale, conflicting and untested states. These controls are useful even without a named personality attached to the page.
No individual biography or fact-checker badge is implied.
Until real identity and assignment records exist, NeobankDB will not claim a named subject matter expert, licensed professional, independent fact-checker, editor-in-chief or review board. It will not backfill old pages with names for search appearance, invent social profiles, generate testimonials or publish credentials whose issuer and scope cannot be verified.
Follow the accountability trail
Verify the policy, evidence and correction route.
The current contributor record is intentionally small. The methodology explains how research works, the editorial policy defines approval and commercial boundaries, the evidence guide separates decision states, the conflict ledger preserves reviewed disagreements, and the correction page accepts public evidence about an incorrect byline, credential, assignment or claim. A valid correction receipt remains an unapproved candidate and does not silently mutate this index.