We support many Additional Payment Methods (APMs) such as ApplePay, PayPal, AliPay, Sofort and PaySafe. A comprehensive list of supported APM’s is available from our website
We integrate with ACI ReD Shield which anticipates and responds to changing patterns of fraud ensuring Secure Trading’s merchants remain protected in all environments. You can find documents for Payment Pages, XML, and JSON on our website. Please contact your account manager for further details regarding this additional service.
Please refer to the Enabling PayPal document.
There is a fully integrated Re-Auth button that is available at the bottom of every transaction you have processed in MyST, allowing you to re-attempt another payment against that card.
|Please note: re-authorisations will not include the Security Code. You may be charged extra fees from your acquiring bank, please check with them before re-authorising!|
Yes, these features are fully supported.
These will be sent out by the support team once they’ve been set up after your contract has been signed with your account manager. Account Credentials are usually supplied within a 48-hour period.
Yes, you must send an email to [email protected] requesting for your account to be switched into live mode.
|Please note: this is only possible after you have received the email informing you that your merchant number has been successfully tested!|
3-D Secure is an additional layer of security that authenticates a customer during a transaction. It also affords you more protection against potential chargebacks.
Provided you are utilising the 3-D Secure system, you will be covered for the majority of fraudulent transactions that are processed and the liability for payment will shift back to the card issuer.
Secure Trading believes the liability shift to be as follows:
A= an attempt on something did not work with the communication
* Important note: If the brand is Visa and enrolled or status is returned as a “U” (Unknown), it means that the merchant is not covered by the 3-D Secure scheme. In this case the merchant is still liable for any fraudulent transactions.
** Important note: There are some cases where the liability is not covered by the card issuer; for example some commercial cards under both brands. For more information please contact your acquirer.
*** Important note: In this case it is strongly recommended that the transaction does not proceed. This means the password entered did not match.
This is a high level overview of the liability shift. Please bear in mind we facilitate the process; we do not create or enforce the rules. If you are unsure of any transaction status that you may see, we would recommend that you contact your acquirer.
The majority of Visa / Mastercard branded cards are covered by 3-D Secure, which does include some Commercial Cards. More information can be provided by your acquiring bank.
If you are using Payment Pages, 3-D Secure will be enabled automatically by ourselves. If you are using an API system and require 3-D Secure, you have to include the relevant XML for performing 3-D Secure requests or if you are using the JSON integration, please refer to the Online 3-D Secure documentation.
In most cases 3-D Secure is not mandatory, but is highly recommended. It is however compulsory when processing Maestro cards. Some acquiring banks require that you use 3-D Secure. Please check with your acquiring bank before making any decisions on this.
It is likely that the Site Reference quoted in your XML is not linked to your Web Services username, or the value you are passing for ALIAS in the XML is invalid (it must be the Web Services username).
The most likely cause of this would be incorrect credentials in your Web Services header, or you are using a username that is not setup as the Web Services role.
This is done within MyST. Please refer to the Rule Manager documentation for more information.
Yes, but this depends entirely on your acquirer. Please speak to support for more information.
You are currently processing on a test account; you will need to ensure you request for your main account to be switched live and that your code is pointing to the correct site reference.
EG: mycompany67890 instead of test_mycompany67891
You are trying to process a card type / currency / account type (ECOM / MOTO etc) that your account isn’t setup to process.
We support many shopping carts such as Magento, PrestaShop, WooCommerce and OpenCart. A list of supported shopping carts is available from our website.
If your account is live, and your transactions are settling as expected, please speak to your acquiring bank. If you are unsure of this, please call Support and we’ll point you in the right direction. You would need to speak to your acquiring bank to find out where they are paying the money into.