Skip to main content
A member is a Voucherify customer enrolled in a specific loyalty program. Membership is program-scoped. The same customer can be a member of several programs at once, but only once per program; a second enrollment attempt for the same customer is rejected. The customer must already exist in Voucherify, and the target program must be ACTIVE before it can accept new members.

​
Enrollment

Members can be created one at a time, or in bulk through a batch endpoint that processes up to 10 MB of entries asynchronously in batches of 100, tracked as an async action. When a member is created, Voucherify automatically issues one loyalty card for every active card definition assigned to the program, so a member can start with several point wallets at once. Card code generation happens asynchronously, so a newly created card’s code may briefly be null.

​
Member lifecycle

A member is typically ACTIVE on creation, but can also be created as INACTIVE. Use the activate and deactivate endpoints to move a member between these two states. An inactive member can’t earn or spend points. Updating a member merges metadata into the existing object and cannot change status; use activate or deactivate for status transitions. Deleting a member soft-deletes the member and its cards.

​
Loyalty cards and points

Each of a member’s loyalty cards tracks its own balance, lifetime point counters, and upcoming activation or expiration events. Beyond the automatic earning and spending flows, several endpoints let you manage points on a specific card directly:
  • Manually adjust points (positive values create an admin credit, negative values an admin debit).
  • List, and optionally manually activate or cancel, pending points buckets before their scheduled activation date.
  • List, and optionally manually expire, expiring points buckets before their scheduled expiration date.
  • List the full transaction history of a card.
Aggregated daily points and earning-rule usage for a member are covered in the Reports overview.

​
Rewards and payments

Members spend points in two ways, both scoped to a member’s card:
  • Purchasing a reward: Spends points from the card tied to the reward’s cost configuration, and can later be refunded, which returns the points to the card.
  • Paying for an order with points: Spends points based on the card definition’s pay-with-points exchange ratio, capped by the card balance or an optional payment limit, and can be run as a dry run before committing to a real transaction.
Members also expose read-only history for benefit fulfillments and tier transitions (joins, upgrades, downgrades, prolongations, and exits), so you can build a complete activity feed for a member without combining several other endpoints.

​
Member vs. membership

Related endpoints return a member’s data from different angles:
  • Get member returns the member together with its cards within one program.
  • Get program membership additionally enriches each card with tier progress. Use it whenever your integration needs to show progress toward the next loyalty tier.
  • Get customer memberships returns every membership for a customer across programs, including member, program, and cards.
Membership lookups accept a path identifier interpreted through identification_type (for example customer ID or member ID).
Last modified on August 4, 2026