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

Trustly payment and QuickPay Api inconsistency #42

Open
etdevhub opened this issue Jan 3, 2025 · 0 comments
Open

Trustly payment and QuickPay Api inconsistency #42

etdevhub opened this issue Jan 3, 2025 · 0 comments

Comments

@etdevhub
Copy link

etdevhub commented Jan 3, 2025

Preconditions

Magento ver. 2.4.6-p8
QuickPay ver. 2.4.5, 2.4.6

Description

We are using Trustly as a payment method with the 'Auto capture' setting enabled and have encountered the following issue.
After the payment was made, the order moved from the 'pending' to the 'processing' state/status, but no invoice was created.
I suspect the issue lies in the callback process. Right after the payment is made, we receive a callback from Quickpay confirming the 'authorize' operation (it can be 'capture' operation as well). This triggers an attempt to create an invoice and initiates an API request to perform the capture operation. The 'capture online' option is hardcoded in Controller/Payment/Callback.php. However, the API response we receive consistently returns the following error:
{
"message": "Unsupported operation type",
"data": null,
"errors": {}
}

Result

As a result, an exception is thrown, leaving no invoice created. However, the order status changes, and the transaction data is saved. Attempts to cancel the order lead to the same error: 'Unsupported operation type.'


I have already contacted the QuickPay support team, and they said:
"Due to the payment being made as a Trustly payment, the payments with Trustly have auto-capture due to the acquirer setup Trustly has, so the payment has already been captured and can, therefore, not be captured again."

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

1 participant