OpenCart

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”.