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

changed redirect behaviour from Buckaroo #81

Closed
meeshoogendoorn opened this issue Oct 20, 2022 · 4 comments
Closed

changed redirect behaviour from Buckaroo #81

meeshoogendoorn opened this issue Oct 20, 2022 · 4 comments

Comments

@meeshoogendoorn
Copy link
Contributor

When i call the /store-api/handle-payment with ideal issuer i will be redirected to the following url at Buckaroo https://testcheckout.buckaroo.nl/html/testresult.aspx.

This is all okay and as it should but i sent a few params with the /handle-payment call see following parameters:

 const handledPaymentResponse = await handlePayment(
          order.id,
          routing.getUrl(`/order-success?orderId=${order.id}`),
          routing.getUrl(
            `/order-failed?orderId=${order.id}`
          ),
          apiInstance
        );

The redirect is an relative url and buckaroo will redirect to the following page resulting in a 404: https://testcheckout.buckaroo.nl/order-success?orderId=SOME_ORDER_ID

In the past Buckaroo would redirect me back to the storefront domain.com/order-success?orderId=SOME_ORDER_ID

Is this a problem on buckaroo's end or in Shopware 6?

I am using Buckaroo Plugin 1.4.0 and SW6 6.4.15.2

@meeshoogendoorn meeshoogendoorn changed the title Did u guys changed redirect behaviour from Buckaroo changed redirect behaviour from Buckaroo Oct 20, 2022
@meeshoogendoorn
Copy link
Contributor Author

This also means that if i set the parameter for finishUrl to https://google.com/ it will redirect me to google with a successful payment.

@Buckaroo-Rens
Copy link
Collaborator

Sorry @meeshoogendoorn forgot to respond to this. We are looking into this a.s.a.p.

@meeshoogendoorn
Copy link
Contributor Author

meeshoogendoorn commented Nov 21, 2022

@Buckaroo-Rens it seem to be fixed with pr #91, Thanks 💪

@Buckaroo-Rens
Copy link
Collaborator

@meeshoogendoorn That's right, I just wanted to confirm if this fix works for you too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants