Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Send e-mail messages for payments requiring invoices #52

Open
GabrielMajeri opened this issue Mar 26, 2024 · 0 comments
Open

Send e-mail messages for payments requiring invoices #52

GabrielMajeri opened this issue Mar 26, 2024 · 0 comments
Labels
back-end Issue related to the back end logic of the application payment-interface Issues related to the payment interface

Comments

@GabrielMajeri
Copy link
Member

Until #44 gets solved (which might take a while), there's an alternative way in which we could issue invoices for payers using a didactic career premium card. The idea is to send an e-mail to an employee (at the University's Financial Department) who is already responsible for generating invoices for those paying by didactic premium card at the University's cash desk. The employee in question will input the payment information received by e-mail into the EMSYS desktop client app, generate the invoice in the platform and then manually send it back to the payer (again by e-mail).

For these purposes, we've got an unmonitored account created in the University's Microsoft 365 tenant, called [email protected]. I've asked the tenant administrator to add the Mail.Send permission to our app's registration (the same client ID we're using for logging in users) and to configure Exchange Online to allow our app to send mails using that no-reply address.

The steps to send a message from the back end are as follows:

For every payment performed using a didactic career premium card, we should send two messages (after the EuPlătesc callback confirms us that they were successfuly performed):

  • A message to the payer, informing them that the payment has been successfully processed and that they will receive their invoice in 5-10 working days.

  • A message to the employee from the Financial Department (this address could be hard-coded or stored in the app's settings) with the payment information (amount paid, first name, last name, personal code, address etc.)

@GabrielMajeri GabrielMajeri added back-end Issue related to the back end logic of the application payment-interface Issues related to the payment interface labels Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-end Issue related to the back end logic of the application payment-interface Issues related to the payment interface
Projects
None yet
Development

No branches or pull requests

1 participant