Hyperwallet Integration in Roster Op: How Payments Work

Schools paid student-athletes $1.77 billion in revenue sharing payments in 2025-26, according to the College Sports Commission. Nearly 35,000 athletes at 307 schools received a payment. For some business offices, each payment run still starts with a spreadsheet export and ends with staff re-checking the file by hand.

The Hyperwallet integration in Roster Op replaces that routine with a direct API connection. Roster Op is LBi Software’s connected platform for roster and revenue-share decisions in college athletics, built by the team behind CAPS, the College Athlete Payment System. With the integration, athletic departments handle account setup through payment reconciliation in one system, with fewer clicks and no double entry.

This guide explains how the integration works and what your staff gets when it launches in February 2027.

Key Takeaways

  • The Hyperwallet integration is the Payments module inside Roster Op, connected directly to the Hyperwallet API.
  • Staff build and approve payment runs in Roster Op, with fewer clicks and no file uploads.
  • Built-in guardrails check funding before each run and flag account changes that affect a payment.
  • Roster Op reconciles each payment from gross to net, tracks the withholding, and keeps a full audit trail of every payment.
  • The integration is part of Roster Op, so the roster decision and the payment share one record.

What Is the Hyperwallet Integration in Roster Op?

The Hyperwallet integration is the Payments module inside Roster Op, and it connects directly to the Hyperwallet API. Staff set up athlete payout accounts in Roster Op and build payment runs from signed agreements. Roster Op sends payment instructions straight to Hyperwallet, then tracks each payment through reconciliation.

Hyperwallet is PayPal’s payout platform for sending payments to large groups of payees. PayPal now markets it as Enterprise Payouts. In June 2025, PayPal announced agreements with the Big Ten and Big 12 to deliver institutional payments to student-athletes.

The Roster Op Hyperwallet module sits beside the Budget tool at the top of Roster Op, above the Football, Basketball, and Baseball modules. The roster decision, the budget against the cap, and the payment stay in one place. It works as student-athlete payment software inside the platform a program already uses for roster decisions.

Learn more about Roster Op.

How Revenue Sharing Works Under the House v. NCAA Settlement

The House v. NCAA settlement, approved in June 2025, lets schools pay athletes directly. It also provides about $2.8 billion in back damages to former athletes over 10 years. Under the revenue-sharing model, each school signs revenue-sharing agreements with its athletes and pays them on a set schedule.

Those payments are separate from third-party NIL deals. In a name, image, and likeness (NIL) deal, an outside company pays the athlete. The Hyperwallet integration covers the payments a school makes under its own revenue-share agreements.

Why Do Revenue-Share Payments Need a Better Process?

Revenue sharing keeps growing. The cap for 2026-27 is about $21.3 million per school. Under the current settlement terms, the College Sports Commission expects another 4% increase for 2027-28. Every one of those dollars has to reach the right athlete on schedule.

The revenue-sharing payment workflow at some schools still depends on manual file handling. A typical run looks like this:

  1. Export the disbursement file from CAPS or an internal database, then fill in the missing fields.
  2. Upload the file to a shared folder and wait for sign-off.
  3. Upload the approved file again, this time to Hyperwallet.
  4. Chase payment status and reports across three systems.

That’s four handoffs across three systems.

Every handoff adds clicks and risk. One value pasted into the wrong row can send the wrong amount to the wrong athlete. Some staff download the uploaded file again and check it against their records before they approve a run.

The process also hides information. A business office may not learn that an athlete never finished account setup until the first payment goes out.

How Does the Hyperwallet Integration Work?

The integration replaces file handling with a direct connection between Roster Op and the Hyperwallet API. Agreements and approvals live in Roster Op, and payment instructions travel straight to Hyperwallet. Status comes back to Roster Op in real time, so staff work in one system instead of three.

Stage    Manual process today    With the Hyperwallet integration
Agreement data    Exported from CAPS or an internal database, then edited by hand    Agreements live in Roster Op
Approval    File uploaded to a shared folder for sign-off    Approval happens inside the payment run
Sending payments    Approved file uploaded again to Hyperwallet    Instructions go straight to Hyperwallet
Status and reconciliation    Staff chase status and reports across three systems    Real-time status, reconciled automatically

1. Set Up Accounts and Agreements

Staff create Hyperwallet accounts for athletes inside Roster Op. Existing athlete accounts link automatically, so a program doesn’t start from zero. Through the Hyperwallet API, staff can review athlete accounts in real time without logging in to a second portal. Agreements stay in Roster Op, next to the roster and cap data.

2. Build and Approve a Payment Run

Roster Op builds each payment run from the rosters and agreements a program tracks. Each school chooses its approval flow: one step or two. After approval, Roster Op sends payment instructions straight to Hyperwallet.

3. Let the Guardrails Catch Problems Early

Roster Op checks each run before money moves:

  • A funding check confirms the money is there before a run goes out.
  • Roster Op flags a change in an athlete’s under-18 status.
  • Roster Op flags a change in entity type, such as an athlete who forms an LLC.
  • Roster Op flags a change in tax details.
  • Each school sets its own under-18 payment method: a Venmo Teen Account with its limit tracked, or a mailed check.

4. Track Every Payment to Reconciliation

Roster Op sends a status notification on every payment. It reconciles each payment from gross to net and records the withholding in between. Staff see real-time status and a full audit trail in the same system that holds the revenue sharing agreements.

What Do Programs Get at Go-Live?

Payments go live in February 2027. Every feature above arrives together at launch. LBi supports the rollout in three ways:

  • Onboarding: dedicated help with initial setup, so account and agreement data loads accurately.
  • Training: two sessions timed to payment cycles. One runs before end-of-month payment runs, and one serves mid-month payers.
  • Documentation: a knowledge base with FAQs and process guides, so answers don’t depend on reaching someone live.

After go-live, the LBi support desk gives staff one team to call.

Why Keep Payments Inside Roster Op?

Roster Op puts the decision and the payment in one system. The agreement a general manager negotiates is the same record the business office pays from. Nobody enters the same deal twice.

That link matters for cap management. Roster Op’s Budget tool tracks multiple cap years within a single football season. With payments in the same system, staff see what a program has paid next to what it has committed. That view supports long-term planning as well as this month’s payment run.

The integration also comes from a team that knows the rules. LBi Software and the College Sports Commission developed CAPS, the system participating schools use to manage and report revenue sharing. LBi has built software for sports organizations for more than 40 years, including cap and contract systems for MLB, the NBA, and the NFL. Roster Op itself was designed with Power 4 athletic departments, and the schools defined the workflow. Hyperwallet inside Roster Op is also a low-cost way to run revenue-share payments.

If a program’s payment tool only moves money, it’s running the amateur version: the cap and the agreement still live somewhere else. Roster Op is the pro version.

Who Is the Hyperwallet Integration For?

The integration serves the people in college athletics who touch revenue-share payments:

  • CFOs, deputy ADs for finance, and business office staff who build and approve payment runs and need to explain every dollar
  • General managers and roster directors who negotiate the agreements
  • Compliance staff who need a clean audit trail and payment records that match agreements

Each group works from the same record in one system, which cuts the clicks and cross-checking between files.

Frequently Asked Questions

What is Hyperwallet?

Hyperwallet is PayPal’s payout platform for sending payments to many payees at once. PayPal now markets it as Enterprise Payouts. Organizations connect through the Hyperwallet API or by uploading payment files. Across the platform, PayPal lists payout methods that include a bank account and a debit card.

How do schools pay student-athletes revenue share?

Schools sign revenue-share agreements with athletes, then pay on the agreed schedule through a payment provider. Participating schools report those payments in CAPS. With the Hyperwallet integration, a program builds and approves those payments inside Roster Op, then tracks each one.

How are under-18 student-athletes paid revenue share?

With the Hyperwallet integration, each school sets its own method. The options are a Venmo Teen Account, with its limit tracked in Roster Op, or a mailed check. Roster Op also flags a change in an athlete’s under-18 status.

Does Roster Op replace CAPS?

No. The College Athlete Payment System (CAPS) remains the system participating schools use to manage and report revenue sharing to the College Sports Commission. The Hyperwallet integration handles the payment workflow inside Roster Op.

Is the Hyperwallet integration a separate product?

No. It is the Payments module within Roster Op. Programs use it alongside the Budget tool and the Football, Basketball, and Baseball modules. It handles revenue-share payments for every sport an athletic department pays.

When does the Hyperwallet integration in Roster Op launch?

The Hyperwallet integration launches in February 2027.

How to automate revenue-share payments to college athletes?

Replace file uploads with a direct connection to the payment provider. In Roster Op, staff build a payment run from signed revenue-sharing agreements and approve it. Roster Op then sends the instructions to Hyperwallet and reports each payment’s status in real time.

One Process From Account Setup to Reconciliation

The bottom line: the Hyperwallet integration gives athletic departments one process from account setup to payment reconciliation. Staff stop moving files between systems and clicking through three tools to finish one payment run. Every payment carries a live status, and the agreement and the payout share one record in Roster Op.

One system for the decision and the payment.

Ready to see a payment run from start to finish? Contact LBi Software to schedule a Roster Op demo.