I well not actually write a “log” here, just some brief notes.
Here is the current status
-
account_payment_talermodule implemented, following the ones for stripe and braintree. This implements- extensions to
PaymentandPaymentJournalto support Taler - a Taler Merchant Account class providing the configuration for accessing the account, defaults fpr pay/refund/wire delays and the possibility to overwrite the currency (so one can easily test with some merchant instance)
- cron jobs for pushing new payments/orders and refunds to the merchant backend and pulling updates
- a custom “checkout” web page to be integrated into a web shop (in case one does no want to directly forward to the Taler order status page).
- a “checkout email” report, anyhow I don’t know where this is used (see Where is
Payment._send_email_checkout()used? in the Tryton forum)
There are still some pieces missing though.
- extensions to
-
written documentation and tutorials
-
added a test-suite which uses the demo backend and required interaction for paying and taking the refund.
Issues I’m facing
-
Tryton does not provide a “standard” or “example” web shop. Thus I can not integrate Taler payment into some actual workflow – and not even write a tutorial how to.
-
Looks like I can’t create (pro forma) invoices containing the QR code for a Taler payment, see the main developer’s comment at Creating a Taler payment for invoicing - #4 by ced - Developer - Tryton Discussion.
Limitations
- The implementation will not (yet) support all features of Taler Merchant like tokens, public reorder url, auto refund, etc. The main reason for this is: I don’t know the business side of this. Of course I’d be easy to add the required fields to the Payment class – but IMHO its not a good idea to put all these into the forms.