- STATUS: ACTIVE

- COMPATIBLE VERSION: 4.0


1. HOW DOES THE INTEGRATION BETWEEN REDSYS AND REVO WORK?
2. HOW TO CREATE A VIRTUAL POS
3. HOW TO TRANSFER THE VIRTUAL POS FROM TESTING TO PRODUCTION
4. CONSIDERATIONS TO KEEP IN MIND WITH THE BANK
5. REVO SOLO
5.1 HOW TO CONFIGURE THE REDSYS PAYMENT GATEWAY FOR REVO SOLO
5.2 RETURN POLICY AND PRIVACY POLICY IN REVO SOLO
6. REVO SOLO XPRESS
6.1 HOW TO CONFIGURE THE REDSYS PAYMENT GATEWAY FOR REVO XPRESS


Redsys is a virtual payment platform that supports payments from credit and debit cards, acting as an intermediary between the buyer and the bank associated with an online store, enabling any business to receive payments quickly and easily.


1. HOW DOES THE INTEGRATION BETWEEN REDSYS AND REVO WORK?

Redsys "transports" money from the End User's account to the bank account of the Establishment. Once the Redsys account is configured and integrated with Revo, payments will be automated and recorded in Revo.


2. HOW TO CREATE A VIRTUAL POS

We will get in touch with the bank manager and request that they manage the creation of a Virtual POS with Redsys PSP. Additionally, we will request that in the Allowed inSite Domains field, the following URLs be included for the payment gateway to function correctly.

These URLs must be written exactly as they appear here:

  • https://{tenant}.revosolo.works
  • https://xpress.revo.works
  • https://revoxpress.works
  • https://revoflow.works

IMPORTANT: Soon these URLs will no longer be operational:

  • https://solo.revointouch.works
  • https://revointouch.works
  • https://{tenant}.solo.revointouch.works
  • https://{tenant}.revointouch.works

IMPORTANT:

The URL to access the Revo SOLO back-office is: https://revosolo.works

  • The inSite Domain URL should be requested based on how the QR codes for Revo SOLO are generated. This is related to how access to the back office is made and QR codes are created, as they take the domain used to enter the back office.



    In this image, you can see that the tenant is revosupport.

  • If the client's financial institution does not allow adding more than one URL in inSite Domains, a Virtual POS (Point of Sale) should be requested for each of the contracted REVO apps (e.g., Revo SOLO and Revo XPRESS).

  • If QR codes have already been generated with old URLs, the old URLs will continue to function. This change will only affect new accounts and orders generated at the moment, not those via the QR code.

  • We recommend that when making a request to the bank, a link to an XPRESS QR code is included so that the team validating the bank's information has access to these links. To do this:

    • Open a table in Revo XEF; this table should remain open until the bank can review the link, so we recommend it be a virtual table.

    • Add a product and finally copy the XPRESS link to provide to the bank.




Once the Virtual POS has been created, we will receive a welcome email from soportevirtual@redsys.es with instructions to configure your Virtual POS.



Next, on the same day or a day later, you will receive a letter from YOUR BANK similar to this one. It is noteworthy that the establishment must have defined in these documents: the Return Policy (cancellation of orders, returns, and refunds) and the Privacy Policy (Security Protection for buyers, Shipments, privacy, and data protection).

These policies should be uploaded to the Revo SOLO back office, and how to do this will be explained later.



Next, we will need to access the website provided to us with the relevant credentials and go to:

  • Administration > Commerce



Once inside, the following screen will appear:



We will click on search, and the establishment(s) we have will be displayed.



To access the Virtual POS, we need to go to the icon, and we can see the visualization of the Virtual POS.



Once inside, we need to ensure that in the Allowed inSite Domains field, it has the URLs we indicated earlier, and in the Send parameters in URLs field, we will need to change it to YES, without showing Redsys receipt.

Once we have verified that everything is correct, we need to save the merchant management number, terminal number, and finally, the signature key, which we will obtain by clicking View Signature Key.


3. HOW TO TRANSFER THE VIRTUAL POS FROM TESTING TO PRODUCTION

Once payment tests have been conducted and confirmed to be functioning correctly, we proceed with the request for the Production Virtual POS.

To do this, we need to access the Virtual POS testing website with our credentials and go to:

  • Administration > Commerce



We click on search, and the establishment(s) we have will be displayed:



To access the Virtual POS, we need to go to the icon. And we click on Move to Production.



We should receive an email from canales@redsys.es like this one with keys that the platform will request from us to move to production.



Once our website has been successfully validated, we will receive an email from canales@redsys.es with instructions to configure our Virtual POS in the real environment. Follow each step as indicated.



As in the testing environment, we need to make sure that in the Allowed inSite Domains field, it has the URLs we indicated earlier, and in the Send parameters in URLs field, we need to change it to YES, without showing Redsys receipt.

Once we have verified that everything is correct, we need to save the merchant management number, terminal number, and finally, the signature key, which we will obtain by clicking View Signature Key.

IMPORTANT: Check if the New Signature Key is the one we already have in the Redsys Payment Gateway configuration for Revo SOLO. If not, it should be changed to the new one.


4. CONSIDERATIONS TO TAKE INTO ACCOUNT WITH THE BANK

1. Modify security policy

Modification of security filters, depending on the needs of the establishment and the type of product, it may be necessary to change the security parameters:

Max. card operations per day (Standard=3)

New max. operations: 15

Max. IP operations per day (Standard=3)

New max. operations: 15

Max. card amount per day (Standard=€1000)

New max. amount: €1500

Max. IP amount per day (Standard=€1000)

New max. amount: €1500

Card country<>Spain and Card country<>IP country

New value: ALLOW / NOT ALLOW


2. Restaurant business Delivery or Pickup in-store

Communication is direct between the payment gateway and the customer. So, the origin @IP is that of each customer. If a customer is going to make more than 3 operations a day, consider the aforementioned limitations.

In case the restaurant shares Wi-Fi with its customers on-site, consider the limit of operations per IP and per day, following what was mentioned earlier.


3. International cards

It must be communicated to the bank that it must allow the use of non-national cards.


4. Registering the card for future payments

The bank must allow saving the card for future cases in the terminal's APP. If not done this way, errors may occur.

In the commerce profile, non-face-to-face payments must be active, necessary to store the cards. Request that they go to the manager to activate it.

Notes: If it does not allow you to save the card, ask the bank to activate the option: Tokenization Operation.


5. Apple Pay / Google Pay

Clients of the Redsys TPV Virtual gateway must request their banking entity to make Apple Pay / Google Pay available on the payment gateway.

The information needed by the bank is as follows:

Id.Commerce Apple Pay: merchant.com.redsys.revointouch

Apple Pay Private Key: attached certificate

Notes:
1. The private key is included in the certificate (ecckey_pkcs8.key). Instructions following the Redsys Apple Pay Manual / on page 6, point 2 says: The content of the resulting file ecckey_pkcs8.key must be entered, together with the merchantld, in the administration portal of the TPV Virtual.
2. It should also be considered that in the transaction, the merchant information appears as: Commerce Revo

If the bank does not allow it, in the back office there is the possibility to disable Apple Pay and Google Pay.


5. REVO SOLO


5.1 HOW TO CONFIGURE THE REDSYS PAYMENT GATEWAY FOR REVO SOLO

Note: Previously, Revo SOLO must be correctly configured.

1. Access the back office of Revo SOLO.

2. Click on Configuration / Payment Gateways.

3. Click on +New.

4. Fill in the following information:



  • Name: Identifying name of the payment gateway.

  • Test: While conducting tests in the Redsys test environment, we should keep it active. Once we move to production, we should deactivate it.

  • Default: Enabled.

  • Type: Redsys.

  • Merchant Identification: Merchant management number.

  • Terminal: Terminal number.

  • Merchant Code Redsys: Signature key.

5. Click Save to confirm the changes.

Note: Once all the data for the Redsys payment gateway has been entered, it is necessary to assign the gateway to your establishment. More information here.


5.2 RETURN POLICY and PRIVACY POLICY REVO SOLO

1. Access the back office of Revo SOLO.

2. Click on Establishments.

3. Add the return policy to the establishment and save.



4. Click on Configuration / Legal Documents.

5. Add the privacy policy and save.



6. REVO SOLO XPRESS


6.1 HOW TO CONFIGURE THE REDSYS PAYMENT GATEWAY FOR REVO SOLO XPRESS

1. Access the back office of Revo XEF.

2. Click on Integrations.

3. From the Add button, search for XPress.

4. Click on Add to add the integration.



5. Fill in the following information:



  • Active:

  • Name: Identifying name of the integration.

  • Test: <

i class="fa fa-toggle-off" aria-hidden="true"> Disabled.

  • Solo XPress message: The text displayed below the XPress QR Code.

  • Payment methods: Select the available payment methods.

  • Payment method: Select the XPress payment method.

  • Redsys Merchant Code: Merchant number provided by the bank.

  • Redsys Merchant Key: Secret encryption key provided by the bank.

  • Redsys Merchant Terminal: Terminal number provided by the bank.

6. Click Save to confirm the changes.

7. Click on the to upload the return and privacy policy.





8. Click Update to confirm the changes.