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:
Refer to Visa Developer Error Codes for a detailed list of Visa Developer error codes and their descriptions.
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 (email@example.com).
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.
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 firstname.lastname@example.org.
Visa Developer has a new user experience for progressing a project from the sandbox environment through certification (if applicable) and to production. The new process is called Going Live. For details, refer to Going Live with Visa Developer.
Visa is responding to client requests to remove friction from the onboarding process and to make the client journey to go live more transparent and clear.
No, the process to register a developer user account has not changed.
When you log in, you will be taken to the dashboard where you will see all your existing projects, if any. There is no change to the dashboard.
Yes, the Project Promotion icon on the left navigation has changed to a Going Live icon. There are newly designed screens with detailed instructions for completing the going live process. You will also be able to see status icons to indicate the environment you are in and if a step is in progress or completed.
When you have completed testing in the sandbox and are ready to request credentials for either the certification or production environment, you will need to follow a new set of steps that will allow you to easily submit the information required. The new process is called Going Live. For details, refer to Going Live with Visa Developer
Projects that are currently in the process of promotion will not be impacted. Data associated with a project will be migrated to the new flow. You do not have to start over and you do not have to take any action.
Existing projects will continue to be available in your dashboard. When you are ready to move to the next environment, follow the new process as described in Going Live with Visa Developer.
Yes, you can renew sandbox, certification, and production certificates for a project.
A: Yes, you can renew sandbox, certification, and production certificates for a project.
When sandbox certificates expire, you will see a notification in the Credentials section of your dashboard.
You will have an option to “Get New Certificate” in the Credentials section of your dashboard. You will be guided through the workflow to request a certificate.
Expiration notifications are sent for projects that have been promoted to certification and production environments only.
For projects that have been promoted to the certification or production environments only, Visa Developer will send email notifications at predetermined intervals, to the “owner” (full access) registered users for the project.
Notifications will be sent 120, 90, 60, 30, 15 and 7 days prior to expiration.
You will see this information in a new status column on the dashboard indicating either “Certificate Expired” or “Certificate Expiring”.
The new workflow is enabled 120 days prior to a certificate expiring.
Mutual SSL certificates are issued for 27 months.
Yes. In sandbox, certification and production the new certificate will come with a new user id and password.
Your sandbox certificate has expired. Navigate to the Credentials section of your dashboard to the “Get New Certificate” link.