Project

General

Profile

Actions
Copy link

Bug #9239

closed

Quickpay: payment response "brand" is now an array

Bug #9239: Quickpay: payment response "brand" is now an array

Added by krileon over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
High
Assignee:
krileon
Target version:
4.7.0
Start date:
28 August 2023
Due date:
% Done:

100%

Estimated time:

Description

This used to be a string. Being changed to an array is now causing payment type detection to throw an error.

https://www.joomlapolis.com/forum/professional-members-support/246093-php-8-1-8-2#334917

Updated by krileon over 2 years ago Actions
Copy link
 #1

Updated by krileon over 2 years ago Actions
Copy link
 #2

So it might not be the notification, but the response object from /subscriptions or /payments call in the notification handling.

Updated by krileon over 2 years ago Actions
Copy link
 #3

Both /subscriptions and /payments API calls indicate the brand metadata should be a string as well.

https://learn.quickpay.net/tech-talk/api/services/#payments

https://learn.quickpay.net/tech-talk/api/services/#subscriptions

Updated by krileon over 2 years ago Actions
Copy link
 #4

Looks like it's the form return handler. So when redirected back to the site. We're still using QuickPay Form API so maybe an unintended change?

https://learn.quickpay.net/tech-talk/payments/form/#quickpay-form

Updated by krileon over 2 years ago Actions
Copy link
 #5

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

Fixed in MR !323

Updated by beat about 2 years ago Actions
Copy link
 #6

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: PDF Atom