You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we updated the Stripe PHP library on our server the other day to 6.17.2 and our order process has started failing. After looking into it, it appears the problem may be with the Stripe PHP library.
The catch here is that source may be null. This was done to make passing a source optional. In previous Stripe PHP versions, setting an array value to null meant it would not be sent at all. It appears the behavior has recently changed to instead interpret null as an empty string, so our order process has blown up with this Stripe error response: Invalid source object: must be a dictionary or a non-empty string.
I looked in our Stripe dashboard and see there is a source in the request body as an empty string, which should not be there.
Update: The version we were on before that worked fine was 6.17.0. I think the array changes you made in 6.17.1 and 6.17.2 are the culprit here.
The text was updated successfully, but these errors were encountered:
Hi, we updated the Stripe PHP library on our server the other day to 6.17.2 and our order process has started failing. After looking into it, it appears the problem may be with the Stripe PHP library.
Our code:
The catch here is that
source
may be null. This was done to make passing a source optional. In previous Stripe PHP versions, setting an array value to null meant it would not be sent at all. It appears the behavior has recently changed to instead interpret null as an empty string, so our order process has blown up with this Stripe error response: Invalid source object: must be a dictionary or a non-empty string.I looked in our Stripe dashboard and see there is a source in the request body as an empty string, which should not be there.
Update: The version we were on before that worked fine was 6.17.0. I think the array changes you made in 6.17.1 and 6.17.2 are the culprit here.
The text was updated successfully, but these errors were encountered: