We have been working with a customer that has been using the COM api for over a decade.
In the past week, we implemented the new API and had the customer add the 'vault' features on their site. Everything else in our configuration has remained the same. The only thing that has changed is that we're using the newer API which tokenizes the credit card.
Everything works great in the sandbox environment. This is leading me to believe that perpahs the customer needs to give us a new set of credentials or something. Regardless:
When we attempt to tokenize a card, we run it through:
var usResAddCc = new ResAddCC("4111111111111111", "2310", "7");
usResAddCc.SetEmail(user.Email); usResAddCc.SetCustId(user.Id.ToString());
IMonerisReceipt receipt;
receipt = _httpsPostRequest.GetReceipt(usResAddCc);
receipt.GetMessage = null: Transaction not allowed: Resolver
Were we supposed to have the customer do anything more than add the vault features to their site. I'm confused that this works fine in the test environment, but not on production.
Many thanks,
MIke
In reply to mmurphy384:
In reply to ND_Moneris: