Frequently Asked Questions  

Here are some tips to resolve problems with logging in and registering at the Visa Developer Center.

Email

If you are not receiving emails from us, in some cases, the email might get caught in a spam filter. Please check your spam, trash, and archived folders. It could also be that your company’s firewall security is causing the emails not to be going to your company’s email address. Besides that, you may also check your proxy setting, which could be blocking the email.

Password

While logging into your Visa Developer account, please make sure you are providing your email address as how you have entered it in the system, using lowercase or uppercase for characters that you had used lowercase or uppercase on.

When choosing a password, please meet the following requirements listed below. While changing password, please make sure you are providing your email address as how you have entered it in the system, using lowercase or uppercase for characters that you had used lowercase or uppercase on. Your password should NOT contain three consecutive numbers like 123.

To change password, please navigate to this link - https://developer.visa.com/identity/user/forgot.

Or, you can login to Visa Developer and navigate to this link to reset password - https://developer.visa.com/portal/account/password

If you are experiencing an issue, please try the following to resolve the issue.

• Try using another web browser (e.g. IE, Chrome, etc.).
  
• Try clearing your cache and cookies.
• Remove extra spaces and do not press TAB.
• Avoid using a password containing parts of your username or company name (e.g. "cUst").
• Try using a different type of special character.
• Make sure your email address and password do not have the same letter sequence or character sequence.

Account Lockouts

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 (VDPCA-SBX.pem) and your private key.

To generate a CSR to use in the sandbox, you have two options:

• Visa generates a CSR for you
• Generate your own CSR

For more details, refer to the Two-Way SSL guide.

To fix issue with your test credentials:

1. Verify the client certificate being used in the certificate chain with the following command:
   OpenSSL> verify -verbose -CA file VDPCA-SBX.pem cert.pem
   You should receive:
   cert.pem: OK
   
2. Check the contents of keystore by using the following command:
   keytool -list -keystore <JKS_File_Path>
   The above command displays the three entries related to Visa Developer as following:
   • Single Private key entry. The private key entry comprises of environment private key and the environment client certificate. The private key should be the same that the client has used for generating Certificate Signing Request for the requested environment. Please ensure that the correct environment certificates are being used.
   • Visa Development Platform Intermediate Certificate.                          
   • Visa Development Platform Root Certificate

You can download all three certificates above from the "Credentials" section on the page for the appropriate environment such as Sandbox, Certification or Production.

The easiest way to troubleshoot connectivity issues is to use the SOAPUI tool. Refer to Testing Two-Way SSL Connectivity Using SOAPUI section in 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:

• Sandbox: sandbox.api.visa.com
• Projects requiring testing in the Certification environment: cert.api.visa.com
• Production: api.visa.com; api.visa.co.in (India) 
  

To fix the connectivity issues with the Sandbox: sandbox.api.visa.com from the Data Power:

1. Create a project
2. Click the "Sandbox" page from the left navigation of the project
3. In the "Credentials" section on the page, click "Add Two-Way SSL" and then "Add CSR" to create a credential
4. In the "Credentials" section on the page, download the GeoTrust Certificate and Project Certificate (cert.pem)
5. In the Trusted Certificates section of Data Power appliance configuration; add Geotrust.pem and sandbox.pem (Note: sandbox.pem is optional and may be needed if hostname verification is enabled)
6. Run the command for sandbox.pem 
   openssl s_client -showcerts -connect sandbox.api.visa.com:443
7. In the Client Configuration section, add the private key in the client private key field and cert.pem in the client certificate field as shown below:
8. 
   

Refer to Visa Developer Error Codes for a detailed list of Visa Developer error codes and their descriptions.

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 protected]).

There is no cost to you to develop your project using any of the Visa APIs in the sandbox. Contact Visa for pricing and commercial details to use in Production.

To navigate between the dashboards, select the environment you'd like to switch to from the sidebar as depicted below

In order to use the products in the certification or production environment, complete the steps on the "Onboarding Dashboard" of your project. Visit Going Live for an overview of the processes to be completed before the APIs can be used in the production environment.

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.

On the "Sandbox" page of your project, you can:

• Click "Add Two-Way SSL" to add a new Two-way SSL credential
• Click "Add X-Pay Token" to add a new X-pay token

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

 Two-way SSL certificates are valid for 27 months. X-pay tokens are valid for 24 months.

Yes. In sandbox, certification and production the new certificate will come with a new user id and password.

Your sandbox credential has expired. To renew the credentials, on the "Sandbox" page of your project:

• Click "Add Two-Way SSL" to add a new Two-way SSL credential
• Click "Add X-Pay Token" to add a new X-pay token

Please refer to Visa Partner's Learn section that introduces you to the payments ecosystem, how it works and the steps needed to launch a card program. You’ll come away ready to craft your own payments strategy – with a solid grasp of payment economics and the overall ecosystem.

You'll learn about:

• The Four Party model
• The transaction lifecycle
• Payment options (debit, credit, prepaid, etc.)
• The economics of managing a card portfolio
•  Implementation strategies

Please contact Visa Developer Support at [email protected] to enable your account.