Visa Developer Community

  This topic is an extension of a previous webinar session, where we walked you through how to run a Visa Direct transaction in Python (don’t worry we have that recording here if you missed it).   Join Visa SW Engineer Jiri Medlen for this hands-on training session, showing you the steps on how to use the Query API to retrieve PushFundTransactions (OCT) transaction details. Plus, exclusively for the webinar, you will get a chance to watch Jiri simulate a timeout and watch him figure out how he retrieves the data using the Query API.     What you can expect: An overview of the Query API How use the Query API to retrieve PushFundTransactions(OCT) transaction details Demo of how to retrieve data after a timeout using the Query API   ... View more

Getting started with Message Level Encryption (MLE) just got a little easier with an enhanced MLE Encryption Guide.    As many of you know, API products hosted through Visa Developer leverage either Mutual SSL or X-Pay Token to authenticate/authorize clients. Now, Visa also sends and receives sensitive information for which, an additional level of security in the form of Message Level Encryption is required as per TSR Guidelines.     MLE on Visa Developer provides an enhanced security for message payload by using asymmetric encryption technique (public-key cryptography).    Why this matters?   While MLE is optional or not applicable for most Visa APIs, there are some APIs which support MLE in enforced/mandatory condition only. This means, users will need MLE implemented on top of Mututal SSL Authentication. The encryption requires separate key-pairs for the Request or Response payloads of the transaction.    Users who must implement MLE will see changes in the Go-Live process which includes new important key steps like uploading additional files - so it's important to get caught up on what is required here and we've laid it out for you in our Developer API Documentation - MLE Encryption Guide page.    Get all the details in the guide, including encryption requests and decryption response payloads in Java, Python, Node.JS and C#.   Like what you see in the guide? Want to see more? Let us know your feedback by commenting below, we'd love to hear from you.  ... View more

Share with the community your tips to how to run the Query API in Visa Direct transaction using Python and  we’ll send you a new edition Visa Dev water bottle.        Questions to help you get the wheels turning:   What did you learn during our latest Visa Dev webinar on the topic? What should devs struggling with the steps keep in mind? What mistakes did you run into and how did you fix it? What's your favorite tool you use to run a Visa Direct transaction?   ... View more

  Visa Developer sandbox secures connections with clients by using one of two authentication methods to invoke an API. Last month’s Visa Dev Webinar covered the Two-way SSL method (watch recording here). Now, it’s time for you to learn all about X-Pay Token and which APIs require this method…and why?  We’ve recruited two of our own X-Pay Token pros to host this hands-on developer training. Watch this webinar to join Saranya Rammohan and Abhishek Yadav who will not only walk us through the existing developer documentation on the topic, but will also guide us through new helpful tips and tricks for running an X-Pay Token connection. Plus, exclusively for the webinar, you will get to watch how to test the connection using Postman, this is a tutorial we have not shared on our developer center until now. Be one of the first to learn how Visa does it.           Here’s what you can expect:   Know what HTTP Request is - what do the body and headers look like? An overview of which APIs require X-Pay Token (save time spent on research for testing) The basics – what is X-Pay Token and why use it? A demo of X-Pay Token that tests connection using Postman   ... View more

Hey everyone! We've just deployed VDP R2007 which includes the launch of a few new APIs including the Visa Merchant Screening Service (VMSS), plus check out the newly updates Visa Developer list of Trusted Certifying authorities for trusting your server side certificates.     For a comprehensive list of all the features we've been adding,   see the full release note pages on the developer center   (we've summarized it below).    New Products:   Visa Merchant Screening Service-  allows Acquirers to identify potentially high-risk, unreliable or fraudulent Merchants and Third Party Agents prior to making an onboarding decision and therefore helps reduce risk exposure to fraudulent and illegal transactions, and helps protect against brand damage and non-compliance assessments.   Visa Stop Payment Services- e nables Visa card issuers to stop card-on-file payments (including recurring and installment payments) from being authorized, cleared, and settled through VisaNet. The service can help to provide Visa issuers with a method for handling cardholder stop payment requests.   Visa ReadyLink-  allows a Visa reloadable prepaid cardholder to add funds to their account from a ReadyLink enabled merchant terminal.  The VRL Merchant Locator API enables cardholders to search for ReadyLink enabled merchant locations. The API allows the location of participating ReadyLink merchants to be delivered in a user friendly way.   Visa Cardholder Verification Service -  gives clients the power to verify consumer identity by using Issuer step-up to deliver dynamic authentication data directly to their cardholders.   Learn more about these new products in our latest release notes here.    New API Features:   B2B Virtual Account Payment Methods -  this now offers a new endpoint called ‘Get Payment Controls’.  This endpoint provides more visibility into the current state of an account’s authorization-level payment controls.    Payment Account Attributes Inquiry -  Recently we updated Payment Account Attribute Inquiry due to which General Attributes Inquiry API is no longer available to new customers. Current customers are not impacted by this change.  Learn more about these new products in our latest release notes here.  Platform Updates: Check out the updates List of Trusted Certifying Authorities    As always, if you have any questions, ask below and we'll help you out.  ... View more

Read details and FAQ on Visa Developer Platform Production Environment Migration to a New API routing model.   What is happening?   In our effort to provide a high quality API performance, we will be migrating our Production gateway to a direct-routing model. This update should help lower API latency and increase overall performance for all of your VDP integrations. During our migration, we will be changing the infrastructure that hosts our api.visa.com endpoint and will need to update our external domain certificate.   What does this mean for me?   Our Visa Developer integration best practices recommend that client’s trust our endpoints by inspecting their root certificates only.  If you are following our best practices, this migration will be completely transparent to your API integrations   We understand that some of our clients need to inspect our leaf or intermediate certificate. These clients will need to pre-trust our new endpoint certificates listed on our Visa Developer PKI page by 10/22/20. https://developer.visa.com/pages/visa-developer-pki   If you have multiple application environments for multiple Visa API integrations, you will need to pre-trust our new certificates for each of those environments   What happens if I do not take action?   If you are only inspecting our root certificates, no action is needed.   If you are inspecting our leaf or intermediate certificate and do not take action by 10/22/20, your Visa API integrations will be impacted.     Frequently Asked Questions   Can I trust both old and new certificates at the same time?   Yes you can. There will be a period where we will need your environments to contain both our current and new certificates. This will allow us to seamlessly migrate to our new routing model, and account for any unlikely shifts in scheduling.   When can I remove the old certificate?   If you are following our best practices, no certificate removal would be necessary. If you have been inspecting our leaf or intermediate certificate, you will be able to remove the old certificate(s) on 12/01/20.   How can I tell if I am inspecting Visa’s leaf or intermediate certificate?   Your application development, IT, networking, or security organizations should be able to guide you through your specific implementation and configuration   Are these the certificates we use for mTLS authentication?   No. Your mTLS certificates that are used for API authentication are not affected by this migration. Only the certificate that is used to identify our production gateway domain – api.visa.com – is affected   If you have any further questions or need help comment below, use our forum or email us at developer@visa.com ... View more