Here are some tips to resolve problems with logging in and registering at the Visa Developer Center.
Email Confirmation Issues
When you register at the Visa Developer Center, you will need to confirm your email address. In some cases, the email might get caught in a spam filter and you won't receive the email to complete your registration. You can always send yourself another email by going to: the Visa Developer Center > Login. This will send out another email confirmation message to your registered email address. From there, you can confirm your email and login with your email address as your user ID, and use your established password.
If you are having issues with login, you can also reset your password by going to: Visa Developer Center > Login. This will allow you to change your password through an email delivered to your inbox.
If you enter an incorrect password several times, your account will be locked out and you will be forced to reset your password to get back into your account. You can reset your password by going to Visa Developer Center > Login. This will allow you to change your password through an email delivered to your inbox.
The Certificate Signing Request (CSR) is a prerequisite to get your project certificate (cert.pem), which is required to establish a Two-Way SSL connection. Additionally, you will need a root certificate (VICA-SBX.pem) and your private key.
To generate a CSR to use in the sandbox, you have two options:
For details, refer to Getting Started > Testing Connectivity and Authentication. This section describes how to obtain a private key, client certificate, and Visa Developer certificate authority root certificate, as well as how to bundle the certificates into keystores, using Java keytool or OpenSSL.
To fix issue with your test credentials:
You can download all these three certificates from the project details page under the appropriate environment (for example, Certification or Production) tab.
The easiest way to troubleshoot connectivity issues is to use the SOAPUI tool. Refer to Testing Two-Way SSL Connectivity Using SOAPUI section in Getting Started > Two-Way SSL that includes steps to access the helloworld project. This is the fastest way to test your access credentials and to create sample HTTP requests that work. Once you get your SOAPUI connection to work, review the raw HTTP request – you will get the exact value of an encoded username and a password that works. You can then compare the working value with the value you generate in your IDE.
Use the following endpoints for:
To fix the connectivity issues with the Sandbox: sandbox.api.visa.com from the Data Power:
The 401 (Unauthorized) status code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource (or endpoint). Visa Developer supports multiple authentication and authorization methods. The request could fail due to one of the following reasons:
Common Root Causes:
Common Root Causes:
The 403 (Forbidden) HTTP Status code indicates that this project does not have permission to access the requested resource. This can happen if you are trying to invoke API request for a resource that is not part of your project e.g. if you have created a project with Visa Direct Product but are trying to use the same credentials to access Visa Consumer Transaction Controls.
X-CORRELATION-ID is a unique ID that system generates for every API request and is included in the Response Headers. If you are using SOAP UI, you can see the X-CORRELATION-ID under Response section as shown below. This is helpful for debugging purposes when you report your issues to Visa Developer (firstname.lastname@example.org).
Visa Developer is an open platform. There is no cost to you to develop your project using any of the Visa APIs in the sandbox. When you are ready to transition to production to use the APIs, fees may apply. Fees are evaluated by project as they are a function of many elements, including the nature of your project and your relationship with any partner.
PCI DSS standard version 3.1 has been retired in October 2016 and the new PCI DSS version 3.2 mandates using TLS 1.2 (or higher) protocol and makes all older TLS versions (e.g. SSL v3, TLS 1.0, TLS 1.1) non-compliant. The standard requires the new TLS requirement to be implemented by June 2018.
In preparation for this requirement, Visa plans to disable TLS 1.0 and TLS 1.1. These versions will be disabled first in Sandbox prior to Production to give you an opportunity to test these in Sandbox and ensure you are using TLS 1.2.
For details, refer to the TLS Blog.
An SSL exception related to mismatch in protocol version may happen if the Transport Layer Protocol version is older than TLS 1.2.
Refer to the TLS Blog for instructions on how to fix this issue.
Yes, your sandbox credentials would still work. You do not need to create or generate new API keys for Sandbox or Production.
As a part of migrating accounts to Visa Developer Center, for your protection we’d like you to simply revalidate your account. You will receive an email to do so. Just click on the link provided in the email and you’re done!
Your profile and configuration pages are located in your Project Dashboard via the “Configurations” link provided in the Left Navigation bar. Once you select this option, you will see Visa Checkout or Visa Token Service listed in the main pane. Select the accordion menu icon next to the API to reveal the links to the product specific profiles and configurations.
Visa Token Service is a restricted product. If you’re interested in using Visa Token Service and believe you meet the requirements, please email us at email@example.com.