A B2B customer portal should let the right person complete a billing task without giving everyone the same access. Receiving an invoice email, viewing an invoice, managing a payment method and cancelling a service are different responsibilities.
For agencies, consultants and subscription businesses, start with who does what inside the customer’s company. Then select the available role that matches those duties. Do not assume that a role named “billing” means read-only access for an accountant.
Separate the customer company from its contacts
The company is the billing relationship. Its owner, finance employee and operations contact are people acting within that relationship. Keep individual access tied to the intended company rather than encouraging everyone to forward one sign-in link.
In the reviewed PayRequest code, customer contacts can have portal access enabled and a portal role assigned. Billing and account email preferences are separate fields. Receiving notifications is therefore not the same setting as being allowed into the portal.
That distinction helps when an employee wants invoice emails but should not manage services, or a technician needs service information without changing payment methods. Confirm the current role behavior for the tasks that matter to your business.
Choose B2B customer portal roles by task
The following summarizes the current access definitions reviewed for this article. It is not an end-to-end authorization certification, and role names should not replace a practical test.
| Portal role | Access indicated by the reviewed definitions | Selection question |
|---|---|---|
| Admin | Broad access within the customer relationship | Should this contact manage the account? |
| Billing | Invoices, payment methods, subscription viewing and billing | May this person manage payment methods? |
| Operations | Orders, subscription viewing and support | Does the person need operational context? |
| Viewer | Invoice, order and subscription viewing plus support viewing | Is this broader than the read access you intended? |
An external accountant who only needs invoice copies may require a narrower workflow than the available viewer role. Do not advertise an invoice-only accountant role unless it has actually been implemented and verified.
Test B2B customer portal access before inviting contacts
Create a separate test contact for each role. For each one, record whether they should view invoices, download copies, manage payment methods, view subscriptions, change account settings and access support.
Then verify both the expected allowed tasks and the tasks that should be unavailable. Test with the contact’s own login rather than an administrator session. Check the intended customer account and confirm that removing contact access stops future access as designed.
This original checklist is a purchasing and configuration tool. It does not claim that live customer permissions were tested as part of writing this article.
Example: an agency customer changes finance staff
A fictional maintenance customer replaces its finance employee. The old contact received invoices and had billing access. The agency should identify the new person, confirm their responsibilities, review notification preferences and remove the former contact’s access when appropriate.
Do not simply forward the previous person’s portal link or change one shared mailbox password. Recheck which contact can manage payment methods, who receives notices and who can ask billing questions. Keep the customer owner involved in deciding access.
When a customer only needs a missing invoice, start with invoice access rather than granting broad account administration. If the request needs clarification, use support requests to keep the discussion and relevant documents together.
How this differs from Stripe portal branding
Stripe already supports branded billing self-service. Its no-code customer portal and configuration documentation cover customer access and billing actions. A logo or custom domain alone is not a reason to replace it.
The buying question here is how your application represents several people within one customer company and which actions each may perform. Do not infer that a connected payment provider supplies your entire B2B permission model.
Explore the PayRequest customer portal and the Stripe Customer Portal alternative to compare billing, contact access and support as one customer experience. Confirm the required plan and actual configuration on the pricing page before inviting your first customer contacts.
When one contact cannot see the right subscription, follow the record-matching investigation before broadening access.
Editorial note: AI assisted this article and its cover. PayRequest access definitions and contact settings were reviewed on 19 October 2026. The agency example is hypothetical; no production permissions were changed.
