AffStackDev / Store Credit
Protect the balance. Preserve the evidence.
Server-side ownership, explicit review, repeat-safe references and auditable value changes support responsible credit operations.
For WooCommerce · Free AffStackDev Suite included with a supported plugin download or purchase
Everyday protections
A visible control is not authorization.
Exact ownership
Customer credit actions resolve the signed-in account or the permitted final billing email. A code alone cannot unlock another recipient’s credit.
Deliberate value creation
Staff permissions and request-intent checks accompany live record and amount validation. Issue review and final confirmation are separate steps.
Reserved value
Transactional records and locks prevent the same available value being promised to competing orders.
Stable financial identities
Issuance, purchase units and reward sides retain their business references. An exact retry recovers the original outcome.
Append-only activity
Corrections create new events with reasons and actors rather than rewriting earlier transactions.
Refusal instead of guessing
Unavailable storage, changed evidence or incompatible providers become an error, waiting state or review—not permission to use the face amount.
Saved evidence
Signing is not whole-database encryption.
Purchase, advanced-order, payout and referral evidence bind the approved identities, values and rules. The system checks those signatures before accepting changed data. The underlying records can still contain recipient emails, messages, internal notes and financial relationships.
Protect administrator accounts, hosting, database access and backups. These safeguards do not make a compromised server or arbitrary trusted extension harmless.
Preserve the original WordPress authentication salts with the database and files. Changing them or restoring mismatched site pieces can invalidate historical signed evidence. Recovery should reconcile the original records, not silently re-sign edited history.
Customer privacy
Useful customer views without sharing the other person’s details.
My Account shows owned credit and recent activity, not another customer’s balance. Checkout display data uses masked references. Referral history does not expose the friend’s email, basket or private account information.
The customer-referral program does not import contacts, automatically email a list of invitations or collect an IP fingerprint. Its share token is an invitation context, not authorization to spend another person’s credit. Hosting, analytics and email providers can still process their own operational data.
Export and erasure
Support requests without deleting financial obligations.
The product contributes owner-scoped credit, transaction and referral information to WordPress’s Export Personal Data and Erase Personal Data workflows. WordPress retains the request confirmation and delivery controls. Exports mask redeemable codes and omit private notes and the other referral participant’s information.
Erasure can remove recipient messages and revoke a participant’s sharing link. Balances, ownership, journal identities, transaction history and signed financial evidence remain where needed for operation and duplicate prevention. These tools are not complete anonymization or a regulatory-compliance certification.
Normal deactivation or uninstall preserves live credit, coupons and referral records. Once the referral journal exists, the older developer-only destructive cleanup path is blocked to avoid orphaned obligations.
Support evidence
Share the problem, not the credentials.
Send the affected screen, action, reference version, sanitized error, timing and relevant non-sensitive record reference. Do not send full credit codes, customer emails, private notes, database dumps or WordPress salts through an ordinary support message.
Part of AffStackDev
Your store. Your credit. Clear next steps.
Explore the workflows, read the requirements, and choose the rules that fit your customers.