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

Fatal error on "Disable stored payment details" API call #568

Closed
anton-close opened this issue Oct 2, 2023 · 1 comment
Closed

Fatal error on "Disable stored payment details" API call #568

anton-close opened this issue Oct 2, 2023 · 1 comment

Comments

@anton-close
Copy link

Describe the bug
\Adyen\Service\Checkout\RecurringApi::deleteTokenForStoredPaymentDetails() gives fatal error "Adyen\Service::requestHttp(): Return value must be of type array, null returned".

The problem is that this method $this->requestHttp($endpoint, strtolower('DELETE'), null, $requestOptions); must return array, but in fact NULL is returned. Adyen API
curl -X DELETE 'https://checkout-test.adyen.com/v70/storedPaymentMethods/{RECURRING_DETAIL_REFERENCE}?merchantAccount={YOUR_MERCHANT_ACCOUNT}&shopperReference={YOUR_SHOPPER_REFERENCE}' --header 'X-API-Key: YOUR_API_KEY'
returns 204 with empty response, but Adyen Service always expects array.

To Reproduce
Steps to reproduce the behavior:

  1. Adyen PHP SDK version is 15.3.0.
  2. Just call \Adyen\Service\Checkout\RecurringApi::deleteTokenForStoredPaymentDetails() method with required arguments

Expected behavior
No fatal error should happen.

@jillingk
Copy link
Contributor

jillingk commented Oct 4, 2023

Hey @anton-close,

Thanks a lot for reaching out to us with this issue! We flagged this issue already actually have since fixed it in the latest release of v15.4.0! Let us know if you experience any other issues during your integration.

Best, Jilling
Adyen

@Aleffio Aleffio closed this as completed Oct 9, 2023
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

3 participants