AffStackDev / Store Credit
Find the original record. Fix the right problem.
Use the balance, linked order or referral claim to understand what happened before creating more value.
For WooCommerce · Free AffStackDev Suite included with a supported plugin download or purchase
Where to start
A small amount of safe context helps.
Identify the workflow
Was this a manual issue, account-credit checkout, purchased gift, referral reward, email, report or integration request?
Check current state
Note available/reserved amounts, order payment state, claim hold/due reason or the existing issuance receipt.
Record the environment
Include the Store Credit, WordPress, PHP and WooCommerce versions, checkout type and relevant companion versions.
Common situations
Do not replace an obligation just because a screen looks wrong.
| Situation | Useful next check |
|---|---|
| Owned credit will not apply | Check login, available/reserved value, expiry, currency, scope and coupon-combining policy. |
| Discount appears, credit stays reserved | Check the original order’s payment state. Awaiting payment normally retains its reservation. |
| Email did not arrive | Inspect the same credit’s send result; recover or resend its notification, not its value. |
| A credit purchase issued only some units | Use the order’s supported retry to verify existing units and issue only missing ones. |
| Referral reward is pending | Check paid date, hold, due reason, original processor and provider availability. |
| Advanced order evidence changed | Use the supported checkout path; do not edit protected metadata to force a match. |
| Payout consumer timed out | Look up the same durable receipt before any new issuance or alternative payment. |
| Reports disagree with a record | Compare date range and sampling with the live credit’s activity and original Woo order. |
Recovery tools
Read-only checks before financial corrections.
Reconciliation checks a bounded sample of accounts, transaction evidence, coupons and linked orders. It flags discrepancies but does not rewrite balances. Site Health checks transactional storage and indexes without repairing the database.
Scheduled work can finish a notification, missing purchase issuance or due referral reward. It does not decide the live checkout balance, reset claim identity or authorize duplicate credit.
Referral review actions retry the original recorded obligation or explicitly cancel it. Unsupported evidence or already-spent reward consequences remain visible for review rather than creating a negative balance.
Updates and backups
Preserve the whole working context.
Back up the database, plugin files and original WordPress security configuration together. Keep later financial activity in mind before restoring a backup; replacing a plugin ZIP does not undo purchases or credit.
Use the optional Test Lab only in a coherent local, development or staging environment. Its fixture scenarios can create and mutate records, and its export may rerun checks. It is not a production customer feature.
For support, share sanitized screenshots and references. Do not include redeemable codes, recipient emails, private messages, payment information or WordPress secret material.
Part of AffStackDev
Your store. Your credit. Clear next steps.
Explore the workflows, read the requirements, and choose the rules that fit your customers.