docs: refund limitation + remaining 3.1.0 race residual - #80
Merged
Merged
Conversation
Neither was documented anywhere public before this: a verified, registered payment has no Credit Memo path through Magento (canRefund() is false; refunds go through Paystack's dashboard directly) -- a pre-existing gap, not introduced by 3.1.0, but newly relevant now that orders show a real invoice/total_paid a merchant will expect to be able to refund. And 3.1.0's reference binding closes the sequential "one charge settles two orders" case but not a same-instant race between two verifications for a not-yet-bound reference -- recorded in CHANGELOG's Known Limitations at the same restrained, no-exploit-detail level as the existing D9 entry. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prompted by a direct question after the 3.1.0 release: "are we actually good to deploy on Marketplace, what about the open issues?" Answer was mostly yes, but documentation was incomplete — CHANGELOG's Known Limitations only listed D9/R2.8; two other tracked residuals from the reconciliation work were never made public, and the refund limitation (pre-existing, not new) was undocumented anywhere.
total_paida merchant will reasonably expect to be refundable.None of this changes code — it's the same level of transparency the D9 entry already set, extended to the other two items that should have been there from the start.
🤖 Generated with Claude Code