MOGU offers several options for processing online payments: its own integrated Stripe gateway and the agency's virtual POS connection. Each option has different advantages that you should take into account. Both options can be activated at the same time. Here are the details.
If you have opted for the option of connecting your own POS, in this article we tell you the 5 steps you have to follow to set it up.
Step 1: Contact your bank
First of all, for the virtual POS to work correctly you must have the following configuration:
In-site integration: this is so that when the user wants to pay, he is not taken to a new window, but the whole experience is within your MOGU proposal. Therefore, you will have to give permission to the domain where your proposals are hosted, which can be the one offered by the default tool: "tours.moguplatform.com" or the one you have configured, for example, "viajes.tuagencia.com".
COF option activated: this will allow you to use the POS to charge through payment schedules, that is to say, to proceed to the automatic collection of the amount without the customer having to pay it expressly. To do this, the bank must activate this option. If you do not activate it, you will be able to use all the payment collection functionalities except the payment schedules (if you have also connected the Stripe payment gateway, this could be used for the payment schedules and your own POS for the rest of the movements).
Taking into account these requirements, two cases can occur:
Option A: You already have your Virtual POS
You will need to write to your bank to make sure that the POS you are already using meets the above requirements. To make the query, you can copy and paste this text we have prepared:
Hello, I am X, from X. My business number is: XI am writing because I am going to connect my virtual POS to a payment management tool and I would like to make sure that it has the necessary configuration:
That it can be integrated in "In-site" mode. In this case it would have to be for the domain in production "tours.moguplatform.com" or "viajes.tuagencia.com" and for the domain in development "beta.moguplatform.com" (for testing).
At the same time the virtual POS must have the COF option activated so that it can transact without the participation of the owner.
In case it is necessary to test the POS first, I would appreciate if you can share with me again the development keys to have them at hand.
Thank you very much in advance for the information, best regards.
Option B: You do not have a Virtual POS yet
You will have to request the registration of a virtual POS to your bank that meets these requirements. To do so, you can copy and paste this text we have prepared:
Hello, I am X, from X. I am going to start using a payment management tool and I would like to register a Virtual POS. It must comply with a specific configuration:
That it can be integrated in the "In-site" mode. In this case it would have to be for the domain in production "tours.moguplatform.com" or "viajes.tuagencia.com" and for the domain in development "sandbox.moguplatform.com" (for testing purposes).
At the same time the virtual POS must have the COF option activated so that it can transact without the participation of the owner.
In case it is necessary to test the POS first, I would appreciate if you could share with me the development keys to have them at hand, thank you very much in advance for the information, best regards.
Step 2: Contact Redsys
If you were already using the virtual POS to charge online, you will already have your production keys and you will have activated it correctly in the Redsys administration panel, so you can go directly to step 3.
If, on the other hand, you have just requested it or you did it at the time but you have not finished configuring it, you will have to contact Redsys to request your production keys and activate it in your administration panel. Let's take a look at it.
Have at hand the data of your POS that the bank shared with you when you registered it. They are:
Trade name: TU AGENCIA S.L. (for example)
Merchant Number: 2863843 (for example)
Terminal number: 001 (for example)
With this information write to the redsys email: canales@redsys.es, with subject "Request REAL environment keys #Trade number". You can copy and paste this information changing the data.
Hello, I am Sara, I would like to request the production keys for this virtual POS:
- Trade name:
- Trade number:
- Terminal number:
Thank you very much.
(In case your bank asks you to perform an internal test in a test environment, you can do it from https://sandbox.moguplatform.com/ to make sure that everything is configured correctly).
Step 3: Login to your administration panel
Redsys will reply to this email giving you instructions on how to access your production keys in the administration panel. Here is a summary:
Access the REAL (PRODUCTION) environment administration panel from this link: https://canales.redsys.es/portal. Click on "I forgot my password". You will be asked for a user and you will have to enter the one that Redsys gives you in the email. With that, you will receive in your email the password to access the administration panel.
Open https://canales.redsys.es/portal again and log in with the password you received. Once inside, let's look for the production key. To do this, follow these steps:
Select the option "Trades", inside there, click on "View Signature Key". Indicate again the password with which you have accessed the administration panel and click on "Show Key". The secret encryption key will be displayed for a few seconds. Keep it.
Step 4: Add that key in MOGU
In this last step you only need to add your POS data and your production key. Fill in these details from Settings > Payment settings > Redsys.
Step 5: Final test
Test in production environment
This test will be performed by you in a production environment.
If you complete all these steps, you will have successfully integrated your Virtual POS. Hurray!