Apply the PSD2 Regulation to your business

PSD2 Regulatory APIs via Redsys

Information about PSD2 access to BBVA Spain, available for authorized providers (TPPs) through the Redsys PSD2 HUB. From BBVA API Market you can understand the available capabilities, PSD2 roles, and their main use cases.

Available in:

Spain

Accessible, open, and secure PSD2 information

PSD2 allows authorized providers (TPPs) to access, with the customer’s express consent and strong customer authentication when applicable, certain services on payment accounts accessible online. This framework enables account information, payment initiation, and funds confirmation services.

In Spain, PSD2 access to BBVA customers’ payment accounts is channeled through the Redsys PSD2 HUB. BBVA API Market does not manage registrations, credentials, sandbox, integration, or operational support of TPPs for this solution.

Customer consent and regulated PSD2 access

These PSD2 capabilities are provided under a regulated, secure framework based on customer consent. Strong customer authentication and applicable requirements depend on the corresponding PSD2 flow and the operational channel defined through Redsys.

Account information, payment initiation, and funds confirmation allow authorized TPPs to build aggregation, reconciliation, account-to-account payments, and prior funds availability validation services.

Centralized account information for AISPs

Access payment account information, balances, and movements, with customer consent, to build aggregation, financial analysis, or reconciliation services.

Payment initiation for authorized providers (PISP)

Allow your customers to initiate payments from your environment, in accordance with the applicable PSD2 flow, maintaining an integrated and secure experience.

Funds confirmation

Verify the availability of funds for a specific operation before executing it, without exposing full balances or additional account information.

Offer your customers their payment account information on your own website or app

Authorized AISPs can access, with customer consent, online accessible payment account information: account list, balances, movements, and account holders. This information allows creating aggregation, reconciliation, and financial management services.

Secure and intuitive payment management

Authorized PISPs can initiate payments from payment accounts accessible online, with customer consent and through the corresponding PSD2 flow. The technical connection is channeled through the Redsys PSD2 HUB.

The European PSD2 regulation has marked a before and after in the open banking scenario. The APIs developed by BBVA to meet its requirements are the perfect instrument for any company that wants to go one step further implementing secure, reliable and efficient functionalities.

Ana Climente, Head of open banking – BBVA Spain

Available PSD2 capabilities

This PSD2 solution in Spain is structured through the Redsys PSD2 HUB and allows consulting the capabilities available for BBVA Spain. You can change geography to see the corresponding APIs for each country.

Funds Confirmation PSD2

Confirm if funds are available before a card operation. As an issuer of card-based payment instruments, verify if there are sufficient funds for a specific operation, through the Redsys PSD2 channel.

More information

Payments PSD2

Allow, always with customer consent, initiating PSD2 payments from your environment as an authorized PISP. Initiate payments from online accessible BBVA payment accounts, with customer consent and through the Redsys PSD2 HUB.

More information

Accounts PSD2

PSD2 account information for authorized AISPs. Access, with customer consent, online accessible BBVA payment account information to facilitate aggregation, reconciliation, and financial analysis services.

More information

Access the complete regulatory API catalog

Access

Do you need help with BBVA’s PSD2 APIs?

BBVA API Market can guide you on the available PSD2 capabilities. For technical onboarding, credentials, sandbox, integration, or incidents, you should contact Redsys.

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

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.

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.

Name	Owner	Duration	Description
mbox	Adobe Target	9 days	Cookie used by Adobe Target to test user experience customization.

PSD2 Regulatory APIs via Redsys

Accessible, open, and secure PSD2 information

Customer consent and regulated PSD2 access

PSD2 capabilities through Redsys HUB

Centralized account information for AISPs