Do you need help with BBVA’s PSD2 APIs?
BBVA API Market can guide you on available PSD2 capabilities. For technical registration, credentials, sandbox, integration, or incidents, you should contact Redsys.
Confirm the availability of funds in an account.
Funds Confirmation PSD2 enables issuers of card-based payment instruments to check, via the Redsys PSD2 HUB, whether a BBVA account has funds available for a specific transaction. This allows you to anticipate the viability of the transaction within the applicable PSD2 framework.
Technical access to Funds Confirmation PSD2 is provided through the Redsys PSD2 HUB, after registration on that platform. BBVA API Market provides information about BBVA’s PSD2 API capabilities, while Redsys manages credentials, sandbox, integration, and operational support for TPPs.

The purpose of this PSD2 capability is to allow issuers of card-based payment instruments to confirm, before a specific transaction, whether funds are available in the associated BBVA payment account, provided the account is accessible online and the customer has given prior consent.
The check applies to cards issued by a third party and linked to a BBVA payment account accessible online, in accordance with the PSD2 funds confirmation flow.
The technical connection for this PSD2 capability in Spain is made through the Redsys PSD2 HUB. This enables you to validate funds availability for a specific amount and reduce uncertainty before completing the transaction.
Advantages of the Funds Confirmation PSD2 API

Check whether funds are available for the queried amount before authorizing a transaction. If funds are insufficient, you can manage the rejection predictably within your service flow.

The customer must authorize the funds confirmation when applicable and complete strong customer authentication in accordance with PSD2. The technical operation is performed through Redsys’ PSD2 channel.

By knowing whether a specific transaction has available funds, you can design smoother journeys, reduce payment friction, and improve the experience without exposing additional account information.
Funds Confirmation PSD2 offers:
The flow allows collecting the customer’s consent and applying strong customer authentication when appropriate to confirm funds availability for a specific amount.
You can check the status of authorizations and consents in accordance with the flows available in the Redsys PSD2 HUB.
You will receive a response on funds availability for the queried amount before completing the transaction.
To use Funds Confirmation PSD2, you must act as an issuer of a card-based payment instrument and the card must be linked to a BBVA payment account accessible online. The technical connection and integration are carried out through the Redsys PSD2 HUB.

Before making the first request for confirmation of funds, your customer gives their consent so that you can check if they have a certain balance in their BBVA account through a bank interface.

To grant such consent, the customer has authenticated using their BBVA online banking access and signature key (SCA).

Once the customer’s consent is obtained, a token is created that allows the confirmation of funds in unaided mode.

Your service can make availability inquiries regarding a specific balance in the customer’s BBVA account. Under no circumstances are the funds blocked.

Up-to-date information is essential when it comes to providing an efficient and optimized service. The Funds Confirmation PSD2 API seeks precisely to confirm this key information when performing debit card transactions.
Ana Climente, Head of Open Banking at BBVA Spain
If Funds Confirmation PSD2 is useful to you, you may also be interested in the PSD2 account information and payment initiation capabilities available to authorized TPPs.
Harness the full potential of the European Payments Directive.
Allows your customers to start their payments immediately and automatically from your own platform.
Subject to express consent, customer may share their BBVA identification data.
Access the complete API catalog
AccessBBVA API Market can guide you on available PSD2 capabilities. For technical registration, credentials, sandbox, integration, or incidents, you should contact Redsys.
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:
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 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 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.
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.
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.
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
| 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.
| 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.
| 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 Spain Argentina Peru Colombia Belgium Chile USA France Hong Kong Italy Portugal United Kingdom Turkey Uruguay Venezuela Alemania, so let’s show you the custom content for your location. Change
In order to access the private area and corresponding sandbox, select the country of the APIs you want to use.
© BBVA API_Market. Legal Notice, Personal Data, Cookie Policy, Security
Choose the country for default content display.