https://www.bbvaapimarket.com/wp-content/themes/gobp-portal/img/microillustrations/payments.svg

Notifications

Mexico

Private

Subscribe to events and receive webhook notifications

Manage subscriptions to important events for your BBVA products, directly from your systems. The Notifications API enables you to register, unsubscribe, and modify your preferences for receiving HTTP webhook notifications. This ensures that your systems receive the necessary information at the right time.

Digital Ecosystems

Payments

Information

Collections

The Notifications API is owned by BBVA México, S.A., Institución de Banca Múltiple, Grupo Financiero BBVA México.

Your systems will receive notifications of relevant events in real time

In a business environment that doesn’t stop, the key is to manage information intelligently. With the Notifications API, BBVA offers you the ultimate tool to manage your subscriptions to the events that impact your operation. Choose what notifications to receive and where, keeping your systems synchronized and ready to act.

Our API is designed so that you can register new subscriptions to events you are interested in, modify existing ones or cancel them with complete flexibility. Once configured, notifications for the events you have subscribed to will be sent automatically through secure and reliable HTTP webhooks, allowing you to automate processes and react instantly to every new development.

In practice

Subscription control: Manage your system’s event subscriptions: add, remove, or modify them on demand, as needed.
Automatic notification receipt after subscribing: Once subscribed, your system will receive HTTP webhooks with relevant information instantly. You will receive this at the callback URL that you declare when you subscribe or modify your subscription. Your system should only "listen" to these events and confirm their receipt, programmatically.
Note: Make sure you comply with the relevant contracting process. The times to start receiving webhook notifications on the Callback URL you declare may vary and will be communicated to you by an executive.

Subscribing to events on your own and receiving webhook notifications

Independently manage subscriptions, cancellations, and modifications of events to which your system subscribes. Once subscribed, your system receives webhooks with relevant information instantly.

Failed notifications are automatically retried

If your systems are temporarily down, we’ll automatically retry sending notifications until your system confirms they’ve been received. That way, you won’t miss a thing.

Decision-making or automations based on notifications

Avoid constantly checking (for example, via querying another API) the status of a resource (e.g. a payment). Instead, listen to the notifications that BBVA will send directly to your systems. Turn notifications into value for various tasks, such as automatic payments reconciliation.

Status changes in sent SPEI payments

Enables webhook notifications for completed SPEI transfers (when they become successful and/or returned)

Status changes in sent BBVA payments

Enables webhook notifications for completed BBVA transfers

CIE payments received through "BBVA Pay By Bank"

Enables webhook notifications for CIE payments made by customers to CIE enterprise customers using the “BBVA Pay By Bank” product.

How does it work?

Get started with the Notifications API

1. Subscribe to the Notifications API

Depending on the type of event you want to receive, you will need to carry out a subscription process. Consult your executive to review requirements and documents.

2. Declare the address of the server where you will receive the webhooks

When you subscribe, share with us the base URL where you will receive the notifications, so that BBVA can ensure that you will be able to send them after subscribing.

3. Manage event subscriptions (registration/ cancellation/modification)

Generate an initial registration, declaring the event type, the address (callback URL) where you will receive it, and other relevant information for the corresponding event type. You can then edit or unsubscribe from it on demand.

4. Receive HTTP webhooks on your systems

Your systems will receive programmatic and automatic HTTP webhook notifications for the events you’ve subscribed to.

Other APIs you may be interested in

The Notifications API and the notifications you will receive go hand in hand with other services that generate such notifications, for example:

Business Payments

Initiate payments and be notified of their status in real time

More information

Pay By Bank

Allows your customers to pay for purchases on an e-commerce directly from BBVA debit accounts

More information

Access the complete API catalog

Access

Let’s talk

Get in touch with us to find out how our suite of APIs can turn your innovations into reality.

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.