Visa Developer Community
turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Ask the Community
neutronron
Helper
April
1 Kudo
Thanks Dave! Removing the line: req.setHeader('Accept','application/json'); ...did the trick. Funny thing, the previous version of the API accepted that header.
... View more
April
3 Kudos
I feel your pain. I've been going back and forth with the one solitary person Visa has responding to emails and forum posts for 4 weeks now. (roughly 30 emails). After reading through release notes, searching the web and testing every possible combination of options, it feels like I have more answer than they do - which isn't saying much. One of the other contributors on the site (daveg) suggested removing unnecessary request headers, so I commented out the 'Accept' header: //req.setHeader('Accept','application/json'); ... and the "Resource not found" problem went away. I hope that helps you too.
... View more
April
1 Kudo
Hi - Thanks for the suggestion ... I should have posted an update. I did modify the payload and was able to get the SoapUI test to work. No carriage returns or line feeds in the payload ... also, escaping the double quotes was a problem, so I bounded the string in single quotes and left the double quotes as is. So the SoapUI test call to v2/payments is working, but still getting "Resource not found" when making the same call from our development environment. It's been difficult getting support on this, but I'm hopeful that we'll hear something back soon. I see that others are getting this error too, so I'll follow up with any solutions we get, here on the forum. Cheers, Ron
... View more
March
Here are some screen caps that might help to clarify the problem - I'm hoping the solution will just jump out at someone. 1. helloworld works .... 2. The script is modified to use the URI "v2/payments" and assign the request JSON to the payload to calculate the x-pay-token correctly: 3. Then the request is updated to call ..../cybersource/v2/payments and the JSON request string is assigned to the body of the request: Resulting in a token validation error.
... View more
March
That's what I thought. I've read the documentation of course, several times. And I had no problem with the helloworld example. Can you offer any other advice? I was hoping someone might be willing to share an exported (working) project for SoapUI that I could try (with our own API key and shared secret) so we can rule out other issues. In SoapUI, I'm getting this invalid token error when trying to access v2/payments (but not the helloworld resource). In our product code, we're getting "Resource not Found" when we try to access v2/payments Plus, we've had the x-pay-token building code working for months. It seems like there's something more than a bad API key going on here. Thanks, Ron
... View more
March
1 Kudo
Does anyone have a working SoapUI project sample that calls the v2/payments endpoint (process payment)? I pulled one from here on the forums (attached) .... and after replacing the API Key and Shared Secret, still couldn't get past the 401, "Token validation failed" error.
... View more
March
I'm getting the same problem. "Resource not found" (Status Code 404). [Update] I don't have a resolution yet, but found I was getting the invalid json error you mentioned above before I removed the carriage returns and line feeds in the json string. I fixed that and it went back to "Resource not found". If I figure that one out I'll definitely share the solution here.
... View more
March
1 Kudo
What's the distinction between the CyberSource Payments REST API promoted and documented on the cybersource.com site, and the CyberSource Payments REST API documented here? I understand that Visa bought CyberSource back in 2010, so I'm a little suprised to see what appear to be two separate companies pushing the same technology. At first I thought the old CyberSource.com developer site was being left up to support the older APIs, and the Cybersource Payments API described here on developer.visa.com was the next generation. But now, I see the what appears to be the same API (perhaps?) but with a different endpoint (e.g. https://api.cybersource.com/pts /v2/payments/) on the other site. If they are the same API, why are there two sets of documentation and two different servers? If they are not, why do they have the same name? And how will implementing to one API and not the other affect our customers who already have CyberSource accounts?
... View more
July 2017
Hi Sanobar - Thanks for your response. It turns out I was calculating the HMAC value wrong. Cheers, Ron
... View more
July 2017
1 Kudo
I'm getting the "Token validation failed" error when I submit a request to the Visa Payments (CyberSource) API and can't tell what's off in my code: Boolean testMode = true;
String endPoint = testMode?'https://sandbox.api.visa.com/cybersource/payments/v1/sales?apikey='+apiKey:'https://api.visa.com/cybersource/payments/v1/sales?apikey='+apiKey;
Http objhttp = new Http();
HttpRequest req = new HttpRequest();
HttpResponse res = new HttpResponse();
req.setMethod('GET');
req.setEndpoint(endpoint);
String queryString = 'apikey='+apiKey;
String URI = 'payments/v1/sales';
DateTime dateTimeNow = dateTime.now();
String unixTime = ''+dateTimeNow.getTime()/1000;
String timeStampUTC = unixTime;
String payload = '{\"encryptionType\":\"WebCryptoAPI\"}';
System.debug('=====> timestamp, uri, query string, payload = '+timeStampUTC+URI+queryString+payload);
Blob hmacData = Crypto.generateMac('HmacSHA256', Blob.valueOf(timeStampUTC+URI+queryString+payload), Blob.valueOf(sharedSecret));
String encodedDigest = EncodingUtil.base64Encode(hmacData);
xPayToken = 'xv2:'+ timeStampUTC + ':'+ encodedDigest;
System.debug('=====> xPayToken = '+xPayToken);
req.setHeader('x-pay-token', xPayToken);
req.setHeader('Content-Type','application/json');
req.setTimeout(120000);
System.debug('=====> request body: '+reqBody);
req.setBody(reqBody);
try {
res = objhttp.send(req);
System.debug('=====> http response: '+res.getBody());
}
catch(System.CalloutException e) {
System.debug('Callout error: '+ e);
} I've checked the timestamp value to make sure it's the current time (UTC), the apiKey and shared secret match those in the sandbox, and the Hmac digest seems to be in order (at least code samples on the Salesforce developer forums for this type of header value). The debug output includes: =====> timestamp, uri, query string, payload = 1500065746payments/v1/salesapikey=...hidden...{"encryptionType":"WebCryptoAPI"} =====> xPayToken = xv2:1500065746:69fTj20b36apeCz3KAOWKOr889w/m+tCgazRDiTeM3M= =====> http response: {"responseStatus":{"code":"9159","severity":"ERROR","message":"Token validation failed","info":"","status":401}} Could someone kindly point out what I'm doing wrong?
... View more
Public Statistics
| Date Registered | July 2017 |
| Date Last Visited | |
| Total Messages Posted | 11 |
| Total Kudos Received | 8 |
Latest Tags
No tags yet