closes odoo/odoo#35754 Signed-off-by: Damien Bouvy (dbo) <dbo@odoo.com>
The description should be an action for the user (i.e. "with this module, you can ...") Correct English errors
Purpose of the task is, there is no easy way to request custom online payments on sales orders or invoices. The only way is to create an URL manually: /website_payment/pay?reference=inv-008&amount=123¤cy_id=1 So added menu 'Generate payment link' in action in sales order and invoice. while making payment pass the partner so reconcilation account flow should not break as partner_id on account payment is reauired to reconcile. co-authored-by: sza-odoo <sza@odoo.com> Task-1938635 Closes: #31575
This commit aims to improve the user experience when using payment acquirers. There currently are no error feedback with some acquirers, which leaves the user wondering what is going on and what is the real status of its payment. In some cases, the user is currently being redirected to the home page even though the payment has failed. We want to make it more obvious to the user that something unexpected has happened by redirecting to an intermediate page that will provide good feedback on payments status. Another goal of this commit is to order acquirers by sequence instead of by flow and to select the first acquirer by default. This feature was already implmented in commit fe294fd43e521bd2d339e962f43acf46c3d4cb97, some UI adaptations were needed though. Related to task #36680 Closes #26958
Help users configure the system in order to send the first quotation to a customer. This panel appears above the sale quotations list. task: 1839195
Add an onboarding panel for invoicing, it appears above the invoice list. After going through the steps the system should be all set to send real invoices. In the payment module, add a payment acquirer step and add it to the invoice onboarding panel. task: 60668
It was very confusing for the user to distinct account.payment and payment.transaction. From now on, the transactions are technical objects and, in the backend, we only refer to it in log messages (Front end will be adapted in the same fashion later on). They are hidden in debug mode in accounting\configuration\payments as their purpose is now purely technical/log This commit also aims to reduce the gap between the accounting app and the transactions: account.payment objects are created/validated upon completion of transaction. To ease the capture/voiding of pending transactions, the related buttons are now displayed directly on the SO/invoice instead of the transactions. Was task: https://www.odoo.com/web#id=35857&view_type=form&model=project.task&action=333&active_id=967&menu_id=4720 Was PR #24043 [FIX] add domain based on journal to payment tokens Was opw: https://www.odoo.com/web?debug#id=1828206&view_type=form&model=project.task&menu_id=5200
- Added the most used payment option (credit cards) in the world and assigned which payment acquirers can use them. - Added the form templates for each payment acquirer.
Customer portal controller and templates contained in website_payment module are moved to payment. This module now uses the customer portal defined in portal module and most of website_payment code is moved to payment. website_payment now contain code really related to website, such as payment acquirers configuration for website.