Background

In November 2024, secupay AG obtained principal membership for Visa and Mastercard for credit card acquiring services. This enables us to offer our customers services that are better tailored to their needs. In order to benefit from the changes, the service must be converted to the new acquiring model and, depending on the scope of functions, the technical connection must also be adapted. We will involve you in this process in good time and to the extent necessary.

The following is only relevant for credit card payments.

Smart Checkout or Custom Checkout

It is not necessary to change the checkout for it to continue functioning, except in combination with recurring payment, subscriptions, or one-click payment. Even when the contract is transferred without any technical change you will likely benefit from better authorization rates and less card abandonment.

Credit Card Iframe Integration

In case you have implemented a custom checkout, and you want to switch to the sandbox for development or testing purposes, you must also switch the credit card iframe URL now:

Livesystem

https://sppf.secupay.com/
(Legacy: https://cc.secupay.com/)

Sandbox

https://spp-sandbox.secuconnect.com/

Demo Transactions

Beginning with secupay Acquiring, demo mode transactions are no longer available.

Currently you can create both, demo and live transactions, on both environments, sandbox and live. In future, there will be no demo transaction mode, but only sandbox and live environments.

Dynamic Descriptors

The following would have no effect when applied to subscription payments.

Dynamic descriptors can be used to pass a DBA (“doing business as”) name and local address instead of the legal name and registration address. A DBA can be a trademark or store name that is better understandable by the card holders when checking their card or bank statements, and can lead to fewer chargebacks. This works only with credit card payment together with the new acquiring by secupay.

Please note that you must only use DBA names and addresses to which you have a legitimate claim.

The dynamic descriptor can be passed when creating the Smart Transaction that is used to control the checkout process. It needs to be inserted in the payment context of the Smart Transaction details:

Excerpt from Request Body
POST /api/v2/Smart/Transactions HTTP/1.1
Host: connect-testing.secuconnect.com
...
 
{
// ...
"payment_context": {
// ...
"dynamic_descriptor": {
"merchant_name": "ACME Buero-Paradies",
"merchant_city": "Bielefeld"
}
}
}

See your full example for Smart Checkout at:

Or for your custom checkout solution at: