[IMP] payment, *: payment methods overhaul#120446
Closed
AntoineVDV wants to merge 4 commits intoodoo:masterfrom
Closed
[IMP] payment, *: payment methods overhaul#120446AntoineVDV wants to merge 4 commits intoodoo:masterfrom
AntoineVDV wants to merge 4 commits intoodoo:masterfrom
Conversation
Contributor
1a90e7b to
8c2f771
Compare
588c092 to
f846376
Compare
066095f to
65db3ab
Compare
6976256 to
5343d4e
Compare
cc52a03 to
ba85f7c
Compare
a01db20 to
cfbc2c2
Compare
7fbddd6 to
4f6ddda
Compare
4ceae7c to
8017cc3
Compare
Feyensv
reviewed
Sep 18, 2023
6efd159 to
bc59d6a
Compare
bc59d6a to
36b8c83
Compare
Contributor
Author
|
@robodoo rebase-ff @robodoo override=ci/security |
Contributor
|
Merge method set to rebase and fast-forward. |
This commit mainly removes the extra indent level left over after commit odoo/odoo@8ec2e8cf. It also cleans up purely cosmetic code styling inconsistencies. task-2882677
Several functions were: - called with `await` while there are synchronous; - declared as synchronous while they should have been asynchronous; - declared as synchronous but their overrides were async; - explicitly encapsulating their return values in a `Promise` when it was unnecessary. This commit also cleans up a few mistakes in comments and docstrings. task-2882677
…orms Before this commit, the payment providers (e.g., Stripe, Adyen...) available for payment were displayed on the payment forms. The customer had to select one to process their payment. After that, the customer had to select their preferred payment method (e.g., Credit Card, Bancontact...) from a list of payment methods supported by the selected provider over which the website administrator had close to no control. This was making the payment forms confusing because the payment methods were displayed sometimes more than once, if at all, in a non-controlled order, and behind the selection of a payment provider that customers should not have to deal with. As the payment method was selected in an iframe or directly on the provider's website, the information on the selection payment method was not available in Odoo. This posed many problems, among which were the impossibility of assessing whether a specific feature (e.g., tokenization, refunds, manual capture...) was available, not being able to easily identify payment tokens through the payment method logo, listing available payment methods on the website, sorting and fine-grained configuration of the available payment method, subpar payment method-specific display on the payment form (e.g., PayPal that requires displaying a "Pay with PayPal" button), etc. In this commit, the payment providers are thus replaced by the payment methods on the payment forms. All contextually available (depending on the country, currency, requested feature...) payment methods are displayed one after the other on a single-level list and in the order configured by the website administrator. Each payment method is "powered by" (i.e., linked) to a single payment provider: the first one, by model order, to support it. This allows, for example, offering the PayPal payment method through Mollie, which charges low processing fees, while also offering Klarna through Stripe, which supports more payment methods but charges higher processing fees. While doing so, the two different payment forms, "Checkout" and "Manage", are also merged together in a new, configurable case-by-case, payment form that is entirely redesigned to offer a better user experience. After payment, the information on the selected payment method is saved on the transaction and eventual payment record and updated with the information received from the provider. task-2882677 Co-authored-by: Anita (anko) <anko@odoo.com> Co-authored-by: Brieuc-brd <brd@odoo.com> Co-authored-by: Valeriya (vchu) <vchu@odoo.com>
Contributor
Author
|
@robodoo r+ |
Contributor
|
@AntoineVDV linked pull request(s) odoo/upgrade#5103 not ready. Linked PRs are not staged until all of them are ready. |
Contributor
Author
|
@robodoo p=1 (blocking other priority tasks) |
This was referenced Sep 29, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

[CLN] payment(_*): correct code styling inconsistencies
This commit mainly removes the extra indent level left over after commit 8ec2e8c. It also cleans up purely cosmetic code styling inconsistencies.
[FIX] payment(_*): make a proper usage of async and promises
Several functions were:
awaitwhile there are synchronous;Promisewhen it was unnecessary.This commit also cleans up a few mistakes in comments and docstrings.
[REM] payment: remove unused payment method icons and SCSS rules
[IMP] payment, *: replace providers with payment methods in payment forms
Before this commit, the payment providers (e.g., Stripe, Adyen...) available for payment were displayed on the payment forms. The customer had to select one to process their payment. After that, the customer had to select their preferred payment method (e.g., Credit Card, Bancontact...) from a list of payment methods supported by the selected provider over which the website administrator had close to no control. This was making the payment forms confusing because the payment methods were displayed sometimes more than once, if at all, in a non-controlled order, and behind the selection of a payment provider that customers should not have to deal with.
As the payment method was selected in an iframe or directly on the provider's website, the information on the selection payment method was not available in Odoo. This posed many problems, among which were the impossibility of assessing whether a specific feature (e.g., tokenization, refunds, manual capture...) was available, not being able to easily identify payment tokens through the payment method logo, listing available payment methods on the website, sorting and fine-grained configuration of the available payment method, subpar payment method-specific display on the payment form (e.g., PayPal that requires displaying a "Pay with PayPal" button), etc.
In this commit, the payment providers are thus replaced by the payment methods on the payment forms. All contextually available (depending on the country, currency, requested feature...) payment methods are displayed one after the other on a single-level list and in the order configured by the website administrator. Each payment method is "powered by" (i.e., linked) to a single payment provider: the first one, by model order, to support it. This allows, for example, offering the PayPal payment method through Mollie, which charges low processing fees, while also offering Klarna through Stripe, which supports more payment methods but charges higher processing fees.
While doing so, the two different payment forms, "Checkout" and "Manage", are also merged together in a new, configurable case-by-case, payment form that is entirely redesigned to offer a better user experience.
After payment, the information on the selected payment method is saved on the transaction and eventual payment record and updated with the information received from the provider.
task-2882677
See also:
payment_methoddocumentation#5717