We started seeing this error on one of our merchants yesterday and now another one popped up today. We've solved this by sending an external_reference_id in our charge payload however this is what our request looked like prior to his issue popping up on the Clover E-Commerce API:
{
"source": "XXXXXXXXXXXXX",
"tip_amount": 0
}
We've never sent an external_reference_id and wondering, is this now a required key? Or is this just another random error on the Clover API?
I would recommend reviewing the api: https://docs.clover.com/reference/createcharge
the external reference ID is not a required field but it you use it it cannot exceed 12 characters.
I believe there is something changed on Clover. This issue is happening on some merchants only.
The docs does not mention anything about this issue.
I've also seen this issue occur for some of our merchants. We have not made any changes to our integration and aren't sending an external reference id in our requests. It seems this started happening since March 5th 2024 and only for some merchants.
We've seen it on a few merchants as well. The only thing we've seen is that they were on a legacy plan that was sunset on that day. The only way we could avoid the error is by sending the external_reference_id key when making a charge. Even though we've never sent it at any point when making these API calls.
8 People are following this question.
