Blockchain is the technology supporting the process of mining and pricing bitcoins, a procedure whereby the users of this cryptocurrency make payments and transactions in an encrypted and authenticated form on a distributed database.
Any issue related to bitcoins is invariably linked to blockchain, the technology on which the cryptocurrency is based. The end result is a huge database distributed in numerous servers all around the world that gathers all the transactions made in bitcoins. Each one of these operations, encrypted and authenticated, is added to the chain of blocks –or blockchain– on which bitcoins are based. This process would be impossible without APIs.
The fact is that today, bitcoin technology offers many more possibilities and arouses more interest among developers than other online payment systems such as PayPal, for example. Currently within the collaborative development platform GitHub there are almost 3,200 repositories linked to PayPal, whereas there are over 8,000 repositories linked to bitcoin. This fever chart compiled by CoinDesk shows the annual growth of both systems since 2009.
The consulting company Deloitte carried out a survey within the bitcoiner community to discover the future outlook for the sector. Some of the most interesting questions in the survey include: What fields related to blockchain had the highest penetration forecasts? 37% of respondents said the launch of new products, followed by new cases of use.
How does blockchain work?
Anyone can use bitcoins –the only thing you need is a virtual wallet installed in a device. You don’t even need to have much technical knowledge to operate with this cryptocurrency, as it works in the same way as any online payment process. What you have to take into account is that every transaction a user makes with bitcoins –once verified– is added to the blockchain, and at that precise instant it begins to form part of a shared accounting system.
This blockchain or shared accounting system is the result of all the transactions made with bitcoin wallets by all the users on the Internet. Each transaction requires a code and a signature that identifies each user and encrypts and verifies each transaction. Each transaction enters the blockchain through a process known as bitcoin mining, based on a procedure known as proof of work (POW).
Each transaction, which is always public, must be verified to avoid problems within the blockchain: bitcoins must be authentic and not duplicated. Otherwise, someone loses money. The idea is that a series of nodes are responsible for verifying the authenticity of each transaction, a protocol that usually takes 10 minutes. It is reevaluated every 2016 blocks, so the process always takes around that time to verify. The idea is that each transaction is verified by consensus, and the transaction authentication process receives a commission through the proof of work. This system avoids violations without having to depend on a trustworthy arbiter (for example a bank).
● Customer-side encryption: all the virtual wallets used by bitcoiners use JavaScript for encryption, which gives them protection against possible server-side violations.
● Open code: all the code relating to the wallets is open code, which facilitates the joint work of the community of developers.
● Offline transactions: the wallets can operate offline with HTML5.
● Conversion of bitcoins into 22 international currencies.
● Transaction types: these include e-mail processes, SMS and Facebook.
● Payment notification: e-mail, SMS, Skype or HTTP POST calls.
● Possibility of making automatic backups of the virtual wallet.
The importance of blockchain APIs
The whole transaction process, receipt and issue of payments, transactions with virtual currencies and data management would not be possible without an application programming interface for each function. Today blockchain has several APIs for different functionalities. Without some of these, no one anywhere in the world would be able to make any bitcoin transactions:
● Receive Payments API: Version 2 of this interface has been available since last 1 January 2016. This is the simplest way for a company or business to begin to accept automated payments in bitcoins. The API is based on HTTP GET requests and is in charge of creating a single address for each user and for each invoice issued in each bitcoin transaction, an essential condition for good praxis.
● Blockchain Wallet API: Since last 1 January, to use of this API it has been necessary to install a local server to manage the virtual wallet. The communication method used is based on HTTP POST or GET calls. The process for creating a virtual wallet is known as create_wallet from this url: http://localhost:3000/api/v2/create. Each wallet is associated to a password with a minimum length of 10 characters, an authentication code for the API, a private code for each user, the folder where the wallet is created, and an e-mail address.
● JSON RPC API: Since March 2016, the universal recommendation for bitcoin users is to use the new Blockchain Wallet API, although the interface based on RPC calls continues to be compatible with the old Bitcoind RPC to interact with virtual currencies. It can be installed and used from libraries in numerous programming languages: syntax such as Python, Ruby, PHP, Node.js and .NET.
● Blockchain Data API: This can be used to consult the data on the transactions and operations within the blockchain in JSON format.
● Query API: Plain text API for querying blockchain data.
● WebSocket API: this app programming interface gives programmers access to real-time notifications on transactions and blocks.
● Exchange Rates API: This manages the information on bitcoin exchange rates and international currencies in real time and in JSON.
In just one year, the second European Payment Services Directive—or PSD2 as it is better known—has created a new scenario combining innovation and security, in which banks have been progressively opening up access to their infrastructure to third parties.
On December 23, 2015, Directive 2015/2366 of the European Parliament and Council, known as the PSD2 directive, was approved, providing a new regulatory framework for the use of mobile payments, tools from non-banking institutions and enhanced security. What do these changes mean compared to the first PSD and how do they affect companies?
Please, if you can't find it, check your spam folder
×
The email message with your ebook is on the way
We have sent you two messages. One with the requested ebook and one to confirm your email address and start receiving the newsletter and/or other commercial communications from BBVA API_Market
×
PROCESSING OF PERSONAL DATA
Who is the Data Controller of your personal data?
Banco Bilbao Vizcaya Argentaria, S.A. (“BBVA“) with registered address at Plaza de San Nicolás 4, 48005, Bilbao, España and Tax ID number A-48265169 . Email address: contact.bbvaapimarket@bbva.com
What for and why does BBVA use your personal data for?
For those activities among the following for which you give your consent by checking the corresponding box:
to receive newsletter from BBVA API_Market through electronic means;
to send you commercial communications, events and surveys relating to BBVA API_Market to the e-mail address you have provided.
For how long we will keep your data?
We will keep your data until you unsubscribe from receiving our newsletter or, if applicable, the commercial communications, events and surveys to which you have subscribed. Whether you unsubscribe or whether BBVA decides to end the service, your details will be deleted.
How can I unsubscribe to stop receiving newsletters and/or communications from BBVA API_Market?
You can unsubscribe at any time and without need to indicate any justification, by sending an email to the following address: contact.bbvaapimarket@bbva.com
To whom will we communicate your data?
We will not transfer your personal data to third parties, unless it is mandatory by a law or if you have previously agreed to do so.
What are your rights when you provide us with your information?
You will be able to consult your personal data included in BBVA files (access right)
You can modify your personal data when they are inaccurate (correction right)
You may request that your personal data not be processed (opposition right)
You may request your personal data be deleted (suppression right)
You can request a limitation on the processing of your data in the allowed cases (right of limitation of processing)
You will be able to receive, in electronic format, the personal data you have provided to us, as well as to transmit them to another entity (portability right)
You are responsible for the accuracy of the personal data you provide to BBVA and to keep them duly updated. If you believe that we have not processed your personal data in accordance with regulations, you can contact the Data Protection Officer of BBVA at the following address dpogrupobbva@bbva.com.
You can find more information in the “Personal Data Protection Policy” document on this website.
×
PROCESSING OF PERSONAL DATA
Who is the Data Controller of your personal data? Banco Bilbao Vizcaya Argentaria, S.A (“BBVA“), with registered address at Plaza de San Nicolás 4, 48005, Bilbao, España, and Tax ID No. A-48265169. Email address:contact.bbvaapimarket@bbva.com
What for and why does BBVA use your personal data for?
For the execution and management of your request, specifically, download the requested e-book/s.
BBVA informs you that, unless you indicate your opposition by sending an email to the following address: contact.bbvaapimarket@bbva.com, BBVA may send you commercial communications, surveys and events related to products and/or services of BBVA API Market through electronic means.
For how long we will keep your data?
We will keep your data as long as necessary for the management of your request, and to receive commercial communications, events and surveys. BBVA will keep your data until you unsubscribe to stop receiving our newsletters or, where appropriate, until the end of the service. Afterwards, we will destroy your data.
How can I unsubscribe to stop receiving newsletters and/or communications from BBVA API Market?
You can unsubscribe at any time and without need to indicate any justification, by sending an email to the following address: contact.bbvaapimarket@bbva.com
To whom will we communicate your data?
We will not transfer your personal data to third parties, unless it is mandatory by a law or if you have previously agreed to do so.
What are your rights when you provide us with your information?
You will be able to consult your personal data included in BBVA files (access right)
You can modify your personal data when they are inaccurate (correction right)
You may request that your personal data not be processed (opposition right)
You may request your personal data be deleted (suppression right)
You can request a limitation on the processing of your data in the allowed cases (right of limitation of processing)
You will be able to receive, in electronic format, the personal data you have provided to us, as well as to transmit them to another entity (portability right)
You can exercise before BBVA the aforementioned rights through the following address: contact.bbvaapimarket@bbva.com
You are responsible for the accuracy of the personal data you provide to BBVA and to keep them duly updated.
If you believe that we have not processed your personal data in accordance with the regulations, you can contact the Data Protection Officer at the following address: dpogrupobbva@bbva.com
You can find more information in the “Personal Data Protection Policy” document on this website.
Banco Bilbao Vizcaya Argentaria, S.A. owner of this portal uses cookies and/or similar technologies of its own and third parties for the purposes of personalization, analytics, behavioral advertising or advertising related to your preferences based on a profile prepared from your browsing habits (e.g. pages visited). If you wish to obtain more detailed information, consult our Cookies Policy.
Cookie settings panel
These are the advanced settings for first-party and third-party cookies. Here you can change the parameters that will affect your browsing experience on this website.
Technical Cookies (required)
These cookies are used to give you secure access to areas with personal information and to identify you when you log in.
Name
Owner
Duration
Description
gobp.lang
BBVA
1 month
Language preference
aceptarCookies
BBVA
1 year
Configuration Accepted Cookies
_abck
BBVA
1 year
Helps protect against malicious website attacks
bm_sz
BBVA
4 hours
Helps protect against malicious website attacks
ADRUM_BTs
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT1
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BTa
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
xt_0d95e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
__s9744cdb192d044faa1bf201d29fafd1e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
wpml_browser_redirect_test
WPML
Session
Text translation in the portal
wp-wpml_current_language
WPML
24 hours
Text translation in the portal
They are used to track the activity or number of visits anonymously. Thanks to them we can constantly improve your browsing experience
Your browsing experience is constantly improving.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
AMCV_***
Adobe Analytics
Session
Unique Visitor IDs used in Cloud Marketing solutions
AMCVS_***
Adobe Analytics
2 years
Unique Visitor IDs used in Cloud Marketing solutions
demdex (safari)
Adobe Analytics
180 days
Create and store unique and persistent identifiers
sessionID
Adobe Analytics
Session
Launch's internal cookie used to identify the user
gpv_URL
Adobe Analytics
Session
Adobe Analytics plugin: getPreviousValue Capture the value of a certain variable in the following page view, in this case the prop1
gpv_level1
Adobe Analytics
Session
Cookie used to store the DataLayer levl1 of the previous page.
gpv_pageIntent
Adobe Analytics
Session
Cookie used to store the pageIntent of the previous page.
gpv_pageName
Adobe Analytics
Session
Cookie used to store the pagename of the previous page.
aocs
Adobe Analytics
Session
Cookie that stores the first values collected at the beginning of a process.
TTC
Adobe Analytics
Session
Cookie used to store the time between the App Page Visit event and the App Completed event.
TTCL
Adobe Analytics
Session
Cookie used to store the time between the LogIn event and App Completed.
s_cc
Adobe Analytics
Session
Determine if cookies are active
s_hc
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_ht
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_nr
Adobe Analytics
2 years
Determine the number of user visits
s_ppv
Adobe Analytics
Permanent
Adobe Analytics plugin: getPercentPageViewed Determine what percentage of the page a user views
s_sq
Adobe Analytics
Session
ClickMap/ActivityMap features
s_tp
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_visit
Adobe Analytics
2 years
Cookie used by Adobe to know when a session has been started.
They allow the advertising shown to you to be customized and relevant to you. Thanks to these cookies, you will not see ads that you are not interested in.
The advertising is customized to you and your preferences.
Your choice means you will not see customized ads, only generic ones.
Name
Owner
Duration
Description
OT2
VersaTag
90 days
VersaTag Cookie used to store a user id and the number of user visits.
u2
VersaTag
90 days
VersaTag Cookie where the user ID is stored
TargetingInfo 2
MediaMind
1 year
Cookie that serves to assign a unique random number that generates MediaMind.
These cookies are related to general features such as the browser you use.
Your experience and content have been customized.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
mbox
Adobe Target
9 days
Cookie used by Adobe Target to test user experience customization.
×
Looks like you’re browsing from Mexico, so let’s show you the custom content for your
location. Change
Looks like you’re browsing from Spain, so let’s show you the custom content for your
location. Change
Select a country
In order to access the private area and corresponding sandbox, select the country of the APIs you want to use.