Pagseguro Payment Acquirer

by
Odoo

42.89

v 10.0 v 11.0 v 12.0 Third Party 9
Required Apps Invoicing (account)
Lines of code 203
Technical Name payment_pagseguro
LicenseOPL-1
Websitehttps://betavision.com.br
Also available in version v 11.0 v 10.0
You bought this module and need support? Click here!
Required Apps Invoicing (account)
Lines of code 203
Technical Name payment_pagseguro
LicenseOPL-1
Websitehttps://betavision.com.br
Also available in version v 11.0 v 10.0

Pagseguro Payment Acquirer

Betavision Sistemas

This module implements Pagseguro as a payment option for paying E-commerce orders, sale orders and invoices in portal

Dependencies

Install pagseguro lib with:

pip3 install pagseguro

to redirect work after payment, web.base.url must be the same as shop url

Need Help?

Email Contact Us Odoo Customization

Odoo Proprietary License v1.0
This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.
The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.
There are no ratings yet!
by
João Paulo de Souza
on 7/16/21, 4:58 AM Author

Alexandre, atualizei o código e removi a parte referente ao  "<<<<<<< HEAD".
quanto ao erro relativo ao timezone e ao pagseguro_email_account  não consegui reproduzir numa instância limpa do odoo.

Apesar disso o módulo vai precisar ser atualizado. Eu até consigo criar a transação e ir pra página de checkout do pagseguro, e pagar via boleto e cartão de crédito.

Porém nas duas modalidades não sou redirecionado mais pro site do odoo e nem notificado da aprovação do pagamento, ambas as ações aconteciam automaticamente, sem necessidade de intervenção do usuário nem de se especificar uma url de redirecionamento dentro do pagseguro ou url de notificação. Provavelmente houveram mudanças do lado da API deles e meu módulo ficou obsoleto com as mudanças. Peço que entre em contato comigo pelo email joao@betavision.com.br para tratarmos de uma solução para o problema.


erro ao instalar versao 12
by
Alexandre Bernardes
on 7/14/21, 3:24 PM Confirmed Purchase

instalando obtenho primeiro um erro no arquivo payment.py relativo a uma anotação "<<<<<<< HEAD".

removendo isso obtenho um erro relativo a timezone, e insistindo o erro muda para:

ValueError: O campo `pagseguro_email_account` não existe


Re: erro ao instalar versao 12
by
João Paulo de Souza
on 7/14/21, 9:04 PM Author

Olá Alexandre, amanhã eu verifico este problema e te atualizo