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

• Added a new keycustomerMethod to every Payment object in an order. When available, this object will contain a key type which specified the used method. The second key, data will contain specific data for that method. We currently have 2 types, iban and card:

IBAN:

"customerMethod": {
  "type": "iban",
  "data": {
    "iban": "NL35RABO0117713678",
    "name": "Stichting Derdengelden Pay.nl",
    "bic": "RABONL2U"
  }
}

Card:

"customerMethod": {
  "type": "card",
  "data": {
    "maskedPan": "123456******7890",
    "scheme": "VISA",
    "issuerId": "18533",
    "countryCode": "642",
    "cardType": "consumer",
    "fundingType": "debit",
    "brandCode": "F",
    "brandName": "Visa Classic",
    "brandProduct": "CN"
  }
}

• Updated several polish translations on the checkout screen.
• Giftcards: Added support for non-numeric PIN entry.
• Giftcards: Fixed a bug preventing customers to be redirected to the giftcard input screen when an order was started with payment method giftcard. Customers were redirected to the payment method selection screen in stead.
• Giftcards: Payments requiring input will now have an expire time of 30 minutes. They previously had no expire time, causing abandoned orders to linger for longer than needed.

📘

These new API's are in pilot phase, please contact your contact person within Pay if you want more information or if you want to join the pilot phase.

We have released new API's to manage look & feel templates (layouts). If you have the appropriate rights you can add one or more look & feel templates (layouts) in your merchant account. With these look and feel setting you can customize our hosted payment page so that it shows the page with your logo and your colors.

We have created the following endpoints:

• Layout:Create; Create a new layout. With this layout you can change e.g. the layout of our hosted payment page;
• Layout:Files; Add files e.g. a logo or a background image to the layout you have created;
• Layout:Update; Update the basic settings of a layout;
• Layout:Get and Layouts:Browse; Get a list of layouts or get the basic information of a layout. For all details of a layout use the Layout:Info endpoint;
• Layout:Info; Get the details (also a base64 representation of all uploaded files) from a specific layout;
• Layout:Delete; Remove a layout.

We also released a few smaller improvements;

• The Invoice:Lines endpoint now returns for the turnoverGroup also the bankaccount that is linked to that turnoverGroup;
• The Transctions:Browse endpoint now support a filter on merchant.

📘

These new API's are in pilot phase, please contact your contact person within Pay if you want more information or if you want to join the pilot phase.

We released new API's to create and manage services /sales locations:

• Service:Create; Create a new service (for a merchant). On a service you can enable payment methods and process payments;
• Service:Update; Update the basic settings for a service;
• Service:EnablePaymentMethod; Enable a payment method for a service, including specific settings for certain payment methods;
• Service:UpdatePaymentMethod; Update a payment method if you have set specific settings;
• Service:DisablePaymentMethod; Disable a payment method for a service;
• Service:GetAvailablePaymentsMethods; Get an overview of available payment methods for the merchant/service, including their boarding status for a service;
• Service:UpdateSettings; Update advanced settings on service, e.g. configure your verify settings or configure your exchanges
• Service:AddUrl / Service:DeleteUrl; Add or delete multiple website URLs for a services;
• Services:Browse; Get an (paginated) overview of all services available for a merchant ;
• Service:Get; Get the basic information of a specific services for a merchant;
• Service:Info; Get the detailed information for a service, including all advanced settings and the enabled payment methods.

📘

More information regarding these API's (and a step by step walkthrough) can be found here

PAY.POS SDK

For selected Merchant, it is now possible to integrate the PAY.POS app into your own app, using the SDK! The PAY.POS SDK makes it possible to accept and process payment card on your iPhone or Android (softpos only).

Documentation and examples regarding the SDK can be found on the PayNL Github.

If you want to get started, please contact PayNL support to get your integrationId!

PAY.POS Local ECR

Starting on PAY.POS version 1.1.18, it is possible to use local ECR. This allows PAY.POS to accept payment requests on the local network using the TCP/UDP procotols.

This feature comes with a new screen: The Order presentation screen. Instead of using TRANSACTION_START via Local ECR, you can show the description & products to the customer live via ORDER_CREATE. When all the products have been registered, and the customer wants to pay, you can transform your order into a transaction and the full order object is sent to the PayNL processing.

Documentation and examples regarding the SDK can be found on the PayNL Github.

• Fixed an error where an additional payment was created when redirected to the hosted payment page after a payment was already created.
• Add supplier data for failed pin transactions to make the incident_code and incident_test fields available.
• Fixed not being able to start an order for several high risk payment profiles:
  • 711 (Carte Blue High Risk)
  • 715 (Maestro High Risk)
  • 708 (Postepay High Risk)
  • 1948 (Nexi High Risk)
  • 1942 (Dankort High Risk)
• Blik: Fixed using the wrong value as the payer id. Payer id will now be empty as Blik does not provide any.
• PayPal: Fixed setting a PayPal payment to captured with amount 0 if the capture is still pending.