OpenCart

Select between "Test" or "Production" to link your shop to the respective environment. Depending on your selection, the shop module will send the transaction requests to the test or production environment.

Make sure to

• Not to mix up credentials from test with live and vice versa when configuring fields PSPID/API and webhooks credentials.
• To switch to "Production" as soon as you have finalised your tests.

Enables or disables the payment method on the checkout page.

Define the payment method name that will be displayed on the checkout page. Translation are available in all supported storefront languages.

Enter the file name of your template to adapt our payment page to the look and feel of your shop. To learn how to create templates, see our dedicated chapters in the Hosted Checkout Page guide.

Define whether to process the transactions as authorisation mode or as direct sale. Select one of the following options:

• Authorization & Capture: The amount has been ordered to be paid out in one go. Use this mode to receive the money before shipping the order. There are no further actions required to capture the transaction.
  Successful transactions will have status="CAPTURED" / statusOutput.statusCategory="COMPLETED" / statusOutput.statusCode=9
• Authorized (Authorization Only): The amount is only blocked on your customer's card. 
  Use this mode when you wish to capture a transaction only after shipping the order).
  Successful transactions will have statusCode=5/status="PENDING_CAPTURE" / statusOutput.statusCategory="PENDING_MERCHANT". 

If you select "Authorized", also configure the following:

• Delay before payment capture: You can set the capture delay of X days in the given field. At the end of this duration, a cron job will capture the transaction automatically. If the transaction is partially captured already in the meantime, any available funds that remain will be captured.
• Capture cronjob: Copy the cron command from the plugin and paste it in your osCommerce core for it to auto execute.

If transaction type is set to "Authorized", beware of the following:

• Make sure that you capture authorised transaction later. Only then will the transaction have status="CAPTURED" / statusOutput.statusCategory="COMPLETED" / statusOutput.statusCode=9, for which you receive the actual payment for the transaction.
• Even if the capture delay is set to X days, you can also manually capture funds fully / partially by opening an individual order once you have delivered the goods/services.

Define when to automatically capture authorised transactions. You can schedule the capture up to 5 days after authorisation.

Define the number of retry attempts for unsuccessful payments on the Hosted Checkout Page. You can configure up to 10 allowed attempts. Any attempt of payment after that will automatically be refused.

In some regions, you may apply a surcharge on credit card transactions. If enabled, our platform will automatically apply a surcharge.

If your account is not configured to accept surcharging, all your transactions will be blocked.

You can also configure different statuses for your order depending of the payment status:

• Payment accepted
• Payment error
• Pending payment
• Authorized payment
• Cancelled payment
• Refunded payment
• Partially refunded payment

Modify this mapping only if you are completely aware of how the order status flow works in your shop.

Enable this feature to log all outgoing API calls and all incoming responses from the API.

Defines how long your systems retain logs (default value: 10 days). We recommend keeping this value when you expect high traffic to ensure stable performance.

Create payment links via our PaymentLinks API which you can share via SMS or e-mail. You can use payment links to

• Allow customers to complete their payment for already shipped orders/abandoned cart orders.
• Create a new order in osCommerce Back Office.

Define the name of the Pay By Link payment method in the shop Back Office.

Define how long a payment link remains active (default value: 7 days).

Allowed range: 24hrs to 6 months.

Removes all plugin settings and redirects you to the user authorisation page, allowing you to connect a different account.

Define whether to enforce Strong Customer Authentication.

We strongly recommend enabling, as 3-D Secure is mandatory in some markets. This will also ensure liability shifts for transactions with successful 3-D Secure authentication. If you disable this option, you may not benefit from liability shifts and may be held liable.

Define whether to enforce Strong Customer Authentication, regardless of any possible applicable exemptions.

Some markets allow you to potentially exempt your customers from a 3-D Secure check. Define whether to request exemptions when the criteria are met.

A customer can receive up to five consecutive exemptions, with a cumulative total of EUR 150. The next transaction that exceeds these criteria will require Strong Customer Authentication (SCA).

Customise the radio button text displayed on the checkout page when a customer is presented a card that has previously been saved.

Defines the payment flow for credit card payments.

• iFrame: Your customers stay on your checkout page while entering their card details in an iframe hosted on our server.
• Redirect: Your customers confirm the order in your webshop checkout page. The plugin then redirects your customers to our Hosted Checkout Page for entering their card details.

Enable/Disable the Hosted Checkout Page "Group cards" feature.

• Enabled: Group all cards payment methods under one single button on the osCommerce checkout page.
  Upon clicking the button, your customers are redirected to the Hosted Checkout Page featuring a brand-agnostic payment form.
• Disabled: List all available card payment methods individually on the osCommerce checkout page.
  Upon clicking any button, your customers are redirected to the Hosted Checkout Page featuring a brand-specific payment form.

If you configure this in the "Credit cards" payment method, we advise to enable grouping the cards.

Your company logo appearing in the header of the Hosted Checkout Page. Allowed formats:

png
jpg
jpeg

Define the session timeout duration on the Hosted Checkout Page in minutes.

Define the specific brand for the Intersolve payment method. Find all possible values in the "Integration" chapter in the Intersolve guide.

If undefined, the default value is 5700.

Define whether to accept only instant transfers for Bank Transfer by Worldline payments.

Set up a cron job to make sure the plugin synchronises the transaction status with our platform. This is a fallback mechanism if the plugin does not retrieve the status correctly once a transaction is finalised.

Beware that the plugin provides only one value for both the test/live environment.

Define whether to process the transactions in authorisation mode or as direct sale. Select one of the following options:

• Pre Authorization: The amount is only blocked (=authorised) on your customer's card for 30 days. You can cancel the authorisation any time, both fully and partially. Supports both full and partial captures. Successful transactions will have status="PENDING_CAPTURE" / statusOutput.statusCategory="PENDING_MERCHANT" /
  statusOutput.statusCode=5. Use this mode when you wish to capture a transaction only after shipping the order.
  In the OpenCart module, the status will be "pending_capture".
• Final Authorization: The amount is only blocked (=authorised) on your customer's card for 7 days. . You can cancel the authorisation any time, but only fully. Successful transactions will have status="PENDING_CAPTURE" / statusOutput.statusCategory="PENDING_MERCHANT" /
  statusOutput.statusCode=5. Use this mode when you wish to capture a transaction only after shipping the order. In the OpenCart module, the status will be "pending_capture".
• Sale: The amount is blocked and paid out (=captured) in one go. Successful transactions will have status="CAPTURED" / statusOutput.statusCategory="PENDING_MERCHANT" /
  statusOutput.statusCode=9. In the OpenCart module, the status will be "captured".

If you select"Pre Authorization" or "Final Authorization", make sure you capture authorized transaction later. Only then will the transaction have statusOutput.statusCode=9/status "captured" in the module.

Configure the duration for auto capture. You can choose to capture manually or set a duration for auto capture. Mind that you need to setup a cronjob for this purpose on the respective environment as well.

Define whether to store your customers' card data for future Card On File payments:

• "Enabled": Create a token for every successful card transaction.
• "Disabled": Do not store the card data.

Confirm choices on whether you want to apply surcharge to your transactions.
Mind that the surcharge only applies to non-EU markets and requires configuring on your account.

(De)activate the 3-D Secure check.

We strongly recommend selecting "Enabled" as 3-D Secure is mandatory in some markets. This will also ensure liability shift for transactions with successful 3-D Secure authentication. If you select "Disabled" and choose to process non 3-D Secure transactions, you may not benefit from liability shift and may be held liable.

Define whether to conceal or skip 3-D Secure authentication whenever possible by default:

• No Preference: No preference for the frictionless/challenge flow.
• No Challenge Requested: Preference for the frictionless flow.
• Challenge Requested: Preference for the challenge flow.
• Challenge Required: You insist on the challenge flow.

Some markets allow you to potentially exempt your customers from a 3-D Secure check:

• No exemption flagging: You pass on any possible exemption.
• Transaction is of low risk: You can request an exemption for transactions you consider low risk. As the acquirer is liable, it decides to grant/reject an exemptions based on the overall portfolio of the transaction (transaction value, fraud rate).
• The value of the transaction is below 30 EUR: For purchases lower than €30. However, SCA will be necessary if a customer makes five transactions in a row or reaches a value of more than €100.
• Whitelisted by the customer: Your customers can request an exemption to their issuer to white-list you as a "trusted beneficiaries".

When debug logging is activated, additional details such as purchase amount, customer address, incoming webhook data, and HTTP requests/responses from the API are recorded.
Enable debug logs when troubleshooting issues and share these logs with the support team for effective resolution.

Define a minimum amount of the basket to make payments for this extension possible.

Geo Zone

Choose a specific geographical zone to make this extension available on your webshop checkout page

Sort Order

Specify the order in which the available payment methods are displayed in the "Payment Method" step on your webshop checkout page.

Customise the submit button text on your webshop checkout page.

Default value: "Place Order".

Customise the submit button text on your webshop checkout page.

Default value: "Place Order".