• Added support for Klarna Extra Merchant Data. We have added the field klarnaMerchantData to the optimize input on the Order:Create API. We pass any data in that field through to Klarna as extra merchant data. For more information about Klarna Extra Merchant Data please visit https://developer.pay.nl/docs/klarna#/
• Added support for the sl_SI locale in the creditcard payment screen
• Updated the required input for the DirectDebit payment method:
  • The firstName and lastName fields are now optional.
  • Added new required field accountHolder.
  • For backwards compatibility the firstName and lastName are used as the accountHolder when the accountHolder field was left empty.
• Fixed an issue where payments for payment methods requiring user input would expire too soon.
• PayPal: We will now deny all PayPal payments of the type ECHECK. We have seen many cases where this leads to fraud due to the check never being paid. To protect our merchants we will not allow these types of payments anymore.

• Add support for the Voucher:Create API (See https://developer.pay.nl/reference/post_vouchers-transaction)
• Added Klarna Debit Risk
• Added new status: In transit. This state was added to indicate the payment was successful, but the funds have not been received yet. This is mainly used for high-risk payment methods where we wait until we receive the money before actually marking the payment as paid.
• Bank transfer: Added several languages to the payment page: Danish, Swedish, Portugese, Polish, Romanian, Czech, Hungarian and Bulgarian.
• Fix edge-case where the captureAmount API would respond with a success while no amount was actually captured

• Creditcard: Added support for tokenisation for recurring creditcard payments
• Riverty: Orders rejected by riverty will now correctly get the denied status
• Fixed orders not going to status captured when we receive a successful payment notification when the order has status aborted
• Giftcards: Updated the error message when customers submit the form with only the card prefix filled in.
• De Cadeaukaart: Updated the header image
• Beauty and More: Updated the header image

We have added several new payment methods:

Twint

Twint is a mobile payment app widely used in Switzerland, designed for everyday payments in stores, online, and between individuals.

To read more click here.

Swish

Swish is a Swedish real-time mobile payment system that connects to users' bank accounts and uses BankID for secure, instant transfers between individuals and businesses.

To read more click here.

Bizum

Bizum is a mobile payment solution widely used in Spain, designed to enable instant money transfers between users and businesses through mobile phone numbers.

To read more click here.

Satispay

Satispay is a mobile payment platform originating from Italy, that allows users to make payments directly from their bank accounts via IBAN, independent of card networks.

To read more click here.

Vipps

Vipps is a Norwegian mobile payment app that facilitates peer-to-peer and business payments using phone numbers, secured by BankID, and is central to Norway’s cashless transition.

To read more click here.

We have released new version since the last POS.SDK. Make sure to update to the latest version for the newest features and bugfixes!

• Android softpos: v0.0.83
• Sunmi hardpos: v0.0.18
• PAX hardpos: v0.0.8
• iOS Tap to pay on iPhone: v0.0.23
• React Native: v0.0.49

NOTE: the SDK is still in active development, so if you encounter an issue, please contact PayNL support!

Documentation: https://github.com/paynl/POS.SDK

New features

• Added support for printing tickets! (supported on Sunmi softpos printers or the build-in hardpos printers)
• Added support for MIFARE classic cards (documentation)
• Added support for Merchant Approved Transactions (offline processing)

Bugfixes

• fixed issues where the PIN prompt was not shown on dual screen devices
• fixed issues where the Android softpos SDK did not initialize correctly
• fixed issues where the Sunmi P terminal did not want to keyload
• Several small fixes to prevent app crashes

MB Way is now available to use. It is Portugal’s leading mobile payment app, developed by SIBS, the operator behind the country’s Multibanco system. It allows users to link their bank cards and make peer-to-peer transfers, online payments using virtual cards, in-store purchases via QR or NFC, and even ATM withdrawals without a physical card.

With over 3.5 million users and around 45% of Portuguese e-commerce transactions, MB Way is deeply embedded in the country’s payment ecosystem. It’s widely accepted across banks, retailers, toll systems, and more.

The app is known for its ease of use, strong security, and popularity among young people. It supports up to eight bank cards and is expanding internationally through the European Payments Initiative.

We released a few small improvements:

• The Service:GetConfig API now returns a publication object with a domainUrl; which reflects the configured URL on service / saleslocation level;
• The DirectDebit:Get and DirectDebits:Browse API now returns a decline object if the direct debit transaction is not successfully executed with more detailed information. A description can be found here; https://developer.pay.nl/docs/transaction-statuses#direct-debits-statuses.

• PayByBank: Fixed a problem where the country dropdown would not contain all available countries.
• Creditcard: Added the missing creditcard object in the payment data when using the legacy /v1/transactions API endpoint.
• Resolved an error processing an order for a service that has been deleted after the order was started.
• Mondu: Removed the requirement to start the order with a company name and VAT number to select this payment method.

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

In this new version, we've released local ECR. This feature allows you to start payment using TCP messages on your local network. This allows for an alternative to the Cloud ECR solution we already provide.

For more technical information, go to our Github Example page: https://github.com/paynl/PAY.ECR