fix: use StripeEventSummary for payment receipt email data #982
Conversation
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
zwidekalanga
force-pushed
the
cnxumalo/fix-payment-receipt-email-zero-values
branch
from
ba7993b to
b82c88d
Compare
iloveagent57
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The payment receipt email was displaying 0 for amount paid and license count because subscription_data (invoice.parent.subscription_details) only contains metadata, not quantity or plan.amount fields.
Now uses StripeEventSummary.get_latest_invoice_paid() to retrieve accurate invoice_quantity, invoice_unit_amount, and invoice_amount_paid.
This repository is deprecated and no longer actively developed.
please reach out to OpenEdx via Slack.