Visa Developer Community

SLi

Hi @kamalmehta, The error 401-9124 usually means that basic authentication is sent but the username or password is incorrect. Can you please confirm that you are using the correct project credentials for the B2B Connect API?

SLi

Hi @kunalanand241, For sandbox testing, only test data provided in the "Test Data" tab of your project dashboard will work. Please refer to below screenshot. Here's a working payload for the push funds transaction API: End Point https://sandbox.api.visa.com/visadirect/fundstransfer/v1/pushfundstransactions Method POST Request { "amount": "124.05", "localTransactionDateTime": "2020-06-29T20:29:53", "senderAddress": "901 Metro Center Blvd", "pointOfServiceData": { "panEntryMode": "90", "posConditionCode": "00", "motoECIIndicator": "0" }, "recipientPrimaryAccountNumber": "4957030420210496", "colombiaNationalServiceData": { "addValueTaxReturn": "10.00", "taxAmountConsumption": "10.00", "nationalNetReimbursementFeeBaseAmount": "20.00", "addValueTaxAmount": "10.00", "nationalNetMiscAmount": "10.00", "countryCodeNationalService": "170", "nationalChargebackReason": "11", "emvTransactionIndicator": "1", "nationalNetMiscAmountType": "A", "nationalReimbursementFee": "20.00", "costTransactionIndicator": "0" }, "cardAcceptor": { "address": { "country": "USA", "zipCode": "94404", "county": "San Mateo", "state": "CA" }, "idCode": "CA-IDCode-77765", "name": "Visa Inc. USA-Foster City", "terminalId": "TID-9999" }, "senderReference": "", "transactionIdentifier": "381228649430015", "acquirerCountryCode": "840", "acquiringBin": "408999", "retrievalReferenceNumber": "412770451018", "senderCity": "Foster City", "senderStateCode": "CA", "systemsTraceAuditNumber": "451018", "senderName": "Mohammed Qasim", "businessApplicationId": "AA", "settlementServiceIndicator": "9", "merchantCategoryCode": "6012", "transactionCurrencyCode": "USD", "recipientName": "rohan", "senderCountryCode": "124", "sourceOfFundsCode": "05", "senderAccountNumber": "4653459515756154" } Response { "transmissionDateTime": "2020-06-29T23:47:25.000Z", "settlementFlags": { "settlementServiceFlag": "9", "givUpdatedFlag": "false", "settlementResponsibilityFlag": "true", "givPreviouslyUpdatedFlag": "true" }, "transactionIdentifier": 153563132307052, "actionCode": "65", "responseCode": "5" }

SLi

Hi @kunalanand241, Thank you for reporting the API doc error. I'll let our internal team know so that this error can be corrected in a future release.

SLi

Hi @kunalanand241, Please try "merchantCategoryCode": ["5814"], with the lower case "m" and let me know if you can get a successful response.

SLi

Glad to hear that you have resolved the issue and thanks for sharing the link to the IIS setting. Please navigate to the below Visa Direct API reference page for details on each attribute parameter and value: https://developer.visa.com/capabilities/visa_direct/reference

SLi

Hi @Pdro, There is a Visa Developer Center Playground tool. It is 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. Will this work for you? https://community.developer.visa.com/t5/Developer-Tools/How-to-test-and-troubleshoot-APIs-with-the-Visa-Developer-Center/ba-p/13357

SLi

Hi @animeshpaul91, Happy to hear that you got Postman to work. I'll see if I can get sample Python code to share. I am not familiar with Python unfortunately.

SLi

Hi @pavelcardgeny, Please check out Visa Cardholder Purchase Inquiry API and its use case. Links below: https://developer.visa.com/capabilities/visa-cardholder-purchase-inquiry https://developer.visa.com/use-cases/transaction-recognition Feel free to reach back out if you have further questions.

SLi

Hi @animeshpaul91, The error 400 - 9124 usually means that the client certificates are not sent. Please check the following in Postman: Settings => Certificates: add your client certificates Settings => General Tab: SSL Certificate Verification is ON Please refer to the below thread for details on Postman setup. All details including screenshot is posted here. https://community.developer.visa.com/t5/Use-Cases/APIs-for-payment-gateway-9124-error/m-p/10448#M113 Hope this helps, please reach out if you need further assistance.

SLi

Hi @NitinMore7 , I am not familiar with Volley, but I highly recommend watching our Two-Way SSL webinar for a hands on guide on how to establish a connection through Two-Way SSL using Postman. Webinar: Configure Two-way SSL with openSSL and Test on Postman https://community.developer.visa.com/t5/Webinars/Configure-Two-way-SSL-with-openSSL-and-Test-on-Postman/ba-p/15089?utm_source=nlblogcta2&utm_medium=twowaywebinar&utm_campaign=april_communityNL

SLi

Hi @granular-smart, 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/pages/working-with-visa-apis/two-way-ssl I was able to get successful results using the below working payload: End Point https://sandbox.api.visa.com/visadirect/fundstransfer/v1/pullfundstransactions Method POST Request { "surcharge": "11.99", "amount": "100", "localTransactionDateTime": "2020-06-24T11:07:21", "cpsAuthorizationCharacteristicsIndicator": "Y", "colombiaNationalServiceData": { "addValueTaxReturn": "10.00", "taxAmountConsumption": "10.00", "nationalNetReimbursementFeeBaseAmount": "20.00", "addValueTaxAmount": "10.00", "nationalNetMiscAmount": "10.00", "countryCodeNationalService": "170", "nationalChargebackReason": "11", "emvTransactionIndicator": "1", "nationalNetMiscAmountType": "A", "nationalReimbursementFee": "20.00", "costTransactionIndicator": "0" }, "cardAcceptor": { "address": { "country": "USA", "zipCode": "94404", "county": "081", "state": "CA" }, "idCode": "ABCD1234ABCD123", "name": "Visa Inc. USA-Foster City", "terminalId": "ABCD1234" }, "acquirerCountryCode": "840", "acquiringBin": "408999", "retrievalReferenceNumber": "330000550000", "senderCurrencyCode": "USD", "addressVerificationData": { "street": "XYZ St", "postalCode": "12345" }, "cavv": "0700100038238906000013405823891061668252", "systemsTraceAuditNumber": "451001", "businessApplicationId": "AA", "senderPrimaryAccountNumber": "4895142232120006", "settlementServiceIndicator": "9", "foreignExchangeFeeTransaction": "11.99", "senderCardExpiryDate": "2020-03", "nationalReimbursementFee": "11.22" } Response { "transmissionDateTime": "2020-06-24T17:24:39.000Z", "approvalCode": "98765X", "cavvResultCode": "8", "settlementFlags": { "settlementServiceFlag": "9", "givUpdatedFlag": "false", "settlementResponsibilityFlag": "true", "givPreviouslyUpdatedFlag": "true" }, "cpsAuthorizationCharacteristicsIndicator": "3333", "transactionIdentifier": 159238227176517, "actionCode": "00", "responseCode": "5" } Hope this helps, please let me know if you have any other questions.

SLi

Hi @granular-smart Please try below working payload. { "amount": "120", "localTransactionDateTime": "2020-06-18T04:13:00.000", "recipientPrimaryAccountNumber": "4761360055652118", "cardAcceptor": { "address": { "country": "USA", "zipCode": "94404", "city": "new york", "county": "San Mateo", "state": "CA" }, "idCode": "ABCD1234ABCD123", "name": "Visa Inc. USA-Foster City", "terminalId": "ABCD1234" }, "transactionIdentifier": 810917935155075, "acquirerCountryCode": "840", "acquiringBin": "408999", "retrievalReferenceNumber": "412770451018", "systemsTraceAuditNumber": "451018", "transactionFeeAmt": "10", "settlementServiceIndicator": "9", "merchantCategoryCode": "6012", "transactionCurrencyCode": "USD", "merchantVerificationValue": { "mvvAcquirerAssigned": "41394644363445313243", "mvvVisaAssigned": "41394644363445313243" }, "feeProgramIndicator": null } If you still get an exception, please let us know what tool you are using to test the API and the correlation ID of the error.

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

Date Registered	January 2019
Date Last Visited
Total Messages Posted	45
Total Kudos Received	3

Visa Developer Community

Re: Getting error while calling getBank details AP...

Re: Testing Visa Direct push fund transactions wit...

Re: Merchant Locator API showing 404 error

Re: Merchant Locator API showing 404 error

Re: gettingresponse code message- "message": "Expe...

Re: visa testing system

Re: Bad Handshake on Pythoon Client.

Re: Getting digital receipt of spend

Re: VISA Travel Predict API Inaccessible from Post...

Re: Two way SSL

Re: gettingresponse code message- "message": "Expe...

Re: got invalid pan while hitting https://sandbox....

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...