Admin Portal login

How to register for, log in to, and recover access to the Scan to Pay Portal.

This page covers how Portal accounts are created, how to log in, and what to do when you lose access. For what the Portal is and who uses it, see Admin Portal overview.


Portal URLs

The Portal works in any modern browser — Chrome, Firefox, Edge, Safari. If your organisation's firewall restricts outbound access, ensure these URLs are reachable from the workstations administrators will use.


Registration

Portal accounts are not self-serve. To get one, the Scan to Pay Operations team has to load you. Email [email protected] with:

  • Your name and surname
  • The email address that will be your username
  • Your mobile number

Once the Operations team loads your profile, you'll receive an automated email from [email protected] asking you to set your Portal password.

⚠️

The set-password email expires in 24 hours. If you don't click the link within that window, the link stops working. Email support to have the welcome email reset.


Login

Once your password is set:

  1. Open the Portal URL for your environment.
  2. Enter your email address (it's your username).
  3. Enter the password you set.
  4. Click Sign in.

If your organisation uses SSO or password-rotation policies, configure them around the Portal credential the same way you'd manage any other web app.


Forgotten password

The Portal login page has a Forgot password? link. Enter your email; the system sends a reset link. Same 24-hour expiry as the original welcome email.

If the reset email doesn't arrive (check spam, then check your firewall hasn't blocked [email protected]), email [email protected] to have the reset issued manually.


Sub-users

If you're the administrator for your organisation, you can add sub-users from inside the Portal. Click the email dropdown (top right) → UsersAdd User, fill in their name and email, and assign permissions.

Sub-users receive the same kind of welcome email as the original administrator, and follow the same login flow above.

📘

Sub-users inherit your scope, not your permissions. They can only see merchants / transactions that are under your administration, but the actions they can take are controlled by per-user permission flags you set.


Locked out

If you lose access entirely (administrator left the company, no working credentials, no recovery email working):

  1. Email [email protected] from a verifiable corporate email (ideally from someone authorised on the account).
  2. Include your merchant ID, PSP ID, or acquirer credential identifier so support can find the right profile.
  3. The Operations team will verify identity (usually by phone callback to a number on file) and re-issue the welcome email to a new or existing administrator.

This is an out-of-band process; it can't be self-serve because the platform can't verify it's really you.


Security recommendations

  • Use a unique password for the Portal. Don't reuse credentials with another system.
  • Enable browser-level credential management (or a password manager) — don't write the password down.
  • Rotate proactively. If a sub-user leaves the team, the administrator should immediately revoke their Portal access.
  • Don't share logins. Add a sub-user instead — actions are logged per user, and sharing logins breaks audit trails.

What's next