One connected suite.
Every payment moment in view.
Juice brings six connected products for admin workflows, payment access, mobile and web self-service, deeper program reporting, and implementation support into one operating model. Together, they help client teams control complex programs while claimants, beneficiaries, members, cardholders, and other payees get a clearer experience.
SIX SURFACES · ONE OPERATING MODEL · CHAIN, NOT CATALOG
The right product for the right moment.
A payment program has more than one user and more than one job. Juice Pro supports the admin side. Payments Center helps recipients move through configured payment choices. Juice Mobile and Juice User support day-to-day cardholder access. Juice Enterprise gives authorized teams a deeper program and reporting view. Quickstart supports the work of getting a program configured. Not every program uses every product, and exact scope varies by program, role, environment, and approved access.
Choose the surface that fits the job.
Juice Pro
Juice Pro gives program and operations teams a structured place to manage supported payment workflows, review records, work with payees, and keep approvals, exceptions, and day-to-day visibility in view. It is the admin surface of the suite: not the recipient portal and not a payment rail.
WHO IT IS FORClient program teams, operations teams, and administrators running supported payment workflows.
WHAT IT HELPS THEM DOPayments Center
Juice Payments Center gives claimants, beneficiaries, partners, and other payees a guided, branded path through configured payment or payout choices. It keeps the last-mile experience connected to the program’s controls without asking recipients to navigate the admin workflow.
WHO IT IS FORPayees moving through a configured client or program payment flow.
WHAT IT HELPS THEM DOJuice Mobile
Juice Mobile gives cardholders a native mobile path to account access, balances, activity, supported card controls, receipts, and support. It extends the branded experience beyond the payment moment, with specific actions and availability varying by program.
WHO IT IS FORCardholders and other end users whose program includes the Juice Mobile experience.
WHAT IT HELPS THEM DOJuice User
Juice User is the cardholder-facing web portal for supported account activity, including balances, transactions, receipts, statements, card settings, and other account tools. It complements Juice Mobile with a browser path and remains separate from client-admin workflows.
WHO IT IS FORCardholders and other end users who need browser-based access to their program account.
WHAT IT HELPS THEM DOJuice Enterprise
Juice Enterprise, our Program & Data Platform (PDP), connects program configuration, transaction context, reporting, reconciliation, and operational visibility around complex payment programs. It gives program, operations, finance, support, and implementation teams a clearer way to understand payment activity without stitching together disconnected views.
WHO IT IS FOREnterprise program owners, operations and finance leaders, implementation teams, support leaders, and technical stakeholders who need deeper context around complex payment-program activity.
WHAT IT HELPS THEM DOJuice Enterprise capabilities, screens, roles, reports, integrations, data coverage, retention, support visibility, and workflow ownership vary by program, client configuration, environment, applicable requirements, and approved access. It is an enterprise/admin and data surface, not a payment rail and not a replacement for the client’s policy, claims, fiduciary, finance, legal, or eligibility decisions.
Juice Quickstart
Juice Quickstart helps clients organize branding, communications, and use-case setup through a structured implementation path. It is the post-sale configuration surface; it does not replace the business onboarding/help hub and it is not a public credential-entry page.
WHO IT IS FORClient implementation teams, program owners, and authorized users preparing a Juice program for launch or change.
WHAT IT HELPS THEM DOOne program. Different surfaces.
Juice connects the work behind a payment to the experience on the other end. Client teams can manage the workflow. Recipients can follow a clearer path to payment. Cardholders can use mobile or browser self-service. Enterprise teams can bring deeper program context into reporting and reconciliation. Implementation teams can configure the experience before it reaches the people who depend on it.
| Layer | Product | Primary job | Primary user |
|---|---|---|---|
| Admin workflow | Juice Pro | Manage supported workflows, payees, approvals, records, and operational visibility. | Client program and operations teams |
| Recipient journey | Payments Center | Guide configured payment access and payment-choice moments. | Claimants, beneficiaries, partners, and other payees |
| Mobile self-service | Juice Mobile | Support phone-based account access, activity, supported card actions, receipts, and help. | Cardholders and supported end users |
| Web self-service | Juice User | Support browser-based account, transaction, receipt, statement, and card-management tasks. | Cardholders and supported end users |
| Program data and administration | Juice Enterprise | Bring deeper program context, reporting, reconciliation, audit, and operational investigation into view where configured. | Enterprise, finance, operations, support, and implementation teams |
| Implementation | Juice Quickstart | Organize branding, communications, and use-case configuration for launch and change. | Client implementation and program teams |
Product scope varies by program. The right combination depends on the workflow, user role, client configuration, connected systems, and approved access.
Existing users
Product marketing explains the role of each surface. Login and Help route existing users to the correct environment.
The products do different jobs. One orchestration model.
Juice brings admin workflows, payment access, mobile and web self-service, deeper program reporting, and implementation support into one connected operating model.