Yes, it is possible to disable Second Chance through the dedicated API. This can be done in the transaction request when you create an order, by using the value false instead of true.
The XML API is deprecated and succeeded by the JSON API
The XML endpoint can still be used to process transaction requests. However, new payment methods, features and tools will only be supported by using the JSON API.
There are no plans to phase out the XML integration at this point, but this might change in the foreseeable future.
An API key is required to successfully establish a connection between your website and the MultiSafepay services.
Currently an API key can only be requested when a website URL is inputted into the backend of the MultiSafepay interface. Thus, an API key will only be generated as long as the field contains the URL of your website. Only then will it be possible to process data and payments.
It is …
It is possible to track the behavior of your customers through Google Universal Analytics tracking
However, this is restricted only to direct orders. If a customer reaches the MultiSafepay payment page, the UA-code will be loaded and you will be able to see that in the corresponding HTML.
For redirected orders (e.g. iDEAL redirect, some cases of Klarna, Afterpay, etc.), there is NO tracking …
Our notifications are webhooks whereby our API will notify your web server when the status of a transaction changes.
The notification webhooks are triggered by events made by both your customers (e.g. completing a payment) and you (e.g. creating a refund).
We will add 2 parameters to the notification:
MultiSafepay will always call the notification_url …
A locale is a set of parameters that defines the user’s language, region and any special variant preferences that the user wants to see in their user interface. Usually a locale identifier consists of at least a language code and a country/region code (e.g. en_US). A locale can be included to provide localized payment pages for the customer. Use the format ab_CD with ISO 639 language codes …
On our API section, you will often see the terms ‘Direct’ and ‘Redirect’ being used. In this section, we will explain the difference between the two API calls.
A Direct transaction will simply connect you directly to the chosen payment method and will either provide a direct link to the payment method or perform the transaction immediately without the customer …
On API level, this is illustrated as:
"status": "", "financial_status": "",
The status is related status of the webshop order. In your MultiSafepay Control, this is referred to as the Order Status.
The financial status is related to the payout of of the transaction. In your MultiSafepay Control, this is referred to as the Status.
As online payment provider, MultiSafepay is obliged by law to monitor transactions and it’s clients. As a result, it must be clear to MultiSafepay what type of service or products are purchased per transaction and by whom.
Please help us in our duty by sending:
for all orders automatically. Failure of sending the …
Post-payment and credit card payment methods require the customer ip_address to be validated and thus, we need the actual IP address of the end user within the ip_address field. This means that the optional parameter “ip_address (optional) within the JSON request is now a “required” field when processing post-payment and/or credit card transactions.
Please note! …