Secure Account
A private portal for managing legitimate refund cases, with session-based authentication and per-user data isolation.
Submit a refund or payment dispute, attach the evidence that supports it, and follow the review from triage to resolution in a secure portal built for one thing: knowing exactly where your case stands.
•••• •••• •••• 4560
•••• •••• •••• 4560
0k+
Protected transactions
0.0/5
Customer trust rating
0%
Successful recoveries
They fail on the paperwork. Four things go wrong again and again, and none of them are about whether you were owed the money.
A receipt in one inbox, a chat transcript in another, the statement line in a banking app. By the time anyone reviews it, half of it is missing.
“We are looking into it” is not a status. Without a named stage and an owner, a case can sit untouched for weeks and look identical to one being worked on.
Most dispute windows are measured in days. A case that stalls in an inbox often expires before anyone notices it needed a reply.
Each call starts from scratch with someone new. Nothing you said last time is written down anywhere you can point to.
RoyalRefund turns a scattered complaint into a single record with an owner, a stage and a timestamped history — the thing a reviewer can actually decide on.
A private portal for managing legitimate refund cases, with session-based authentication and per-user data isolation.
Submit and manage eligible refund or dispute requests through a guided form that captures everything a reviewer needs.
Organise transaction information and supporting documents in one place so nothing is missing when the review begins.
Follow the status of a submitted case from triage through to resolution, with a timestamped history of every change.
Each stage has a clear owner and a clear exit condition, so a case never sits in an unnamed queue.
Register with your name, email and country. No banking passwords, card PINs or recovery phrases are ever requested.
Describe the transaction and what went wrong. The guided form validates each section before it is submitted.
Attach statements, receipts or correspondence. Files are stored in a private bucket scoped to your account.
A case handler assesses the evidence, requests anything missing and records each decision against the case.
Watch the status move through the pipeline from your dashboard, or with your reference on the public tracker.
When the review closes you receive the outcome, the reasoning behind it and a full copy of the case history.
When a case is approved, the recovered amount is returned to the account it left from, in the currency it was taken in. You see the confirmation the moment it clears.
Amara Osei sending
William Adeyemi receiving
Payment Receipt
Payment Success!
Case RR-2019-0118 has been resolved and the amount returned.
Total returned
$466.50
View case
We work directly with major financial institutions to expedite refund claims on your behalf.
A few words from people whose cases have closed.
The guided form asked for exactly the documents I already had. Uploading everything in one sitting made the whole thing feel manageable.
Being able to check a reference number without logging in is the detail I appreciated most. I stopped refreshing my inbox.
The case timeline reads like an audit log. When a colleague picked the case up, nothing had to be explained twice.
Clear status names beat a vague progress bar. Documents Required told me precisely what was blocking the review.
It never once asked for anything it had no business knowing. That alone put me at ease submitting a case.
These are the controls the platform actually implements, described in the terms an engineer would use. Nothing here claims a certification we cannot evidence.
Sessions are issued and refreshed by Supabase Auth over httpOnly cookies. Passwords are hashed by the provider and are never stored by this application.
Data travels over TLS and sits in a managed Postgres instance encrypted at rest by the provider, with row level security on every table.
Uploads land in a private storage bucket keyed by user id. Files are served through short-lived signed URLs, never public links.
Administrative access is decided by a server-side role lookup and mirrored in database policy. A client-side check alone never grants access.
RoyalRefund will never ask for a banking password, a card PIN, a one-time code, a seed phrase or a private key. If any page ever appears to, close it and report it.
The things people ask most often about submitting and following a case.
Create an account, open your dashboard and choose Start a claim. The form walks through your personal details, the transaction, what went wrong and your supporting documents. You can review everything before submitting, and a reference is issued as soon as you do.
Something not covered here? Ask us directly.

Manage your cases wherever you are. Upload a receipt from your camera roll, answer a reviewer between meetings, and get a notification the moment your status changes.
Download the app
Creating an account takes a minute. Submitting a case takes about ten, and you can save and come back to it. No banking passwords, no PINs, no recovery phrases.
Stay Updated
Product notes and changes to the case workflow. Unsubscribe anytime.