Identifiers
| Access to the payment gateway | |
|---|---|
| Shop ID | Indicate the 8-digit shop ID, available in your Merchant Back Office (Menu: Settings > Shop > Keys). |
| Test key | Specify the test key available via your Merchant Back Office (Menu: Settings > Shop > Keys). |
| Production key | Specify the production key available in your Merchant Back Office (Menu: Settings > Shop > Keys). Note that the production key will only become available after the test phase has been completed. |
| Signature algorithm | Algorithm used to compute the signature of the payment form. The algorithm must be the same as the one configured in the Merchant Back Office (Settings > Shop > Keys). If the algorithm is different, the parameter will have to be modified via the Merchant Back Office. |
| Instant Payment Notification URL | URL to copy in your Merchant Back Office (Settings > Notification rules > Instant Payment Notification URL at the end of the payment > Instant Payment Notification URL of the API form V1, V2 menu). For more information, see the chapter and the sub-chapters on Configuring the notification URL. |
| Payment page URL | This field is pre-populated by default: https://secure.osb.pf/vads-payment/ |
| Advanced options | |
|---|---|
| Card data entry mode | This parameter setting is described in the chapter on Choosing the integration type in the documentation. |
| Display in a pop-in | Select Yes to display embedded payment fields in a pop-up window. |
| Theme | Choose the theme you would like to use to display the embedded payment fields. |
| Compact mode | If your shop offers several payment methods, we recommend that you activate this setting for better legibility. All the payment methods offered by your shop will be compacted. |
| Payment attempts number | Maximum number of payment retries after a failed payment, this value must be between 0 and 9. If this value is not specified, the default value will be 3. |
| Payment page | |
|---|---|
| Default language | This option allows to choose the default language of the payment page in case the language of Odoo is not supported by PayZen by OSB. If the language(s) used by the Odoo is (are) implemented into PayZen by OSB, the payment page will be displayed in the language of Odoo when the buyer clicks on “Pay”. |
| Available languages | Allows to customize the language displayed on the payment page. The buyer will be able to select a language when he or she is redirected to the payment page. If you do not select any language, all languages will be displayed on the payment page. Available languages: German, English, Chinese, Spanish, French, Italian, Japanese, Dutch, Polish, Portuguese, Russian, Swedish, Turkish. |
| Capture delay | Indicates the delay (in days) before the capture. By default, this parameter can be configured in your Merchant Back Office. (Menu: Settings > Shop > Configuration - section: Capture delay). It is recommended to not populate this parameter. |
| Validation mode | Back Office configuration: Recommended value. Allows to use the configuration defined in the Merchant Back Office. (Menu: Settings > Shop > Configuration section: validation mode). Automatic: This value indicates that the payment will be captured in the bank automatically without any action on the merchant’s part. Manual: This value indicates that the transactions will require manual validation by the merchant via the Merchant Back Office. Warning: if the transaction is not validated by the merchant before the expiration date of the authorization request, it will never be captured in the bank. Remember to configure the Instant Payment Notification rule on an operation coming from the Back Office to update the order status in Odoo. |
| Card types | Select the payment methods you want to display on the payment page. Hold down the Ctrl key if you want to select multiple payment methods. The payment types offered to the buyer on the payment page depend on the contracts and options associated with your OSB offer. It is recommended not to select anything to display all payment methods compatible with your shop. |
| Custom 3DS | |
|---|---|
| Managing 3DS | Allows to request authentication without interaction (frictionless). Requires the Frictionless 3DS2 option. |
| Payment options | |
|---|---|
| Number | Number of installments: 3 for payment in 3 installments 4 for payment in 4 installments etc. |
| Period | Period (in days) between each installment. |
| First installment | Amount of the first installment, expressed as a percentage of the total amount. Example: For an amount of 10 000 XPF in 3 installments, you can set the percentage of the first payment at 50% of the amount. This means that the amount of the first installment will be 5 000 XPF an that the two others will be of 2 500 XPF. For 50% enter 50. If you want the amount of every installment to be the same, leave this field empty. |
| Return to shop | |
|---|---|
| Automatic redirection | This option allows to automatically redirect the buyer to the merchant website. This option depends on the following settings. This option is disabled by default. |
| Time before redirection (success) | If the automatic redirection option is enabled, you can define the delay in seconds before your buyer is redirected to your shop in case of a successful payment. |
| Message before redirection (success) | If the automatic redirection option is enabled, you can define the message that will appear on the screen following a successful payment before your buyer is redirected to the shop. The default message is: “Redirection to the shop in a moment”. |
| Time before redirection (failure) | If the automatic redirection option is enabled, you can define the delay in seconds before your buyer is redirected to your shop in case of a failed payment. |
| Message before redirection (failure) | If the automatic redirection option is enabled, you can define the message that will appear on the screen following a failed payment before your buyer is redirected to the shop. The default message is: “Redirection to the shop in a moment”. |
| Return mode | During the redirection to the shop, these parameters are returned to the shop in POST or GET modes. The POST mode is set by default. |
Once you have completed the configuration, click 