Upcoming changes

Legend

info there is no concrete release date yet, please get in contact with us to get more details

soon these changes will be released within the next 2-4 weeks

next these changes will be released within the next days

List of Upcoming changes

Date

Description

Adjustments to API integration

Adjustments to business process 

soon

Adjustments for credit card handling, to meet new PCI-DSS requirements.

You should whitelist the domain https://sppf.secupay.com/ if your application is using the credit card checkout process. This new domain will replace https://cc.secupay.com/. All requests to the old domain will be redirected to the new one in the near future.


soon

Improve processing speed POST /Services/Identrequests

Improve processing speed POST /Payment/Contracts/{id}/requestId



soon

Improvements for Push-Service, to avoid postponed messages

Failed push messages will be send repeatedly in a longer interval, if it was failed multiple times (not every 5 minutes, like before).


Latest changes

Date

Description

Adjustments to API integration

Adjustments to business process 

 

Improved processing speed GET /Payment/Contracts/{id}



 

New product ids for "VISA Debit" and "Gutschrift VISA Debit"



 

Small improvements for Twint payments.



 

Fix for getAvailablePaymentMethods endpoint. On contracts with multiple currencies, the result was in some rare cases not correct.



 

Adjustments to avoid an unwanted (full) cancellation of a transaction.

This request will result in an error:

POST /Payment/Transactions/PCI_.../cancel 
{
    "reduce_amount_by": 0
}


If you want to cancel a transaction over the full amount you can still send:

POST /Payment/Transactions/PCI_.../cancel 
{
    "reduce_amount_by": null
}


 

Removed some old error codes.




2024

Date

Description

Adjustments to API integration

Adjustments to business process 

 

XRechnung integration

(no adjustments)

It's possible that we could send a structured electronic invoice in XML format, in addition or instead of the PDF.

 

New endpoint for deleting app configurations of terminals on device, store or merchant level.

DELETE Smart/Devices/SDV_.../appsConfig
{
}

or

DELETE Smart/Devices/my/appsConfig
{
    "merchant": "MRC_..."
}

or

DELETE Smart/Devices/my/appsConfig
{
    "store": "STO_..."
}


 

As a platform it is now possible to provide an additional verification document (file) when updating the bank account of a contract.

POST General/Contracts/GCR_.../updateBankAccount
{
    "owner": "Max Muster",
    "iban": "DE27...",
    "bic": "DE...",
    "verification_document": "DUP_..."
}


 

Integration of Pay by Bank (aiia) via Smart Transaction: https://openbankingeu.mastercard.com/use-cases/e-commerce/

 


 

Smart-ZVT timeout value was increased from 90 to 180 seconds.

 


 

Improvements for a faster sync process.

 


 

Adjustments for credit card handling, to meet new PCI-DSS requirements.

As of end of May 2024 you cannot create Payment Containers with type credit_card via POST
/Payment/Containers anymore. Your application needs to create these Payment Containers implicitly with POST /Smart/Transactions/{id}/prepare/creditcard.


 

Reporting feature for secuOffice.



 

Improvements in the push notification logic, to avoid delayed push notifications.



 

The endpoint GET /Payment/Transactions/{paymentTransactionId}/shippingUrl was removed, as it was not in use anymore.



 

Enabled the generation of CSV file for avis with more than 2000 entires.



 

New testing environment, to improve the stability for your tests.

The outgoing IP of the testing environment is now: 91.195.151.4

No change is needed, if you already accept the recommended range of IPs:

91.195.150.0 - 91.195.151.255


 

A new terminal app is available.



 

Improvements in the push notification logic, to avoid delayed push notifications.



 

Adjustments in handling input data of the endpoint POST Payment/Contracts/.../requestId



 

Adjustments for credit card handling, to meet new PCI-DSS requirements.



 

Improved Push-Notification system

 (The change is backward compatible)

  • It's possible to provide push notifications for Payment/Payouts objects.
  • It's possible to provide customized push notifications, which f.e. contains the changed data directly.
  • It's possible to setup different push urls (one for each object type).
  • It's possible to setup custom conditions, f.e. only push completed credit card transactions.

 

 Removed deprecated / unused endpoints in PublicWebsite.



 

The callback_urls parameter is now optional for the POST Smart/Transactions/STX_.../prepare/creditcard endpoint if payment_context.merchant_initiated is enabled.



 

Improved file type detection for the endpoint /Loyalty/transactions/DUP_.../BulkTransaction/MRC_...