Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[14.0][RFC] payment_pagseguro: refactor charge to orders endpoint #2309

Draft
wants to merge 1 commit into
base: 14.0
Choose a base branch
from

Conversation

marcelsavegnago
Copy link
Member

@marcelsavegnago marcelsavegnago commented Jan 21, 2023

@mileo nesta PR eu fiz alguns ajustes para conseguir fazer a comunicação com o pagseguro. Porém, se tiver interesse fique a vontade para trabalhar na refatoração/implementação necessária para adpatar as novas necessidades do pagseguro.

Testei o envio e a captura.. ainda falta testar o cancelamento.

obs. alguns dados estão chumbados no código

@marcelsavegnago marcelsavegnago force-pushed the 14.0-rfc-payment_pagseguro-orders branch from f9324b3 to 612d4d7 Compare January 21, 2023 13:08
@rvalyi
Copy link
Member

rvalyi commented Jan 21, 2023

vale a pena vc tb checkar os últimos commits na V12, porque até onde eu lembro nem tudo tinha sido portado para a V14 neste módulo...

@marcelsavegnago
Copy link
Member Author

vale a pena vc tb checkar os últimos commits na V12, porque até onde eu lembro nem tudo tinha sido portado para a V14 neste módulo...

Fato

"card": {
"encrypted": self.payment_token_id.pagseguro_card_token,
},
"items": [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

eu colocaria algo assim para listar as sale_order_line:
items = []
for line in self.sale_order_ids[0].order_line:
item = {
"reference_id": line.product_id.default_code,
"name": line.product_id.name,
"quantity": line.product_uom_qty,
"unit_amount": int(line.price_unit * 100),
}
items.append(item)

Copy link
Member Author

@marcelsavegnago marcelsavegnago Jan 23, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@augustodinizl se possível, pega a branch desta PR e submete uma PR para o fork da https://github.com/escodoo/l10n-brazil fazendo favor.

@marcelsavegnago
Copy link
Member Author

Na situação atual, é um pedido enviado para o pagseguro é o modelo de pre-autorização sem captura de cobrança de automática. Para usar o modelo de pré-autorização + captura, deve ser definido o parametro 'capture'

@marcelsavegnago marcelsavegnago force-pushed the 14.0-rfc-payment_pagseguro-orders branch from 612d4d7 to f4f7579 Compare January 26, 2023 16:05
@mileo
Copy link
Member

mileo commented Sep 30, 2023

@sadamo @cristiano-one

Copy link

github-actions bot commented Feb 4, 2024

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 4, 2024
@mileo
Copy link
Member

mileo commented Feb 5, 2024

Bom dia @marcelsavegnago,

Tem previsão de dar continuidade nesse PR? Chegou a verificar os testes?

@marcelsavegnago
Copy link
Member Author

Grande @mileo estou usando esta PR em um cliente mas não consegui dar andamento nela. Se tiver alguem que pode dar uma força.. eu agradeço.

@sadamo
Copy link
Contributor

sadamo commented Feb 8, 2024

@marcelsavegnago

Foi iniciado o desenvolvimento dessa feature aqui: https://github.com/kmee/l10n-brazil/tree/14.0-pagseguro-pix-boleto

Pode ser que te ajude a seguir com esse desenvolvimento.

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 11, 2024
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 16, 2024
@mileo mileo removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 16, 2024
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants