Migrating from v1 to v2 requires that you complete all configurations for v2. Please contact the Clock Customer Service team for assistance.
Important: Tokens (credit card details) stored with v1 cannot be used through v2.
Due to this, you can use both versions of the interface in combination until you have no more transactions that need to be made with a v1 token.
Please note that once you have configured the v2 interface and selected Adyen v2 as a payment service in your guarantee options, all modules (WRS, MyBooking Portal, Online Check-in, Kiosk) will use Adyen v2 for the transactions. The only situation where v1 will be used is when you need to manually operate with a credit card (token) that was saved with v1.
Operations where you need to use the v1 interface
The situations in which you need to use the v1 interface are:
- Charging a card (token) saved through v1.
- Refunding amounts charged through v1.
- Capturing or releasing a pre-authorization made through v1.
Which tokens are saved through v1 and which through v2?
When previewing the booking / company / event and the Credit Card section you can easily differentiate if the stored tokens are v1 or v2:
- v1 tokens will have the green Adyen logo on their right side - they can only be used through v1.
- credit card details that have blue/green/red credit card icon on their right side can only be processed through v2.
- depending on your channel manager mapping settings and specifically if you've set tokenization of cards not only storing, you will have the same card details stored twice in the booking. In such cases, you can directly use the card with the card icon next to it so that the operation goes through v2.
The card with the Adyen logo can be discarded as it can only be processed through v1.
Charging tokens through the correct version
When having both interfaces configured you will see two separate Credit card buttons in the folio:
- Credit card Payment will process trough v2 already stored tokens, manually added cards on the spot, or processing through the terminals.
- Credit card will process trough v1.
- Terminal is a v1 button and will be removed after migrating to v2.
Differentiating payments made from v1 and v2 in a folio and refunding
You can easily differentiate which payment is from which version by checking the payment section in the folio:
- v1 payments will have a 'Void' button on their right side. To refund such payment, you need to use the arrow in the 'Credit card' button and refund as you've done until now with v1.
- v2 payments will have a 'Refund' button on their right side which you can use to initiate a refund.
Once you have no need of Adyen v1 any longer you can remove the configuration from menu Settings->All settings->Adyen (Integrated Payments)-> deselect all the services. This will remove the v1 Credit card button from the folio.
Note: If you come across a v1 token which you need to operate with, you can select the services again and the v1 button will be available again in the folio. If you are completely sure that you no longer have v1 tokens to use, you can completely remove the v1 config.
Channel manager and v2
Once you have completed the configurations of Adyen v2 and have started using it, please make sure that in your channel manager settings/mapping - menu Settings->All Settings->your channel manager section - for all mappings you have 'Save credit card only' selected as a 'Deposit auto-payment' service. If you need to charge OTA bookings a deposit once the booking is imported you can create a task in the Payment Autopilot for it.
1. With Adyen v1, some actions with pre-authorizations could take a significant amount of time to complete (due to the system waiting for full confirmation by Adyen and the issuing bank) and this blocked your worked as you needed to wait for the transaction confirmation. With Adyen v2, we've included a new feature that will help with this. In the Adyen settings, you will see the field 'Quick capture auth age' in which you can enter a number of days.
The main thing to consider is that with this setting you define how much risk you are willing to take to speed up operations.
- Any amounts pre-authorized up to 7 days in the past will be processed without waiting for a response (which may take an indefinite amount of time - minutes, hours, etc.). If for some reason the transaction is declined later on (e.g. by the issuing bank) you will receive a ToDo message notifying you about his.
- For pre-authorized amounts older than 7 days, the current behavior, namely waiting for confirmation, is maintained.
In case you do not want to use the speculative mode of operation for both Capture pre-authorizations and direct payments, enter 0 for the value of the Quick capture auth age field. You will then need to wait for a response from the partner to complete all Capture operations.
2. With Adyen v1, alternative payment methods such as iDeal, Bancontact and many other were managed by what was known as Hosted Payment Page (HPP) and you had a completely separate merchant account dedicated specifically for those methods.
However, Adyen are deprecating the HPP functionality and are migrating those to a new module - DropIn.
To continue using the alternative payment methods, you no longer need a separate 'HPP' merchant account. You simply need to make sure that those alternative payment methods are active and enabled in the eCommerce/COM merchant account used for the connection (see image below). Furthermore, the DropIn functionality needs to be configured.
3. With Adyen v1 payments were posted with payment type 'Online' with sub-type being the card brand. With Adyen v2, this is changed and the payment type will be 'Card', sub-type remains being the card brand.
You are still able to use the 'Trough payment gateway only' button in the Payment Report which will show you payments from both versions.
Note: If you have an integration or export to an accounting system, you should have the above in consideration and possibly adjust the payment type mapping for that connection.
4. If you are using Adyen terminals in Standalone mode (not connected to Clock PMS+) in addition to the ones connected to our system, you need to make sure that they are in separate Adyen POS merchant accounts due to the capture delay setting.
For example, if you have currently 2 terminals connected and 1 standalone, they need to be in two separate Adyen POS merchant accounts (currently, they are most probably in 1 account) with the following POS capture delay settings:
- The merchant account that manages the terminals used by Clock PMS+ should have 'Capture delay' and 'POS capture delay' - Manual.
- The merchant account that manages the standalone terminal should have capture delay - Immediate.