Merchant Validation Failure

Question

Created Apr ’24

Replies 1

Boosts 0

Participants 1

I currently have two merchant id's configured in our production environment which are tied to separate certificates. The one below was recently created for our OlO integration which uses Spreedly. The other integration is with Worldpay directly. When attempting to validate the new merchant id for OlO, we get the following response.

Request Body {
	"merchantIdentifier":"merchant.com.cbolo.prod",
	"displayName":"Cracker Barrel",
	"initiative":"web",
	"initiativeContext":"stage.crackerbarrel.com"
}

Response Body {
  "statusMessage": "Payment Services Exception merchantId=745C2D1BC1B86B0E3FF898001666D44AADE6EC457F128075A723DA511D0BA0B4 unauthorized to process transactions on behalf of merchantId=D276804A1BF06DADBAE2DC291266FB87C15C8E6702959025D56CF4694FAB56C4 reason=D276804A1BF06DADBAE2DC291266FB87C15C8E6702959025D56CF4694FAB56C4 never authorized mass enablement transactions to occur via 745C2D1BC1B86B0E3FF898001666D44AADE6EC457F128075A723DA511D0BA0B4",
  "statusCode": "400"
}

We have followed all the steps documented around verifying our domains and still we get this error. Has anyone had this issue and been able to resolve? We opened an Apple Support case 4 business days ago and have heard nothing back. Case: 102259384074.

Boost

Answer 1

Rodger-Reed OP

Apr ’24

Resolved Issue: I ended up discovering the cause of my problem after waiting for Apple Support which was of no help. The issue turned out to be caused by having multiple merchant id certs loaded in my key chain then downloading the .p12 that was needed for the merchant id I was requesting the validation for. To correct the issue, I had to do one merchant id at a time by removing all other merchant id certs from the key chain but the one I needed the .p12 for. After taking those steps, my problem went away and the validation is working as expected. I hope this helps those who may be experiencing the same issue.

0