Closed cmutel closed 6 months ago
Fixed in commit #bcc5ff1 (as part of #65 -- can't cherry-pick it to a separated main-based branch to review independently due to conflicts).
A view of currency selection in the billing form:
A stripe payment form with currency value, provided to the API:
A fragment of a pdf with correct payment details and currency:
Just realized that we, probably, have to use different stripe products for registrations and memberships. It'd be nice to have it as an issue (if it's necessary).
I don't think we actually need invoice templates, or at least not year. This is because the differences across currencies only really change the incoming bank details, but not the layout or content of the invoice itself. Therefore, we can delete the
template
column.Invoice.template
andInvoice.INVOICE_TEMPLATES
.The incoming bank account details will change based on the currency. Therefore, the invoice context can't hard-code these values. Instead of
default_payment_details
, we need a dictionary: