BBVA API Market
Windows 10 users will be able to use Microsoft Wallet, the online payment platform, through Microsoft Edge, the new web browser for Windows, thanks to the implementation of the new Payment Request API developed by the W3C and presented last December. Payment Request API is a method of communication that acts as an intermediary between digital commerce platforms and the system where users have stored their payment details.
It is available to developers that have the Build 14986 or later of the Windows Insider Preview program. Microsoft Edge will connect to Microsoft Wallet to provide a user payment interface. Both the Microsoft Edge update with the new payment interface and Microsoft Wallet will be launched to the public in the next Creators Update in mid 2017.
Its operation is simple: Payment Request API is a standard method to make payments both on the web and in native apps. During an electronic purchase through the software the user is using at the time, whether a browser like Microsoft Edge or any program, the software takes care of invoking a digital portfolio or equivalent where users store their payment credentials.
Through here and with the Payment Request API the user sends addresses and billing information to the site or e-commerce platform, which returns updated information with the final costs. At that time, the user, again within the digital wallet, makes the payment. Finally, Payment Request API is responsible for communicating payment information and receiving the appropriate response.
Google has already implemented the Payment Request API in Chrome 53 for Android, and will include support for the interface in the future to desktop Chrome. With a platform as extended as Android, and the efficiency and security of Google cloud services, mobile e-commerce will be easier for hundreds of millions of users worldwide.
Mozilla and Opera, meanwhile, have not implemented this feature yet. And it is very unlikely to reach Internet Explorer, because Microsoft is focusing most of its resources on Edge.
Finally, Apple has not shown willingness to implement this protocol in Safari as it has Apple Pay JS, a similar but proprietary system whereby the company’s customers can make online payments by taking advantage of biometric identification in the company’s hardware.
Developers who want to implement online payments securely in their e-commerce platforms with the highest present and future certifications can do so thanks to BBVA Payments. With BBVA and the Payments API you can pre-empt the PSD2 directives which will enter into force in 2018.
BBVA offers a multitude of various financial APIs to facilitate the work. Payments uses Customers White Label, a method which can provide gateways for e-commerce that remove the need to manage an actual payment system. The protocol makes it possible to:
– Create new customers: add a new customer with the required data. The method will return a unique identifier that can be used in the future for information.
– Receive information on a specific customer: once added, you can use the BBVA Customers White Label API to receive customer data when necessary.
– Update customer information: with new data and identifiers, and remove it from the platform.
You no longer need to go to a bank branch to open a bank account. APIs allow you to complete this and any other banking operations without leaving your company's own platform, with a fully integrated experience.
A new edition of the Secure Payments & ID Congress was held on November 17, an event dedicated to analyzing the current state of collection and payment services, authentication and identification processes, and fraud security and prevention.
A few years ago, Bank of Mexico implemented the SPEI payment system and the CIE agreements to facilitate bank transactions between individuals and to provide commercial operations with more information. We how they work here.