How do credit holds keep the recipient experience intact?

Holds are recipient-invisible by design; the recipient-visible status is unchanged. Their tracking page renders the normal "processing" copy. Only customer admins see the held queue.

Does the external API contract change?

No. Existing REST API integrations work identically.

Solution

Governed Corporate Gifting

Gifting at scale, with the controls finance demands.

5 layersOptional caps

0%Platform fee

Per-accountOpt-in

Get a proposal Browse the shop

What it is

The program

Multi-level spend caps, a continuous fulfillment credit limit, hierarchical roles, optional teams, recipient-invisible credit holds, and append-only audit ledgers. Delegate gifting to dozens of senders without losing financial control.

What you get

6 capabilities

Five Cap Layers

Per-recipient, per-campaign, per-team, per-user, and account-wide fulfillment credit — all optional, all configurable.

Continuous Credit Limit

Headline number for in-flight (allocated, not invoiced) exposure. Naturally frees as orders move to invoiced.

Recipient-Invisible Holds

Over-cap orders park silently. Recipients always redeem successfully. Admins clear the queue at their pace.

Audit-Trail Native

Every cap edit and every override writes a ledger row with before/after, actor, reason, timestamp.

Hierarchical Roles

Admin / Manager / Sender with optional Teams. Delegate at the right level without privilege creep.

Auto-Release

Held orders clear automatically when invoices land, limits are raised, or period counters reset.

Where teams use it

Common sends

Sales team sends with per-rep capsMarketing campaigns with total budget guardrailsMulti-department spending with separate team budgetsQuarterly team budgets with auto-resetAnti-over-gifting per recipient