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
Like #2, we need to do better error handling, and return to the client a response that makes sense. When sending a POST to /payment with bad vals, I get a 201 with an empty response. Logging the response from Spreedly is a different story though:
{ errors: [ { key: 'errors.payment_method_or_payment_method_token_required',
message: 'You must specify a valid \'payment_method\' or valid \'payment_method_token\' parameter.' } ]
}
The text was updated successfully, but these errors were encountered:
raychz
changed the title
makePayment() fails silently when given bad params
makePayment() fails silently when given bad Body params
Nov 13, 2018
Like #2, we need to do better error handling, and return to the client a response that makes sense. When sending a POST to /payment with bad vals, I get a 201 with an empty response. Logging the response from Spreedly is a different story though:
The text was updated successfully, but these errors were encountered: