Visa Developer Community

SLi

Hi @ bt, I see that you are calling an endpoint in the certification environment. Can you please confirm that your project is currently in the certification stage? If yes, please send an email to developer@visa.com and include the following: 1. Project name 2. The region that you are located so we can involve a regional Visa representative to provide you with further assistance

SLi

Hi @ hakim, Thank you for providing the screenshot and API request and response details. This is very helpful. I checked the API reference page on Visa Developer Center and found that the information is outdated. Please use the below test data and let us know if you can successfully call the VCES Validate API. Please ensure that requestTimesStamp is within 5 minutes of current time. End Point https://sandbox.api.visa.com/visacardeligibilityservices/v1/cardeligibility/validate Method POST Request { "permanentAccountNumber": "4000000000000013", "vendorUniqueId": "4658_TstVDPPgm3", "numberOfAdditionalRedemptions": 2, "requestTimeStamp": "10/7/2019 6:07:56 PM", "correlationId": "dfsdfasdsdf", "extendedData": "asddd", "expirationDate": { "Month": "01", "Year": "2020" } } Response { "statusDescription": "Success", "cardId": "311", "responseTimeStamp": "10/7/2019 6:08:09 PM", "isEligible": "True", "CorrelationId": "dfsdfasdsdf", "eligibilityLevel": "2", "statusCode": "000" } Response Header Status Code: 200 OK Server : nginx Content-Type : application/json;charset=utf-8 Content-Length : 181 X-SERVED-BY : l55c012 X-CORRELATION-ID : 1570471688_948_91200070_l55c012_VDP_WS X-Backside-Transport : OK OK,OK OK Cache-Control : no-cache, no-store ,no-cache, no-store, must-revalidate Pragma : no-cache Expires : -1 X-OPNET-Transaction-Trace : a2_465bc920-d9ee-404d-b225-4f66e3061abc-10724-105 X-AspNet-Version : 4.0.30319 X-Powered-By : ASP.NET X-Content-Type-Options : nosniff X-Frame-Options : SAMEORIGIN X-XSS-Protection : 1; mode=block Content-Security-Policy : default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; X-Global-Transaction-ID : 448482cb5d9b7f09a970b1ef X-APP-STATUS : 200 Strict-Transport-Security : max-age=2592000;includeSubdomains Date : Mon, 07 Oct 2019 18:08:09 GMT Connection : keep-alive

SLi

Hi @ Athirah, I think the requestTimeStamp you entered in your request is invalid because the response you received shows error "Vendor RequestTimeStamp format error". Can you try again and when you r eceive the response, copy the responseTimeStamp and enter it in your requestTimeStamp?

SLi

Hi @ mcalleja, Thanks for confirming. Since your project is in certification, please send an email to developer@visa.com with the following information: 1. Project Name 2. The region that you are located so we can involve a regional Visa representative to provide you with further assistance

SLi

Hi @ mcalleja, I see that you are calling an endpoint in the certification environment. Can you please confirm that your project is currently in the certification stage?

SLi

Hi @ Nkanyezi, The error "Expected input credential was not present" usually occurs when the credentials used are invalid. Can you please confirm if you are using valid credentials? Visa Direct uses Two Way SSL for authentication. Please test the connectivity and credentials by following the Two-Way SSL (Mutual Authentication) guide: https://developer.visa.com/vdpguide#twoway_ssl_mutual_authentication If you continue to get this error, please provide us screenshots of your SoapUI or VDC Playground setup so we can further investigate the issue. Please also refer to this community forum post link for additional troubleshooting steps that we have provided: https://community.developer.visa.com/t5/General/Always-getting-quot-Expected-input-credential-was-not-present/m-p/11755/highlight/false#M2156

SLi

Hi @ Nkanyezi, I'd like to let you know about VDC Playground. Visa Developer Center Playground (VDC Playground) is a tool designed exclusively for testing and troubleshooting Visa APIs that are exposed through the Visa Developer Platform (VDP). It comes integrated with all required authentication methods to connect and get going with VDP APIs. Please feel free to use this tool and use the "Export" feature to capture additional information to share with us for further troubleshooting. To access and download this tool, log in to Visa Developer > Project dashboard > Asset Management. Please access the User Guide below for details: https://developer.visa.com/pages/visa-developer-center-playground

SLi

Hi @ yibs, Please check your Postman Settings and make sure on the Proxy tab "Use System Proxy" is set to On.

SLi

Hi @ yibs, I just tried the Visa Direct API (https://sandbox.api.visa.com/visadirect/mvisa/v1/cashinpushpayments) and got a response successfully. Please see request/response details below. Please also reference this page for Postman setup: https://community.developer.visa.com/t5/Use-Cases/APIs-for-payment-gateway-9124-error/m-p/10461#M114 End Point https://sandbox.api.visa.com/visadirect/mvisa/v1/cashinpushpayments Method POST Request { "amount": "124.05", "localTransactionDateTime": "2019-08-28T20:35:51", "recipientPrimaryAccountNumber": "4123640062698797", "cardAcceptor": { "address": { "country": "IN", "city": "Bangalore" }, "idCode": "ID-Code123", "name": "Test Merchant" }, "senderReference": "1234", "acquirerCountryCode": "643", "acquiringBin": "400171", "retrievalReferenceNumber": "430000367618", "systemsTraceAuditNumber": "313042", "senderName": "Mohammed Qasim", "businessApplicationId": "CI", "merchantCategoryCode": "6012", "transactionCurrencyCode": "840", "senderAccountNumber": "4541237895236" } Response { "transmissionDateTime": "2019-08-28T20:38:20.000Z", "approvalCode": "21324K", "transactionIdentifier": 142364194068951, "actionCode": "00", "retrievalReferenceNumber": "430000367618", "responseCode": "5" } Response Header Status Code: 200 OK Server : nginx Content-Type : application/json Content-Length : 194 X-SERVED-BY : l55c015 X-CORRELATION-ID : 1567024700_640_1750390527_l55c015_VDP_WS X-Backside-Transport : OK OK,OK OK X-APP-STATUS : 200 X-Global-Transaction-ID : de8c0d945d66e63c121ec5e5 X-Frame-Options : SAMEORIGIN X-XSS-Protection : 1; mode=block X-Content-Type-Options : nosniff Strict-Transport-Security : max-age=2592000;includeSubdomains Cache-Control : no-cache, no-store, must-revalidate Pragma : no-cache Expires : -1 Date : Wed, 28 Aug 2019 20:38:20 GMT Connection : keep-alive

SLi

Hi @ yibs, To further investigate, please provide the following information: 1. End Point URL 2. Request Header 3. Request Body 4. Response Header 5. Response Body If you can attach screenshots of the Postman screen showing the error, that would be very helpful.

SLi

Hi @ giswas, Please try below test data and let me know if you can get a response successfully. We are in the process of updating the documentation on VDP. { "issuer" : { "metadata" : { "adhoc":"true" }, "bank" : [ { "regionId" : "1", "processorId" : "1", "bankId" : "1940" }, { "regionId" : "1", "processorId" : "2", "bankId" : "5126" }] }, "companyFields": "all", "departmentFields": "all", "cardHolderFields": "all", "cardAccountFields": "all" }

SLi

Hi @ malviyaash18, Ok, if MLE for the Funds Transfer API is turned on, then you'll need to encrypt the payload with your MLE credentials, otherwise you will get the token validation error.

SLi

Hi @ malviyaash18, Thanks for sharing the screenshots, it's very helpful. The SoapUI setup looks correct. The Funds Transfer API has an option to turn on MLE. Can you please confirm whether you have MLE turn on or off for this API? Also, when you first created your project, did you upload your own CSR or did you have it auto-generated. Thanks.

SLi

Hi @ malviyaash18, The error "Expected input credential was not present" usually occurs when the credentials used are invalid. Can you please confirm if you are using valid credentials? Visa Direct uses Two Way SSL for authentication. Please test the connectivity and credentials by following the Two-Way SSL (Mutual Authentication) guide: https://developer.visa.com/vdpguide#twoway_ssl_mutual_authentication If you continue to get this issue, please provide us screenshots of your SoapUI setup so we can further investigate the issue. Please also refer to this community forum post link for additional troubleshooting steps that we have provided: https://community.developer.visa.com/t5/General/Always-getting-quot-Expected-input-credential-was-not-present/m-p/11755/highlight/false#M2156

SLi

Hi @ ramavs2, Thank you for your inquiry. The sandbox environment does not have data for all ATM locations. Please use the test data provided in your VDP project's Test Data tab. Here's a sample request with valid response: End Point https://sandbox.api.visa.com/globalatmlocator/v1/localatms/atmsinquiry Method POST Request { "wsRequestHeaderV2": { "requestTs": "2019-05-02T16:51:18.000Z", "requestMessageId": "ICE01-001", "userBid": "10000108", "correlationId": "909420141104053819418", "applicationId": "VATMLOC", "userId": "CDISIUserID" }, "requestData": { "distanceUnit": "mi", "distance": "20", "culture": "en-US", "options": { "findFilters": [ { "filterValue": "C", "filterName": "OPER_HRS" }, { "filterValue": "", "filterName": "AIRPORT_CD" }, { "filterValue": "N", "filterName": "WHEELCHAIR" }, { "filterValue": "N", "filterName": "BRAILLE_AUDIO" }, { "filterValue": "N", "filterName": "BALANCE_INQUIRY" }, { "filterValue": "N", "filterName": "CHIP_CAPABLE" }, { "filterValue": "N", "filterName": "PIN_CHANGE" }, { "filterValue": "N", "filterName": "RESTRICTED" }, { "filterValue": "N", "filterName": "PLUS_ALLIANCE_NO_SURCHARGE_FEE" }, { "filterValue": "N", "filterName": "ACCEPTS_PLUS_SHARED_DEPOSIT" }, { "filterValue": "N", "filterName": "V_PAY_CAPABLE" }, { "filterValue": "N", "filterName": "READY_LINK" } ], "range": { "start": 10, "count": 20 }, "operationName": "or", "sort": { "primary": "city", "direction": "asc" }, "useFirstAmbiguous": true }, "location": { "address": null, "geocodes": { "latitude": 40.45205189371198, "longitude": -80.00868417440162 }, "placeName": null }, "metaDataOptions": 0 } }

SLi

Hi @ naveench, Apologies, but I do not have any recommendation or steps to test the VAU API using Netsuite as I am not familiar with this tool. From your previous post on July 26, you were getting 200 response via SoapUI, correct?

SLi

Hi @ naveench, Unfortunately I am not familiar with Netsuite to provide input on the error you are getting.

SLi

Hi @ naveench, Are you getting the "500 Internal Server Error" when using Soap UI to test the VAU API? This API uses 2-Way SSL method, so please don't add the API key in the request. Please follow the instructions in the link provided below to test your credentials and connectivity using the sample HelloWorld app. https://developer.visa.com/pages/working-with-visa-apis/two-way-ssl#twoway_ssl_tutorial_video

SLi

Hi @ giswas, Great! Thank you for the update!

SLi

Hi @ giswas, Thank you for you inquiry. I tested the VAU API on my end and it is working fine. Please see below for the detailed request and response. Please note that I have masked the PAN, please use the test PANs from your "Test Data" tab of your VDP project. End Point https://sandbox.api.visa.com/vau/v1/vauissuer Method POST Request { "requestHeader": { "requestMessageId": "83VAU4951620190724160009083", "messageDateTime": "2019-07-24T16:00:10.491" }, "requestData": { "pANs": [{ "pAN": "xxxxxxxxxxxxxxxx", "expDate": "2004" }], "bIN": "", "timePeriod": "", "from": "2016-08-01", "to": "2017-08-02", "group": "STANDARD", "dateUpdated": "" } } Response { "responseHeader": { "numRecordsReturned": "1", "responseMessageId": "83VAU4097320190724160204425", "requestMessageId": "83VAU4951620190724160009083", "messageDateTime": "2019-07-24 16:02:07.570" }, "responseData": { "bin": "", "panList": [{"panData": { "inquiries": [{ "tpaInd": "N", "merchantResponseCode": "V", "merchantInquiryDate": "2017-07-01", "subMerchantName": "", "merchantName": "NETFLIX INC" }], "panResponseMsg": "Success", "pAN": "xxxxxxxxxxxxxxxx", "expDate": "2004" }}], "from": "2016-08-01", "to": "2017-08-02", "dateUpdated": "", "timeperiod": "", "group": "STANDARD" }, "status": { "statusDescription": "VAU Service - Success", "statusCode": "CDI000" } } Response Header Status Code: 200 OK Server : nginx Content-Type : application/json;charset=UTF-8 Content-Length : 617 X-SERVED-BY : l73c013 X-CORRELATION-ID : 1563984124_026_1419172749_l73c013_VDP_WS X-Backside-Transport : OK OK,OK OK Pragma : no-cache Cache-Control : no-cache, no-store, max-age=0 ,no-cache, no-store, must-revalidate Expires : Thu, 01 Jan 1970 00:00:00 GMT ,-1 Content-Language : en-US X-Global-Transaction-ID : 4083965157 X-APP-STATUS : 200 X-Frame-Options : SAMEORIGIN X-XSS-Protection : 1; mode=block X-Content-Type-Options : nosniff Strict-Transport-Security : max-age=2592000;includeSubdomains Date : Wed, 24 Jul 2019 16:02:07 GMT Connection : keep-alive If you continue to get the error, can you please provide us the x-correlation ID of the error? Also are you using SOAP UI to test the endpoint? Please let me know if you have any other questions.

SLi

Hi @ mmcewen_pay360, In order to resolve your issue quickly, please reach out to the Visa Checkout Support Team directly at developer-support@mail.digital.visa.com. Additionally, these browsers are recommended for use with Visa Checkout: * Internet Explorer, version 11 or later. Note: Do not use the compatibility setting; specifically, do not use it to specify a version less than IE 11 (e.g. do not specify x-ua-compatible=IExx where xx is less than 11 in your pages). * Firefox, current version through 10 versions prior * Chrome, current version through 10 versions prior (except beta versions) * Safari, version S6 or later * iOS, version 6 or later * Android, version 4 or later Other browsers may be acceptable; however, the HTML pages that contain a Visa Checkout button must support TLS 1.2 and be compatible with HTML 4.01 or higher (including XHTML 1.0 and above). Typically, you specify the HTML version in the DOCTYPE declaration for version 4.x as follows: . HTML 5 does not require explicit version numbers.

SLi

Hi @mmcewen_pay360, Can you please let us know the browser type and version you are using? How often do you need to clear the browser cache? We'll take a look and get back to you soon.

SLi

Hi @swaritsharma, Thank you for your patience. We currently do not have a solution that you can use the Merchant ID obtained from the Merchant Search API and use it in the Merchant Push Payments API in mVisa. Please visit this link for details on how the Merchant Push Payments API is invoked: https://developer.visa.com/capabilities/visa_direct/reference#visa_direct__mvisa__v1__merchant_push_payments_post Please let me know if you have any questions.

SLi

Hi @ swaritsharma, Thank you for your inquiry. We will get back to you with an update soon.

SLi

Hi @ JbJopito, Thank you for your update. I'm glad to hear that you have found a workaround by creating a new project and generating new credentials. I'm happy to investigate further why your old credentials don't work on the Merchandise Refund API (https://sandbox.api.visa.com/visadirect/mvisa/v1/mr). Can you please send an email to developer@visa.com and provide the following information. 1. attach certificate public key PEM file 2. attach certificate private key PEM file 3. userid 4. password

SLi

Hi @ JbJopito, Since I don't have access to your testing environment, can you please use SoapUI to test instead? Here is the link to setup SoapUI: https://developer.visa.com/pages/working-with-visa-apis/two-way-ssl#testing_twoway_ssl_connectivity_using_soapui

SLi

Hi @ JbJopito, I have a few additional questions. 1. You mentioned that in sandbox console, the API returned success, but in your environment, it returned error. What is the environment the you are referring to? 2. Are you using the SOAPUI tool to test the API? 3. Is Merchandise Refund (https://sandbox.api.visa.com/visadirect/mvisa/v1/mr) the only API with errors?

SLi

Hi @ JbJopito, I tested the mVisa Merchandise Return API and was able to get a response successfully. Please see below for detailed request and response. End Point https://sandbox.api.visa.com/visadirect/mvisa/v1/mr Method POST Request { "systemsTraceAuditNumber": "313223", "amount": "1200", "localTransactionDateTime": "2019-07-10T21:36:38", "recipientPrimaryAccountNumber": "4761360055652118", "merchantCategoryCode": "6012", "transactionCurrencyCode": "INR", "cardAcceptor": { "address": { "country": "IND", "city": "BGLR" }, "idCode": "VMT200911086070", "name": "Mr. ABC" }, "acquirerCountryCode": "643", "retrievalReferenceNumber": "430000367722", "acquiringBin": "400171" } Response { "transmissionDateTime": "2019-07-10T21:41:38.393", "approvalCode": "21324K", "transactionIdentifier": 148231096112576, "cardAcceptor": { "idCode": "IDCode", "name": " Mr ABC", "terminalId": "TERMID01" }, "actionCode": "00", "retrievalReferenceNumber": "430000367722", "responseCode": "5" } Response Header Status Code: 200 OK Server : nginx Content-Type : application/json Content-Length : 269 X-SERVED-BY : l73c013 X-CORRELATION-ID : 1562794898_323_2077717867_l73c013_VDP_WS X-Backside-Transport : OK OK,OK OK X-APP-STATUS : 200 X-Global-Transaction-ID : 213119673 X-Frame-Options : SAMEORIGIN X-XSS-Protection : 1; mode=block X-Content-Type-Options : nosniff Strict-Transport-Security : max-age=2592000;includeSubdomains Cache-Control : no-cache, no-store, must-revalidate Pragma : no-cache Expires : -1 Date : Wed, 10 Jul 2019 21:41:38 GMT Connection : keep-alive Please make sure that you are using the correct test data for this API from the Test Data tab of your sandbox project. If you continue to get the error, please provide the following information for me to investigate further. 1. End Point URL 2. Request Header 3. Request Body 4. Response Header (include the x-correlation-id) 5. Response Body

SLi

Hi @ JbJopito, I'm sorry that you are having problems with mVisa Merchandise API in sandbox. In order to investigate can you please provide me the following information: End Point URL Request Header Request Body Response Header (include the x-correlation-id) Response Body I will take a look and get back to you soon.

SLi

Hi @ Testing, @ kranti-rzp, Good news! We have fixed this issue and I've verified it myself. Please try generating the CSR again and let me know if you have any questions.

Date Registered	January 2019
Date Last Visited
Total Messages Posted	33
Total Kudos Received	2

Visa Developer Community

Re: Visa B2BC - Expected input credentials was not...

Re: 400 Bad Request Error

Re: Error 404 - Visa Card Eligibility iFrame API

Re: vts/provisionTokens access

Re: vts/provisionTokens access

Re: "status":401,"code":"9124"

Re: "status":401,"code":"9124"

Re: Getting Error while trying to test Visa Direct...

Re: Getting Error while trying to test Visa Direct...

Re: Getting Error while trying to test Visa Direct...

Re: VBDS - Starter API

Re: PullFundsTransactions POST [Expected input cre...

Re: PullFundsTransactions POST [Expected input cre...

Re: PullFundsTransactions POST [Expected input cre...

Re: Visa ATM Locator Svc-Solr Execution Failure

Re: 500 Internal Server Error on Visa Account Upda...

Re: 500 Internal Server Error on Visa Account Upda...

Re: 500 Internal Server Error on Visa Account Upda...

Re: 500 Internal Server Error on Visa Account Upda...

Re: 500 Internal Server Error on Visa Account Upda...

Re: Visa Checkout cookies issue

Re: Visa Checkout cookies issue

Re: Merchant Push Payments using Merchant Id.

Re: Merchant Push Payments using Merchant Id.

Re: Getting Error API Internal Error: 1001. Please...

Re: Getting Error API Internal Error: 1001. Please...

Re: Getting Error API Internal Error: 1001. Please...

Re: Getting Error API Internal Error: 1001. Please...

Re: Getting Error API Internal Error: 1001. Please...

Re: CSR validation failed Error when trying to Add...