pgeu-system.git - PostgreSQL Europe Conference and Membership management system.

Age	Commit message (Collapse)	Author
2025-06-11	New transferwise APIs no longer allow downloading statements	Magnus Hagander
	So remove the scheduled job that handles them, as well as the database table that stores them.
2020-04-01	Specify on_delete for all ForeignKey and OneToOneFields	Magnus Hagander
	This was already done once in 8289e05cd but had not been properly maintained.
2019-09-06	Add function to send TransferWise monthly statements to treasurer	Magnus Hagander
	TransferWise doesn't send statements automatically, and downloading them is limited by the single-user-per-account-system. But since their API allows downloading of a PDF statement between arbitrary dates, use that to download the statements once per month and email them as an attachment. The function is optional and turned on/off on a per-paymentmethod basis.
2019-06-28	Track transferwise payout status all the way	Magnus Hagander
	The payouts table already had a field for "completed at", but this was never set. Start setting that one, and also track which actual transaction completed a payout. In poassing, make the payment reference field in the payouts table unique.
2019-05-31	Properly set transferwise counterpart name and account	Magnus Hagander
	The code to use them was in place, but it seems I forgot the part that sets them...
2019-05-31	Add support for "return to sender" on bank transfers	Magnus Hagander
	This allows the return of a bank transfer that does not belong to an invoice. A regular refund is attached to an invoice and thus cannot be used. Implement this for TransferWise only at this point, since it's the only bank transfer provider that actually supports sending money. We do this by adding a generic payout framework to it, that we can also use for other things in the future, and then use this one to track return-payments.
2019-03-27	Add payment provider for TransferWise	Magnus Hagander
	This uses the TransferWise REST API to get access to an IBAN account, allowing "traditional" bank paid invoices to be reasonably automated. The provider integrates with the "managed bank transfer" system, thereby handling automated payments using the payment reference. Since this reference is created by us it can be printed on the invoice, making it easier to deal with in traditional corporate environments. Payments that are incorrect in either amount or payment reference will now also show up in the regular "pending bank transactions" view and can be processed manually as necessary. For most SEPA transfers, TransferWise will be able to provide the IBAN number to the sending account. When this is the case, the provider also supports refunds, that will be issued as general IBAN transfers to tihs account. Note that refunds requires the API token to have "full access" as it's permissions in the TW system, meaning it can make arbitrary transfers of any funds. There is no way to specifically tie it to just refunds, as these are just transfers and not payments.