Built for WooCommerce on WordPress · v2.2.0 // how it works

How CreditKit Pro works, end to end.

Two flows tell the whole story: a customer paying for an order in credits, and a team spending a shared prepaid budget with approval. Everything else — the ledger, the gateway, the webhooks — sits underneath these two.

// flow 1
CreditKit Pro My Credits: a customer balance in credits with a recent-activity ledger

A customer pays for an order in credits.

Members hold a credit balance. At checkout, the pay-with-credits gateway covers the whole order from that balance — all-or-nothing, never a part-credit-part-card split.

Top up

A customer buys a credit bundle (a WooCommerce product), or you grant credits manually. The balance lands in their account, recorded in the ledger.

STEP 1

Spend at checkout

On a credits-payable product the Credit gateway is offered. If the balance covers the order it pays in full; if not, the gateway is hidden and a “Buy credits” link sends them to top up first.

STEP 2

It is on the ledger

The spend is one atomic, signed transaction. The customer sees their new balance and full history in My Account; you see it in Transactions.

STEP 3
// flow 2 · the part no one else ships
CreditKit Pro My Team: a member requests credits with threshold-gated manager approval

A team spends a shared budget, with approval.

Turn on Groups & Budgets and the same engine runs a B2B program: a pooled prepaid budget, spent by many members, with manager approval on the transactions that cross your threshold.

Fund the pool

Create a group, add members, and top up one shared credit budget. No per-member allowances to maintain, no card on file.

STEP 1

Set the threshold

Choose a credit amount above which spends need sign-off. Below it, members buy freely; above it, the spend waits.

STEP 2

Approve per transaction

A manager approves or rejects each over-threshold spend before the credits leave the pool — every time, not a one-off sign-off.

STEP 3
// under the hood

Built so the ledger always balances.

Atomic spend

Every debit is a single guarded operation, so a shared balance can’t be pushed negative by two people at once.

SAFE

Signed ledger

Every credit movement is a timestamped, signed transaction — a real audit trail, not a single balance field.

AUDIT

REST + webhooks

Automate top-ups and react to events with a documented REST API and signed webhooks for key credit, team & security events.

API

Buy CreditKit Pro See every feature →