Overview
The one-click feature allows you to simplify your returning clients’ checkout by reusing previously stored card information.
To correctly process your one-click transactions, you will be required to send HiPay two specific additional parameters during the tokenization process and the order process.
Firstly, the multi_use parameter during the tokenization process informs HiPay to store your client’s card data after the first transaction is authorized. Failing to send this parameter set to true would result in the card data being deleted after the first payment is processed, rendering the corresponding token useless for subsequent payments.
Secondly, during the order process, the one_click parameter informs HiPay of the payment use case you are using. The one_click parameter should be sent for every one-click transaction processed with the stored card data (token):
⇒ During the first payment, without this field set to true, HiPay will not know you are initiating a one-click payment and will initiate a recurring payment instead.
⇒ For subsequent payments, if this field is missing or set to false, HiPay will look for your client’s information in the “recurring” card data and will therefore not find it, thinking you are trying to initiate a recurring payment (meaning that the transaction would be treated as a recurring transaction MIT instead of One-Click).
Merchant Configuration
Ogone
In the Worldline / Ogone back office, the “CVC obligatoire” parameter should be unchecked for each card payment method. To uncheck this option, the Partnership team and the PayOPs team should contact Worldline:
⚠️ Removing this option WILL impact all the merchant’s payments, even those which are not processed in a one-click use case. ALL the merchant’s transactions will be CVC-free, including regular one-shot e-commerce transactions.
Consequently, it should be deactivated with caution and for selected merchants only. Additionally, the merchant needs to update their integration as specified hereafter.
PayOn
No specific requirements configuration-wise. The merchant just needs to update their integration as specified hereafter.
Merchant integration - Order
Initial Transaction
During this transaction, the client can grant you the right to store their card data. In this case, you need to inform HiPay that the card you are tokenizing will be stored and reused. This is done using the “multi_use” parameter set to 1 during the tokenization process.
Tokenize card data
/rest/v2/token call with the following parameters (with example values):
Returns:
Merchant action
Store the token for subsequent use. It should be easy to find when your client returns for new payments. You can also store the debit_agreement_id which will be returned by the Order API. This is equivalent to a card storage mandate and can be useful in case of support requests sent to HiPay.
Send an Order request to HiPay
/rest/v1/order call with the parameters described in the following documentation and adding the following parameter:
Subsequent transactions
During these transactions, the client can choose to reuse the cards they have stored on your site. Once they have chosen which card they want to reuse (if they have stored multiple cards), retrieve the corresponding token.
Send an Order request to HiPay
/rest/v1/order call with the parameters described in the following documentation and adding the following parameter:
Transactions on HiPay Console
HiPay Console allows you to see which transactions are one-click with the “one-click” field. This field:
- can be used in an extended search,
- can be displayed as a column in the search result,
- can be seen directly on the transaction information sheet.
Adding the one-click criterion in an advanced search
Adding the one-click column in the search result
Finding the one-click criterion on the transaction information sheet
