| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
In order to be sure website is loaded and to allow searches in DOM require
on website was necessary. This is a partial revert of e66ba3ce1ed7c7c79dc2965237d1e37c6e02940b
that was a bit hasty.
|
|
|
|
on registration
When registering a payment token, validating it using a payment of a small amount followed by a refund
allows ensuring that the 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.
payment_ogone: add support for tokens validation
|
|
Also include 2939800ed438505be9c919d4edca0ce624e6bf8e which seems to
have been forgotten during previous forward-ports
|
|
|
|
Remove logging unecessary information. While this info is not persistent or
transmited, there is no reason to log it in developper console.
|
|
- generate payment from the frontend using a simple form
- send a payment with a simple url
- define a default provider for payments
|
|
With this module, you can register payment methods with a nice formatting
|
|
bzr revid: tde@openerp.com-20131115133209-u1z48pmw991zwdc4
|
|
module JS file + udpated CSS / SASS
bzr revid: tde@openerp.com-20131112132133-f9nqb7jgy1ovmc5b
|
|
jquery.payment library use
bzr revid: tde@openerp.com-20131108155054-t4wsnvfu5eb0o3hf
|
