GMS: Release notes 10-07-2025

This week we have released a few improvements:

• Service:GetConfig we have added a few data items to the output of this API
  • For each checkoutOption we now return an id. This ID reflects the ID that can be used to start a payment. If for Online Card payments (CNP) and for Vouchers/Giftcards in the sales location grouping is enabled, the 'generic' creditcard or voucher/giftcard ID is returned. If grouping is not enabled then we return the ID of the payment method;
  • For each checkoutOption we also a returning a smartGrouping flag and for each paymentMethod in the checkoutOption we return a targetCountries list. The idea is that if the payer originates from e.g. Danmark and for the Online Card payments (CNP) payment methods smartGrouping is enabled, you can check if there is a payment method specific for Denmark and show this as 'seperate' payment method in you checkout page, before showing the other CNP payment methods (grouped) in your checkout.
• The Transaction:Info now returns in the paymentMethod object also the terminalCodeif the transaction is an in-person card payment, so that you have a reference on which terminal this transaction is executed.

We have also created new endpoints to set invoice and clearing settings on the merchant and added these settings to the Merchants:Info endpoint. The following settings are available:

• clearingPeriod; possible options are DAY, WEEK, MONTH and indicates how transactions are grouped on your clearing. By default they are grouped per month. If grouped by WEEK and there is a change of month two clearings will be generated that week. If grouped by DAY a clearing will generated every day;
• clearingFrequency; possible options are MANUAL, DAY, WEEK, MONTH. We check every DAY, WEEK, MONTH if there are funds that needs to be cleared. If that is the case we will do a settlement to the clearing bank account. If MANUAL is configured we will not check automatically if we need to clear funds and we expect you to use addClearing endpoints to clear funds to the clearing bankaccount.
• clearingMoment; possible options are DIRECT or COLLECT. Each payment method has a so-called release period. These release periods are defined in payout scheme's. Depending on factors such as your relationship with PAY, transaction history, payment mix, and the company’s service level (e.g., few chargebacks and disputes), a higher payout speed can be applied. DIRECT means that the funds will be cleared as soon as the revenue has been released. COLLECT means that the funds will be cleared as soon as the revenue from the clearing period has been released.
• invoicePeriod; possible options are WEEK or MONTH. Transaction costs and/or other fees will be grouped per MONTH or per WEEK;
• invoiceFrequency; possible options are WEEK or MONTH. We will send an invoice (or will settle the invoice with your balance) every WEEK or MONTH;
• settlementPerClearing; indicates if every clearing results in a separate settlement on the clearing account;
• splitByTurnoverGroup; indicates if we need to spilt the clearing by turnovergroup. For each turnovergroup a different clearing will be generated;
• mt940;
  • change the MT940 bankaccount in the MT940 file;
  • change the headers in the MT940 file; possible options are STANDARD, CUSTOM or TWINFIELD. If CUSTOM is defined then the custom headers configured are returned.

With the Merchant:Info endpoint a settings object is available which returns these settings. With the Merchant:UpdateSettings endpoint these settings can be set.

📘

Note; depending on your rights you can set and retrieve these clearing and invoice settings