MATCH - Discussions
Help assess risk prior to signing a merchant
Topics 82 Replies 209
Topic Author Replies Last Reply
Ok fixed timestamp error on my side everything is OK
christian 26 Apr 1 christian 11 hours ago
Match v. 3  is including a character code 18 (0x12) within an XML response. We're using a closed system that parses the XML response immediately, before providing it to us, so I haven't been able to acquire ...
Ken Hartness 16 hours ago 0 -
Correction: character code 18 (0x12) is not appearing at a fixed location, even though the search each time is the same
Braintree Developers 22 Dec 4 Ken Hartness 28 Apr
Ok i found the error  on my side so now everything work fine&nbsp
christian 17 Apr 2 christian 23 Apr
We saw the same thing in production around 4/1 (wondered if one of your developers had an odd sense of humor). Resubmitting the exact same request worked fine, suggesting an issue on MC's end
Maria Gurina 13 Oct 2 Ken Hartness 12 Apr
Realised I was being an idiot and was using a Terminated Merchant with a different Terminated Principal from the sandbox data set. Corrected this by using Terminated Merchant 4 from the sandbox data set. No change in the result: still zero results returned ...
marcus_holmes 03 Apr 1 marcus_holmes 05 Apr
We are receiving the below messaging for some of our MATCH API inquiries, and would like to get some clarity on the message means {}does this mean there is no matching data against MATCH's db? (i.e. no there is no record of any of the information we're submitting or something ...
Christel Chan 15 Mar 0 -
Hi Chris, You are still failing Oauth, on our Oauth validation page, there are all the parameters (private keys, parameters, etc) that you can test out.  You can use this to make sure you're set up correctly ...
Chris K 22 Feb 6 Peter Caulfield 11 Mar
An update on this. I tried doubleencoding the body hash and consumer key. Now the actual request is identical to the expected request, except for the nonce and timestamp. Can someone shed some light on this? Here's what I'm sending: POST& https%3A ...
Chris K 03 Mar 1 Chris K 08 Mar
Hi, We noticed some connectivity issues last night circa 21:45 GMT MATCH calls via the API were failing with error: "Server returned error code: 403 Forbidden" Service appears to have been restored ...
Siobhan Kavanagh 18 May 3 Siobhan Kavanagh 19 Feb
Hi Can MATCH accept and handle special characters of any kind? Kind regards Siobhan
Siobhan Kavanagh 18 Feb 1 Siobhan Kavanagh 19 Feb
Hi Kyle, <?xml version="1.0" encoding="utf8"?><PurchaseRequest><MerchantIdentity><CompanyId>324855</CompanyId><CompanyPassword>
</CompanyPassword></MerchantIdentity><Reference><MessageId>12TG65H987BBQJ56742</MessageId><SettlementId>12345WXYZ6789</SettlementId></Reference><Amount><Currency>USD</Currency><Value>55555</Value ...
Venkata Araveeti 09 Jul 11 parmanandsagar 23 Feb
How did you resolve this issue
Deepak Malleshappa 12 Sep 2 hammad85ali 27 Jan
Hi Kyle, Do you have an email address we could use to reach out to you and provide more information? Thanks
Braintree Developers 11 Jan 3 Braintree Developers 26 Jan
Hello Kris, "MATCH Online" is an application within MasterCard Connect. This application within MasterCard Connect is only provisioned for Financial Institutions and registered service providers. You can sign up for MasterCard Connect via the following: ... 04 Dec 1 Kyle Williams 10 Dec
Hello, MasterPass sandbox environment is working properly. Please try again. Thank you, Rachel
Howard Klein 02 Oct 2 Rachel Gilmor 24 Nov
039440 04 Nov 0 -
Had similar problem. Have you tried changing the XML namespace? Mine was the opposite problem. I was using a namespace ending with termination and needed to use a namespace ending with inquiry. <ns2:TerminationInquiryRequest xmlns:ns2=""> Perhaps ...
b2bjordan 24 Sep 1 Ken Hartness 15 Oct
Peter, Is there any chance that you could check my requests and see what's wrong with them? I have updated the csr file, I'm now sending the correct Acquire Id (80), but it all my calls still returns "Please ...
Craig Barrcliff 08 Sep 3 Craig Barrcliff 23 Sep
Hello Renan, This error is thrown when the ICA used in your request is not the Sandbox ICA. Please ensure you are using <AcquirerId>1996</AcquirerId> in your request. I have checked within our server logs and I am seeing ...
Renan Tymoschenko 14 Sep 1 Kyle Williams 15 Sep
Hi I have a questionabout the Termination Inquiry v3 API I just put in a inquiry query and got a respose xml back. in The response xml I have the following response ...
futoshi nishimura 19 Aug 0 -
Hi Kyle, We are continuing to receive same error XML response. Please let me know if you need any information to resolve this issue. Thanks for your time. \ Deepak
Kyle Williams 14 Jul 5 Deepak Malleshappa 29 Jul
I cloned the Match API PHP SDK from github and tried the unit test in the SDK. The unit test failed but I was able to get it working with the following fixes: 1) of course change unit test path to my own keystore ...
John Skovron 24 Jun 0 -
Hello Andres, Sorry for the delay, so it looks like this merchant is not a high risk merchant. Basically with the MATCH Termination Inquiry you are checking for if the merchant you sent in has been terminated in the past by another acquirer. If they were it will return a result with the history ...
Andres Ordonez 11 Jun 4 Brett Thomson 16 Jun
Good Afternoon Ken,  Good catch, we are seeing this same behavior on our end, we are working with our internal teams to solve this issue at this time.  In the meantime if you do have the MATCH service available to you through ...
Ken Hartness 29 Apr 2 Brett Thomson 12 May

© 1994-2016. MasterCard. All rights reserved.