Skip to main content
PRODUCTS · JUICE MOBILE

In their hands.
The program lives where
the cardholder lives.

Juice Mobile is the native app for iOS and Android your cardholders carry: balance and activity up front, cards they can activate, lock, and reveal themselves, and in-app help, all under your program's brand and rules.

Talk to Sales→See the controls→
9:41
Juice
•••• 6217
Activate your card
Set a 4-digit PIN to activate card •••• 6217.

ILLUSTRATIVE SCENARIO · ACTIVATE, LOCK, AND VERIFY-TO-REVEAL ON A WORKING PHONE

Where cardholder experience breaks

The card is issued. The relationship is not.

Programs spend months earning a cardholder's trust, then hand the daily experience to a phone queue and a generic portal. The phone in their pocket is where that trust is kept or lost.

01
The card arrives, the questions follow
How do I activate it? What is my balance? Did that payment go through? Without self-service, every one becomes a call.
02
A lost card becomes a lost week
If locking a card means a phone queue, the cardholder either waits exposed or gives up and calls your program.
03
Card details get shared carelessly
When people cannot see their own virtual card safely, they read numbers aloud, text them, and write them down.
04
The program's brand stops at the envelope
A generic app experience at the moment of daily use spends the trust the program earned at enrollment.
One app, many cardholders

The cardholder is never one person

Different people, different situations, different levels of confidence with a card. The app has to work for all of them without becoming six products.

Claimants spending a payout
Beneficiaries with controlled access
Members with benefit cards
Paycard workers on payday
Cardholders traveling
Caregivers helping a recipient
First-time card users
Recipients replacing a lost card
Anyone checking a balance at midnight
Everyday self-service

What cardholders do without calling anyone

The daily actions that used to generate support calls, each one resolved in the app.

Balance and activity, first

The dashboard opens with what matters: available balance and recent activity, no digging.

Activation in the app

New or replacement cards activate with a PIN and a one-time code, right from the dashboard, no call required.

Lock and unlock from the phone

Misplaced the card? Lock it from the dashboard. New purchases decline while it is locked.

Card details behind verification

The virtual card stays hidden until the cardholder verifies. Numbers are seen, not shared.

Receipts and transaction review

Purchases can be reviewed and receipts attached from the same screen the charge appears on.

Support inside the app

Help lives where the questions arise, with the program's support model behind it.

Controls

Consumer-simple surface, program-grade rules

The app feels effortless because the program's decisions are already baked into every screen.

Your brand, not ours

The app carries the program's identity, so daily use reinforces the relationship the program owns.

Verification on high-risk actions

Activation, card reveal, and sensitive changes sit behind one-time codes, completed by the cardholder.

Program-configured features

Which capabilities a cardholder sees follows the program's configuration, not a universal checklist.

Direct deposit details, self-served

Where the program offers it, account and routing details live in the app, so setup does not need a call.

Support routing back to the program

In-app help connects to the program's support path, with context attached.

Clear status language

Balances, banners, and states say what is happening and what to do next, in plain terms.

Self-service where it counts

Activation, lock, balance, receipts, and recovery resolve in the app instead of the queue.

Connected to the program

What the cardholder sees reflects the program's rules, from access to support.

What buyers ask

Straight answers before the first call

Why does a payment program need a mobile experience?

Because recipients live on their phones. The app gives them a familiar way to view activity, access funds, and follow program guidance. Its value is the clearer connection between the payment moment, the next step, and the controls and support around it.

What should end users be able to do?

Check balances and activity, activate and control cards, review transactions, attach receipts, and reach support, from a branded experience. Exact functions depend on product configuration and the cardholder's relationship to the program.

How does Mobile stay connected to administrator oversight?

The app is one layer of the program, not a separate consumer product. It connects to client-defined rules, payment activity, reporting, support, and exception workflows: a simpler user moment on top of a controlled operating model.

Who owns what

Your program sets the rules. The app carries them daily.

YOUR TEAM DECIDES
Program rules and cardholder access
Which features are available
The support model
Branding and communications
Exception and dispute decisions
JUICE SUPPORTS
The native app experience
Card controls and verification flows
Balance, activity, and receipts
In-app support paths
Reporting around cardholder activity

Juice Mobile carries your program to the cardholder. It does not decide what the program allows.

Who feels it

When the app works, the program feels present

01

Cardholders

Activate, lock, check, and resolve from the phone in their pocket.

02

Support teams

Balance, activation, and lost-card answers live in the app, where cardholders look first.

03

Program owners

Daily cardholder activity that reflects the program's rules and brand, not a third party's.

04

The brand

Every balance check reinforces the program the cardholder actually belongs to.

Put the program in their pocket.

If cardholders still call for balances, activations, and lost cards, let's look at what your program could hand them instead.