Operating notes

What this preview is, and what it refuses to pretend.

Creative direction: composed, precise, commercial, transparent. Ink navy, warm paper, one teal, a wordmark of two paths meeting. No shield, no approval badge, no invented track record.

Assumptions

RevRouters does not process, route or settle funds.
Where Stripe is the existing provider, it remains the processor. This is not an alternative processor.
No legal entity, licence, partnership or approval was supplied, so none is shown.
Live processing stays blocked until permission and agreements exist. Those are not in this preview.
Data you enter stays in this browser.

Unresolved questions

What is the legal entity, company number, registered office and who can bind it?

Not supplied. Omitted from public pages rather than invented. About page says so.

Has any processor been asked, in writing, about this structure?

No evidence supplied. Permission is treated as absent. Activation stays blocked.

How is compensation calculated?

No model agreed. No percentage is published. Internal review task: set a written model before any commercial proposal.

Could RevRouters ever touch the funds flow?

Current description assumes it does not. If that changes, the public explanation has to be rewritten and the missing permissions obtained first.

Who is controller of the personal data, for how long, and on what basis?

Flagged for qualified privacy review. The privacy page is a labelled draft.

Are complaint timings or any ombudsman route a real commitment?

No. The complaints page labels timings as an operating intention pending review.

Which countries will actually be accepted?

Not decided. The form collects country and does not promise cover.

Claim register

Proposed capabilityHomepage

RevRouters introduces merchants seeking processing arrangements to businesses considering a payment partnership.

Evidence: Defined in the operator brief for this build. No operating history supplied. Owner: Operator — named owner not supplied. Review: Before any production launch.

Unverified — omittedNot published

RevRouters is a payment processor, facilitator or merchant of record.

Evidence: No authorisation, scheme registration or merchant-of-record structure supplied. Owner: Operator. Review: Do not publish unless evidence exists.

Rejected as a claimContradicted on the homepage, eligibility and FAQs

An introduction or an active account is processor approval.

Evidence: No processor permission letter supplied. Owner: Operator. Review: Ongoing.

Unverified — omittedNot published

Legal entity, office, founders, licences, certifications, customers, volumes, approval rates.

Evidence: None supplied for this build. Owner: Operator. Review: Publish only the items later evidenced.

Sitemap

Readiness

Homepage, partner page, merchant page

Implemented

How it works, responsibilities, eligibility, about, contact, complaints

Implemented

Guides

Implemented

Stripe accounts briefing

Implemented — explanatory, not a bypass guide

Application forms with validation, save and resume

Implemented in this browser

Submission confirmation without approval language

Implemented

Applicant workspace and review console

Demonstrated with synthetic data, plus anything you submit locally

Activation of processing

Blocked pending approval evidence

Introductions between real parties

Not implemented

Identity, KYB vendors, processor APIs, email, signatures

Awaiting integration

Legal entity and regulatory position

Awaiting operating decisions

Privacy, terms and complaint timings

Awaiting professional review

Company number, address, founders, logos, testimonials, volumes

Omitted — no evidence

Data model

User

Not implemented. This preview has no accounts. Identity is not verified.

Organisation

Represented by the legal name on an application, stored in the browser.

Person

Submitter name and email on the application. Not an identity check.

Ownership relationship

Free-text summary on partner applications. Not verified.

Merchant application

Kind merchant. Separate from partner applications.

Partner application

Kind partner. Cannot see another applicant’s record except in the local review console, which is a preview limitation.

Website

Collected as text. Not crawled or approved.

Product category

Free text, not a controlled catalogue.

Processor

Named by the applicant. No processor API is connected.

Evidence record

Status is one of: Applicant declared, Document supplied, Independently verified, Expired, Rejected, Not assessed.

Approval record

Not created. There is no approval object that can turn processing on.

Review decision

Human-entered status, rationale, scope, conditions, expiry, triggers. Cannot set Active.

Document

File name, type and size only. Bytes are not stored or uploaded.

Agreement version

Sample draft only. No signature, no execution.

Consent

Operational confirmation is separate from optional product news, which defaults to off.

Introduction

Not performed. No matching and no disclosure of one party to another.

Complaint

Stored locally with a stage of “Submission recorded”.

Audit event

Append-only in this browser: submissions, decisions, evidence changes, withdrawals, complaints.

Security and privacy

Server-side authorisation — Specified, not connected

Preview data lives in the browser. A production build needs per-organisation checks on the server, not a hidden flag.

MFA for privileged users — Specified, not connected

No privileged login exists in this preview.

Private document storage and signed links — Specified, not connected

Files are not uploaded. Only a name and size are kept locally.

File type and size checks — Implemented in preview

PDF, PNG, JPEG and WebP only, up to 10 MB. The file is then discarded.

Card numbers, passwords, CVCs — Implemented as a refusal

The form warns on card-like numbers. There is no field for passwords, CVCs or API secrets.

Malware scanning — Specified, not connected

No scanner is wired, because no file is stored.

Rate limiting, sessions, secrets — Specified, not connected

No server session and no secret store. Do not add credentials to the repo.

Audit logging — Demonstrated locally

Events stay in this browser. They are not a central audit system.

Backup, retention, incident response — Awaiting professional review

No retention schedule is claimed. Reset clears this browser only.

Analytics and AI — Implemented as a local log

Events are not sent to an analytics vendor or an AI service. Documents are not submitted to one.

Legal compliance — Not claimed

Controls, even once built, are not a statement of GDPR, PCI or financial-services compliance. Qualified review is required.

Measurement

audience_selected — Recorded locally

Merchant or partner chosen at the start of an application.

cta_engagement — Recorded locally

A primary call to action or an enquiry.

application_started — Recorded locally

The first step of a form was opened.

application_completed — Recorded locally

Submitted for review. Not a qualification.

evidence_completed — Not auto-fired

A file name can be stored. That is not completed evidence.

qualified_application — Not emitted

Nothing in this preview marks an application qualified.

permission_verified — Not emitted

No permission has been verified.

agreement_completed — Not emitted

No agreement can be executed here.

authorised_activation — Not emitted

Activation is blocked.

withdrawal — Recorded locally

Applicant closed the application.

complaint — Recorded locally

A complaint was saved in the browser.

Checks that hold in this build

An active account is not treated as eligibility.
A suspension does not auto-qualify a merchant, and it must be disclosed.
Missing permission blocks activation. The Active status cannot be selected.
There is no sales override.
Privacy and terms are labelled drafts.
Sample companies are labelled. No testimonials, ratings or volumes are invented.
Cross-organisation isolation is not enforced on a server, and the review console says so.