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

Request to Pay

Spain

Private

The tool that will allow you to efficiently manage your collections

With the Request to Pay API, you can initiate payment requests that will be sent instantly to your payers.

Treasury Management

Collections

The Request to Pay API is owned by BBVA, S.A.

Integrate collection requests into your processes

With the Request to Pay API, you can send payment requests from your own invoicing, recovery, or sales processes. This way, you will gain agility and efficiency in your collection processes.

Additionally, you will have full traceability of your payment requests at all times, and you will be able to know whether they have been accepted or rejected by the payer.

In practice

Issue up to 200 payment requests to different payers in a single API call.
Check your requests in real time, regardless of their status. In addition, you will have full traceability of the responses to your requests.
Automatically reconcile the payments received in your bank account through the request’s own reference.

Control

Your customer will have full visibility of the payment details and will be able to manage the request through their own bank.

Ease

The customer, whether businesses or individuals, can accept the payment request from their financial institution, according to the defined conditions: deadline, payment type, and amount.

Clarity

If the customer rejects the request, they can indicate the reason for rejection to the issuer.

Agility in managing your collections

Request to Pay complements the current catalogue of collection solutions with an immediate and digital product. Your payment request will be sent instantly to the payer.

Simplicity and control

Ease of reconciliation and traceability of operations. You can reconcile the credits in your account with the payment requests issued.

Greater security

It significantly reduces the risk of returns or refunds, as payments are received via payer-authorized transfers which, once executed, are irrevocable, providing greater certainty and finality of settlement.

How does it work?

1. Integrate the Request to Pay API

Configure your systems to call the Request to Pay API in those flows that require a payment request.

2. Make payment requests

You can include one or multiple payment requests (RTP) in a single call, which may be addressed to the same payer or to different payers, depending on your operational needs.

3. Consult the status of your requests

Use the Request to Pay API to consult the status of your issued requests.

4. Reconcile your payments

Use the Request to Pay API to check the requests that have been paid, accepted, or rejected. Additionally, you can reconcile the account credits with the requests to pay you have sent.

The Request to Pay API redefines the payment collection experience with full traceability, control, and agility for issuers and payers. A digital solution that simplifies payments and improves operational efficiency.

Miguel Díaz Díaz, Product Owner Enterprise Client Solutions

Other APIs you might be interested in

If the Request to Pay API has been useful to you, these options may also interest you:

Reconciliation

Combine Request to Pay with the Reconciliation API and reconcile issued payment requests and collections received in your account in real time.

More information

Business Payments

Complete the solution by incorporating the management of your payments with an API that allows you to make automated payments in both Euros and foreign currency.

More information

Validations

Verify the ownership of a bank account in real time, providing greater security to your payments and collections, and helping to reduce errors and operational risks.

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.

Request to Pay

Learn more about Request to Pay

Integrate collection requests into your processes

In practice