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 

 

Apple Pay: Migration to Payment Platform Integrator ID

The Payment Platform Integrator ID gives a simpler, more flexible way to manage integration with Apple Pay. It replaces the previous allowlisted Merchant ID model with self-service tooling, non-expiring domain verification files, and full compatibility with the Web Merchant Registration API.

The migration is designed to be completely seamless, with no downtime expected. Your existing identifier remains unchanged, and payment processing continues uninterrupted throughout the migration.

However, you will need to update the Apple Pay domain verification file on any pages you host. We will publish the new file in your integration guide and also send it to existing merchants who processed an Apple Pay payment within the last three months.

Because the new "Apple Pay Platform Integrator Identity Certificate" has an expiry date, you will need to replace the domain verification file once a year.


info

GooglePay Integration via secupay acquiring.

New google pay settings:

const tokenizationSpecification = {
type: 'PAYMENT_GATEWAY',
parameters: {
'gateway': 'secupay',
'gatewayMerchantId': 'GCR_...'
}
};



next

Google Pay and Apple Pay needs to be activated via contract to be available via pay.secupay.com checkout.


https://developer.secuconnect.com/integration/Google_PayTM_Integration_Checklist.html

The Payment method "Google Pay" and "Apple Pay" will not be active by default on pay.secupay.com - you will need to enable this via customer support.

Latest changes

Date

Description

Adjustments to API integration

Adjustments to business process 

 

Click To Pay (C2P) Integration for secupay Issuing.

New endpoints to activate or disable C2P for secupay credit cards are available.


 

Removed the eGoods functionality from the API

The old eGoods endpoints are removed or read-only now:

  • Prepaid/Contracts
  • Prepaid/Itemgroups
  • Prepaid/Items
  • Prepaid/Reports
  • Prepaid/Sales

Effective March 31, 2026, secupay AG will discontinue the eGoods product line. As a result, gift card activation (e.g., Zalando, Amazon) and the sale of PIN-printing products will no longer be available directly via API.

Merchants who currently use these functions will need to adjust their operational processes accordingly.

  

DELETE Payment Containers (and Customer) return one object wrapped in an array which is not wanted.

No adjustments needed if you are using the secuconnect SDK.


 

New endpoints to process huge payouts faster and more reliably.

Imlement the new endpoints:

  • POST /payment/secupaypayout/me/initializePayout
  • POST /payment/secupaypayout/PCI_.../attachPayoutItem
  • POST /payment/secupaypayout/PCI_.../completePayout


 

New mapping for requestId endpoint for crowd onboarding process.

Depending on your contract settings you will need to submit additional fields like "funding_threshold" or "project_brochure" for onboarding new project on your crowdfunding / -investing plattform.


 

Use new Smart Checkout without checkout_template.

When a Smart Transaction is created without a checkout_template, the default template (COT_WD0DE66HN2XWJHW8JM88003YG0NEA2) is used as a fallback, instead of calling the old Smart Checkout, which is end of life.


2026

Date

Description

Adjustments to API integration

Adjustments to business process 

 

The merchantRef parameter is now explicitly cast as a string if it was passed as an integer.



 

New implementation of Mastercard "Pay by Bank".

A new payment method mc_pay_by_bank will become available in the Smart Transaction endpoints.

Please contact us if you are interested in using this payment method.

 

Adjustment in the Smart/Transactions endpoint: if the credit card token is no longer valid, no iframe_url is returned.



 

Return PCI-ID in POST /Payment/Secupaypayout/me/PayoutWithoutCustomer

The request POST /api/v2/Payment/Secupaypayout/me/PayoutWithoutCustomer returns the PCI-ID (id) for the payout transaction (in addition to trans_id).


 

We allow platform API users to retrieve project invoices using the existing GET /api/v2/Payment/Invoices Endpoint.



 

Extend requestId endpoint (and create GET General Contracts Endpoint) for event details

The RequestId endpoint has some new fields:

POST /api/v2/Payment/Contracts/{Master_GCR_ID}/requestId
{
"event_details": {
"event_date": "2026-05-01",
"event_description": "Dynamo - Aue"
},
...
}


It's now also possible to add new contracts to existing merchants:

POST /api/v2/Payment/Contracts/{Master_GCR_ID}/requestId
{
"merchant_id": "MRC_id",
"event_details": {
"event_date": "2026-05-01",
"event_description": "Dynamo - Aue"
},
...
}


In the GET endpoint you will receive the new fields too:

GET /api/v2/General/Contracts/{GCR_ID}
 
{
"object": "general.contracts",
"id": "GCR_2H69XY35227V2VKP9WRA3SJ0W95RP0",
...
"event_details": {
"event_date": "2026-05-01",
"event_description": "Dynamo - Aue"
}
}



 

A new TLS/SSL certificate has been registered for our domains.

We have switched from a DV certificate to an OV certificate.

As the root certificate remains unchanged, we do not expect any issues and no further actions are needed on your side.


 

We added the support for individual payout dates for ticketing/future business sector. For this purpose, transactions will be paid out in staggered installments based on a defined distance to the event date.


Please contact us if you are interested in this business model.