What does your team see?
The whole bank report set, and nothing that is not yours. A signed-in contact lands on their program's reports: compliance audit standing per BIN, risk exposure, boarding and underwriting attestation, new-merchant approvals and declines, remediation activity, settlement reconciliation, reserve and funding exposure, and sanctions-screening cuts. Pick a report, pick the month, and run it now, or download what the scheduler already delivered.
Every number reads from the ledger that settles the volume, the same rows QorPay's own operators see, scoped to your program. Nobody prepares an export for you, and nothing is assembled the night before a review; the data your team sees is the data on the platform. When your risk committee meets, the numbers on the table are the numbers on the platform, pulled by your own analyst that morning.
And one report answers a question most programs cannot: who at your bank signed in, what they viewed, and what they exported. The portal's access trail is itself a report your institution can pull, which means your oversight of the program is documented as thoroughly as the program itself.
Your program at a glance
Before any report, the dashboard. Signed-in contacts land on a live view of the program: how many merchants are on your book and how many are boarding, this month's VAMP posture at a glance, reserve exposure, and the boarding pipeline, each tile one press from the report behind it.
Below the tiles, the portfolio's dispute and fraud ratio runs month by month against the network threshold line, with the merchants nearest the line and the largest reserve holders named. The trend an examiner asks about is the first thing your own team sees, current as of the moment the page loads.
How does sign-in work?
With nothing to remember and nothing to leak. Your institution names its contacts; QorPay grants each one and sends an invitation. From then on, sign-in is two steps: the contact enters their registered work email and receives a secure, single-use link that expires in minutes, and opening it prompts for a six-digit code as the second check. There is no password to reset and none to steal.
Sessions are read-only and scoped to your program from the first click, so what a contact can see is decided before they arrive, not filtered after. When someone leaves the bank, a bank admin revokes them in one press, effective immediately. Your security team gets named accounts and a full access trail without managing a single credential.
Alerts between reviews
The portal tells your team when the book moves: a merchant entering a network monitoring program, a sanctions result that needs eyes, a protective action applied, a reserve spike. The feed is shared across your institution's team, severity-coded, and cleared with one press when you are caught up.
What reaches each person's inbox is theirs to choose. Alert settings subscribe a contact to the alerts they care about, by email, in the portal, or both, so your risk analyst and your relationship manager can watch the same book without reading the same mail.
A room for the exam paperwork
Evidence moves in both directions, so the portal gives it a room. QorCommerce posts compliance packets, policy documents, and exam support material to your institution; your team uploads signed attestations, audit requests, and dispute evidence back. Everything is typed, sized, stored encrypted, and downloadable by your team on demand.
And like everything else in the portal, the room keeps its own record: every upload and every download lands in the access trail. When an exam closes, the question of who sent what, and when, has an answer neither side has to reconstruct from email.
Run it yourselves
Bank admins run the portal without a request queue. The Team view manages your own contacts: make a colleague an admin or a viewer, revoke access the day someone leaves, restore it if they return, and reset a lost authenticator, all in one press each. Brand-new contacts are provisioned by QorPay, so every person with access to your program was deliberately granted.
Schedules are self-serve too: create a delivery for any report, set the frequency, time, formats, and recipients, and pause or resume it as review cadences change. When a regulator arrives, examiner access mints a time-boxed, watermarked, read-only window into your reports, revocable at any time, with every view counted. And for institutions that pull data into their own systems, the data feed offers API keys and scheduled file drops, managed from the same place.
Why does this matter for oversight?
Because sponsorship risk lives in the gap between what a program does and what the bank can see, and most programs close that gap with a monthly packet. The Sponsor Portal closes it with a login. Ratios, exposure, boarding activity, and reconciliation are current whenever your team looks, so a question raised in a Tuesday meeting is answered Tuesday, from the source, by your own staff.
Put it in the diligence conversation: ask any program you are evaluating to show you the surface where your team pulls the book directly, and the log it keeps of every pull. We will show you ours, live, in the first session.