Rewards on every swipe, in your program.

All solutions

Set the rate by merchant, category or company, put promotions on a calendar, and let your customers redeem to a balance or a bank, in your app.

From the rate you set to the cash they redeem.

Set the rate.

By merchant, by category, or on every swipe. Give it dates and it is a promotion.

Keep the ledger.

Every reward is an entry beside the charge that earned it, at the rate on that day. A refund earns nothing.

Visible in your app.

Balances and history in the same screens as spend, in your brand.

Let them redeem.

To a prepaid or credit balance instantly, or to their own bank in one to three days.

Program-level reporting.

Live rules, the blended rate, what is accruing, and the liability against a ceiling you set.

A retention lever.

Cards that earn get used. Usage is what keeps a program alive.

Why run rewards on Outpave.

Fully yours

Your name on the card, the app, and the emails. Your customer relationship stays your customer relationship.

Live sooner

Start on an application platform that already runs instead of building one. Your schedule depends on scope, integration, and provider approvals.

Operated beyond launch

Outpave manages platform security, data storage, disputes, and second-line support. Program obligations are agreed with you and your provider.

Questions we get asked.

Do we have to offer rewards?

No. Programs launch with rewards off and switch them on when the economics make sense. Existing balances stay redeemable if a program is switched off later.

Who funds the rewards?

That is a program design question we work through with you during scope. The platform caps total payout per month and alerts you as accrual approaches the ceiling.

Can rates differ by customer?

Yes, down to the individual company. A rule can apply to every company on the program or to a chosen few.

How is the liability accounted for?

As a subledger per company, beside the charges that earned it. The platform reads the total outstanding; the company redeems against its own balance.

Let’s scope your program.

Thirty minutes, a shared screen, and an honest answer about scope.