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

[FEATURE] describe actual state of async payment flow #1478

Open
mkucmus opened this issue Nov 25, 2024 · 2 comments
Open

[FEATURE] describe actual state of async payment flow #1478

mkucmus opened this issue Nov 25, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request payment

Comments

@mkucmus
Copy link
Collaborator

mkucmus commented Nov 25, 2024

Description

  • describe the current state
  • report the bugs
  • find solutions

Use Case

  • there are still hidden parts in async payment process like what would happen in case of fail or unfinished happy path

Proposed Solution

No response

Alternatives Considered

No response

Additional Context

No response

@mkucmus mkucmus added the enhancement New feature or request label Nov 25, 2024
@mkucmus mkucmus self-assigned this Nov 25, 2024
@mkucmus mkucmus moved this to In Progress in Composable Frontends Nov 25, 2024
@mkucmus
Copy link
Collaborator Author

mkucmus commented Nov 28, 2024

issues found:

  • no feedback about failed transaction after redirection from finalize-payment route - there is no info what went wrong, customer is just redirected back to frontend app URL according to handlePayment URL defined, with no details
  • the async flow is not fully headless, the finalizeTransaction action takes place in storefront context
  • sometimes the payment handler does not handle additional parameters required to finish transaction, like success token for payment intent for credit cards

@BrocksiNet
Copy link
Collaborator

Push it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request payment
Projects
Status: In Progress
Development

No branches or pull requests

2 participants