Full screen / Iframe Integration

1. Introduction
2. Integration for data capture
   1. Operation of the data capture (example)
   2. Methods of payment according to the integration
3. Parameters
   1. Execution of User Registration in the system (add_user)
   2. Execution of charge (User implicit registration in the system) (execute_purchase)
   3. Execution of subscription registration (User implicit registration in the system) (create_subscription)
   4. Execution of Preauthorization Registration (User implicit registration in the system) (create_preauthorization)
   5. Card validation and confirmation (User implicit registration in the system) (deferred_preauthorization)
   6. Execution of Charges to a user in the system with DCC (execute_purchase_dcc)

Introduction

The purpose of using an integration for capturing customer card data is to facilitate compliance with the PCI-DSS standard of the web application. So, the collection of banking data is done in the secure environment of Banco Sabadell and then treated in a Server2Server conversation without the risk of data theft.

Integration for data capture

This solution enables the generation of a form of data captura with the look&feel predefined in the product control panel. This solution must be activated by Banco Sabadell, so if it does not appear in the control panel, you must request it by opening an administrative ticket (Support → Notification of incidence → Administrative Department)

In this section you will be able to see a preview of the styles applied below. Styles allow reference to external sites but must respond with a digital certificate correctly signed by a trusted entity; otherwise the customer browser will display an error that will generate mistrust in your customer:

In the section on product configuration, just below the preview, you will find the parameters that can be modified from the panel:

These are parameterizable using CSS properties to fit the design of your application.

If the available properties do not meet the needs of the application, you may request a development of specific "Template" by opening an administrative ticket (Support → Notification of incidence → Administrative department).

We will inform you of the steps to be followed and the rules of said development.

The functionalities available in Bankstore IFRAME are

• Function: (add_user)
• Function: (execute_purchase)
• Function: (create_subscription)
• Function: (create_preauthorization)
• Function: (deferred_preauthorization)
• Function: (execute_purchase_dcc)

Said functionalities are those that involve the collection of the bank details of the customer. Subsequently, once the IDUSER and TOKENUSER data have been collected, XML and REST interfaces may be used to execute purchases, modify subscriptions, information of user card data, cancel subscriptions, etc...

Operation of the data capture (example)

The purpose of using an integration to capture customer card data is to facilitate compliance with the PCI-DSS standard of the Web application. In this manner, the collection of bank data is carried out in the Banco Sabadell secure environment for processing them later in a Server2Server conversation without risk of the data being susceptible to theft.

In a fictional environment we would find the following scenario:

A business with high recurrence wants to store the bank details of the customer to facilitate future purchases. The techniques for collecting their bank details are two:

• From their customer account. In their control panel they can modify their billing and shipping information and even their associated credit/debit card. Thus, at the end of the shopping cart, they will make the order payment with just one click.
• In the first purchase. The customer enters all their bank details in the final process of the cart and these will be stored for future purchases. In this way, storage is done in a "transparent" way when completing the order.

In the first case, the customer is authenticated on the e-commerce platform because it is a previously registered user. They login to their Control Panel and chose to add a credit/debit card to their account to make the payments. The business shows in an integrated way in their control panel an form to capture data and Banco Sabadell notifies the business of the result. The business stores the IDUSER and TOKENUSER data in the customer's account (they may have several, in order to have multiple cards), to subsequently make payments.

In the second case (storage on the first purchase), the customer places an order normally and when selecting the method of payment by credit/debit card, the bank details are requested to proceed to

Parameters

Execution of User Registration in the system

Function: (add_user)

This operation will register a new user in the system and make the appropriate notification.

Select the type of integration:

Execution of charge (User implicit registration in the system)

Function: (execute_purchase)

This operation will register a new user in the system and will perform the payment operation on that user. The result of the user registration and the payment operation will be notified.

Select the type of integration:

Execution of subscription registration (User implicit registration in the system)

Function: (create_subscription)

The registration of a subscription implies the registration of a user in the BankStore system of Banco Sabadell. This operation will register a new user in the system and will perform the operation of the first payment of the subscription. The result of the subscription shall be notified.

Select the type of integration:

Execution of Preauthorization Registration (User implicit registration in the system)

Function: (create_preauthorization)

This operation will register a new user in the system and perform the operation of preauthorization registration. The result of the user registration and the preauthorization operation shall be notified.

Select the type of integration:

Card validation and confirmation (User implicit registration in the system)

Function: (deferred_preauthorization)

This type of operation allows the merchant to validate if the card details entered are correct. In this validation, the authentication of the holder is carried out unless the business does not have a secure payment method (Type 13). To use it with REST, it is a question of calling preatuh to verify the card with the payment details and confirmpreauth to complete it, with the parameter deferred = 1 in both cases. To use it with GET you have to call deferred_preauthorization and deferred_preauthorization_confirm similarly.

Select the type of integration:

Execution of Charges to a user in the system with DCC

Function: (execute_purchase_dcc)

Select the type of integration: