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! Redsys specifies in their documentation that the parameter Ds_Merchant_Order 4 numeric digits on the description and then alphanumeric characters, but the data type in the same row says 12 alphanumerics. Indeed, we have been transacting for over a year with transaction ids like this one: QPYDStLbYl5P.
The method PurchaseRequest::setTransactionId() was generating me a 16 length string, by appending 4 zeros at the left. I find this very misleading because the parameter sent should be the one you are inputting. Maybe a solution could be to fill with zeros at the left, if the length is <12?
The text was updated successfully, but these errors were encountered:
I'd have to go back and look at the documentation, it's been a while since I did the implementation for this one. That sounds like a reasonable approach though, and certainly one that should be easy to cover with unit tests. It's a little confusing when the documentation is saying different things, though!
Hi! Redsys specifies in their documentation that the parameter
Ds_Merchant_Order
4 numeric digits on the description and then alphanumeric characters, but the data type in the same row says 12 alphanumerics. Indeed, we have been transacting for over a year with transaction ids like this one:QPYDStLbYl5P
.The method
PurchaseRequest::setTransactionId()
was generating me a 16 length string, by appending 4 zeros at the left. I find this very misleading because the parameter sent should be the one you are inputting. Maybe a solution could be to fill with zeros at the left, if the length is <12?The text was updated successfully, but these errors were encountered: