Admin Portal overview
The Scan to Pay Portal — the web interface for Banks, PSPs, and Merchants to manage their accounts, view transactions, and configure notifications.
The Scan to Pay Portal is the web interface for everyone working with the platform — issuing banks, acquiring banks, PSPs, aggregators, and merchants. Where the API is for automation, the Portal is for day-to-day operational tasks: pulling reports, managing sub-users, configuring notification URLs, regenerating API passwords, looking up specific transactions, and so on.
If you've been onboarded to Scan to Pay, you've been issued Portal credentials. This section documents what's behind that login.
Who uses the Portal
Different roles see different views:
| Role | What they can do |
|---|---|
| Acquirer | Load, manage, disable, and view PSPs and/or merchant information and transactions belonging to the acquirer |
| Issuer | View transactions done on their Scan to Pay wallets |
| PSP / Aggregator | Manage their own merchants — create, suspend, configure |
| Merchant | Manage and set up QR codes, view their own transactions, configure their notification URL, generate API passwords |
| Sub-user | Inherits the permissions assigned by their parent administrator |
The Portal applies role-based access — you only see the merchants, transactions, and configuration that belong to your scope.
What you can do in the Portal
The most common tasks:
| Task | Where |
|---|---|
| Generate or rotate an API password | API tab on your merchant profile |
| Configure a webhook notification URL | Email dropdown (top right) → Notifications |
| Generate a Lib Lite token | Email dropdown → Lib Lite Tokens |
| View transaction history | Transactions menu |
| Look up a specific transaction by reference or transaction ID | Transactions → Search |
| Add a sub-user | Email dropdown → Users → Add User |
| Suspend or reactivate a merchant (PSP / Acquirer roles only) | Merchant list → select merchant → Suspend / Activate |
| Download settlement reports | Reports menu |
For programmatic versions of most of these, see Merchant Onboarding.
Portal URLs
| Environment | URL |
|---|---|
| Sandbox / QA | https://qa.scantopay.io/portal |
| Production | https://scantopay.live/portal |
The Portal supports modern browsers — Chrome, Firefox, Edge, Safari, Opera. If your organisation's firewall restricts outbound access, ensure these URLs are reachable from the workstations where you'll administer the Portal.
Two portals, two environments
Your sandbox Portal profile and your production Portal profile are completely separate. Sub-users, merchant lists, notification URLs, API passwords — everything is environment-specific.
When you move from sandbox to production, you create a fresh administrator account on the production Portal and replicate the merchants you set up in sandbox. There's no migration tool; this is by design (sandbox is throwaway, production is real).
What's next
- Get started with logging in → Admin Portal login
- Programmatic alternatives to most Portal actions → Merchant Onboarding API
- Webhook configuration walk-through → Webhooks
- Customer disputes process → Customer disputes
- Merchant query resolution → Merchant query resolution
Updated 3 days ago