summaryrefslogtreecommitdiff
path: root/addons/payment_authorize/controllers/main.py
AgeCommit message (Collapse)Author
2019-05-02[FIX] payment_authorize: missing fieldsNicolas Martinelli
- Activate Invoice Online Payment - Set Authorize to pay through Odoo (S2S) - Create a new customer (do not give portal access) - Create invoice -> send to them - Open invoice in incognito mode - Try to pay invoice online with Authorize An error is raised: The transaction cannot be processed because some contact details are missing or invalid: City, Country. Please sign in to complete your profile.If you don't have any account, please ask your salesperson to update your profile. The error is quite confusing, and the user is missing the main point: he needs to sign in. There is no reason to display the fact that contact details are missing for a public user, so this part is now shown only if the user is logged in. opw-1981003 closes odoo/odoo#33116 Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>
2019-02-11[MERGE] forward port branch saas-11.3 up to 728bb2a28ecChristophe Simonis
2019-02-07[FIX] payment_authorize: add new card verificationJorge Pinna Puissant
In the e-comerce, when the user try to add a new card in this payment methods. Before this commit, to validate the card, besides of the creation of the payment token, an amount of $1.5 id charged and refunded. During the refunded an error was raised. This error arrives because: payments made via Authorize.net are settled and allowed to be refunded only on the next day. https://account.authorize.net/help/Miscellaneous/FAQ/Frequently_Asked_Questions.htm#Refund <quote>The original transaction that you wish to refund must have a status of Settled Successfully. You cannot issue refunds against unsettled, voided, declined or errored transactions.</quote> This means, we can't refund directly after the payment. Now, we only create the payment token. As Authorize.net verify the card during the creation of the token, a new verification is not needed. OPW-1927754 closes odoo/odoo#30905
2018-09-19[IMP] payment_*: payment acquirers error handlingToufik Benjaa
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
2018-01-24[FIX] payment_ogone, payment_stripe, payment_authorize: give partner_id as ↵fda-odoo
parameter to s2s_process If the page doesn't provide the partner_id, the three acquirer will now add it before process the payment.
2018-01-24[FIX] Payment, payment_authorize: show an error if customer doesn't have a ↵fda-odoo
complete profil on authorize.net payment. If the user has no Zip code, country or city, authorize refuse the payment, but Odoo doens't show any error. The commit invite the user to log in in this case or to fill his missing information
2017-08-14[IMP] Payments & subscriptions: Improved Paymentstbe-odoo
- When registering a payment token, validating it using a payment of a small amount (~1.50€) followed by a refund allows ensuring that the payment method is valid (i.e. checksumming the card number simple ensure the number is valid but not that the card exists). This commit introduces a generic approach that must be implemented for each acquirer that has tokenization support. This commit also introduces a generic payment token registration/usage template that can be adapted according to one's need. - Introducing a new payment form that handles payment, deletion and adding payment method (only for server2server for the moment). - On /my/payment_method, changed strings 'Payment Acquirers' to 'Payment Methods' which is more clear. - Stripe can now be used to pay subscriptions.
2017-05-15[FIX] P3: urllib, urllib2 and urlparseXavier Morel
In Python 3, all of these were "consolidated" under urllib(.request, .parse, .errors) which is inconvenient. Since we already have hard dependencies on requests and werkzeug(.urls, which is a backport of Python 3's unicode-aware urllib.parse) migrate *everything* to that. A sticking point is urllib2.URLError, those were (mostly) replaced by the slightly more general IOError which URLError extends.
2017-01-03[REF] ir_config_parameter: remove `group_ids` and simplifyRaphael Collet
Add `sudo()` to call `get_param` where necessary, and make the web client use a controller instead of directly accessing parameters.
2016-09-01[IMP] payment_authorize: add server2server supportDamien Bouvy
This commit add s2s communication to the Authorize.net payment provider, allowing the user to: - Create a payment token - Charge a payment token - Authorize/capture transactions
2016-07-06[CLN] payment_authorize: cleaning and guidelinesThibault Delavallée
As this module is already in new API only small linting is performed.
2015-11-24[FIX] payment_adyen, payment_authorize, payment_buckaroo, payment_paypal, ↵Goffin Simon
payment_sips: Disable csrf on callbacks Inspired from 2099f15d67564ab153d48993cca0f80aee04bb09 opw:653341
2015-01-16[ADD] New payment acquirer Authorize.net.Ajay javiya